 
	
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [RFC v2 2/7] arm64: Add definitions for fwnode_handle
 Hi, On 21/09/17 01:37, Sameer Goel wrote: This will be used as a device property to match the DMA capable devices with the associated SMMU. The header file is a port from linux. The code was changed to remove the types that were not needed for Xen. I think you probably want a bit more context in the commit message about implement fwnode.h in common code. Within this series, fwnode seems to only be used by Arm. So what would be the advantage to get that in xen/? Is it going to be used by x86 or taken advantage in common code? Linux ChangeId:ce793486e23e: driver core / ACPI: Represent ACPI companions using fwnode_handle Signed-off-by: Sameer Goel <sgoel@xxxxxxxxxxxxxx> --- xen/include/asm-arm/device.h | 2 ++ xen/include/xen/fwnode.h | 33 +++++++++++++++++++++++++++++++++ 2 files changed, 35 insertions(+) create mode 100644 xen/include/xen/fwnode.h diff --git a/xen/include/asm-arm/device.h b/xen/include/asm-arm/device.h index 6734ae8..78c38fe 100644 --- a/xen/include/asm-arm/device.h +++ b/xen/include/asm-arm/device.h @@ -2,6 +2,7 @@ #define __ASM_ARM_DEVICE_H#include <xen/init.h>+#include <xen/fwnode.h>enum device_type I was expecting a todo in the code after the discussion about leave of_node here. #endif + struct fwnode_handle *fwnode; /*fw device node identifier */ Space missing before "fw". 
 Looking at Linux code, the fwnode_type already disappeared from Linux (see commit db3e50f3234b "device property: Get rid of struct fwnode_handle type field"). I understand the goal on using fwnode is to help porting drivers from Linux. So how much this has changed now? Cheers, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel 
 
 | 
|  | Lists.xenproject.org is hosted with RackSpace, monitoring our |