leandrof/linux
1
0
Fork 0
forked from Minki/linux
Code Issues Pull Requests Packages Projects Releases Wiki Activity

of/platform: Initialise dev->fwnode appropriately

Browse Source 
Whilst we're some of the way towards a universal firmware property
interface, drivers which deal with both OF and ACPI probing end up
having to do things like this:

    dev->of_node ? &dev->of_node->fwnode : dev->fwnode

This seems unnecessary, when the OF code could instead simply fill in
the device's fwnode when binding the of_node, and let the drivers use
dev->fwnode either way. Let's give it a go and see what falls out.

Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Rob Herring <robh@kernel.org>
This commit is contained in:
Robin Murphy 2016-09-14 16:01:24 +01:00 committed by Rob Herring
parent a67e9472da
commit f94277af03
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
drivers/of/platform.c
View File

@ -142,6 +142,7 @@ struct platform_device *of_device_alloc(struct device_node *np,
} }
dev->dev.of_node = of_node_get(np); dev->dev.of_node = of_node_get(np);
dev->dev.fwnode = &np->fwnode;
dev->dev.parent = parent ? : &platform_bus; dev->dev.parent = parent ? : &platform_bus;
if (bus_id) if (bus_id)
@ -241,6 +242,7 @@ static struct amba_device *of_amba_device_create(struct device_node *node,
/* setup generic device info */ /* setup generic device info */
dev->dev.of_node = of_node_get(node); dev->dev.of_node = of_node_get(node);
dev->dev.fwnode = &node->fwnode;
dev->dev.parent = parent ? : &platform_bus; dev->dev.parent = parent ? : &platform_bus;
dev->dev.platform_data = platform_data; dev->dev.platform_data = platform_data;
if (bus_id) if (bus_id)