Hi, this series makes it possible to extract device dependencies from firmware data with fwnode, thus not depending on the particular format of that data.
The first patches are about making sure that we can reach the fwnode handle of the firmware data associated with a given device, and the rest add API that makes dependency extraction possible. Thanks, Tomeu Tomeu Vizoso (10): of/platform: Set fwnode field for new devices i2c: core: Have clients point to their firmware nodes mfd: Have child devices point to their firmware nodes device property: add fwnode_get_parent() device property: add fwnode_get_name() ACPI / scan: Add acpi_dev_get_next_child() device property: Add fwnode_get_next_child_node() device property: add fwnode_is_compatible() device: property: add fwnode_driver_match_device() core: platform: use fwnode_driver_match_device() drivers/acpi/scan.c | 5 +-- drivers/base/platform.c | 8 +--- drivers/base/property.c | 95 ++++++++++++++++++++++++++++++++++++++++++++---- drivers/i2c/i2c-core.c | 1 + drivers/mfd/mfd-core.c | 1 + drivers/of/platform.c | 1 + include/acpi/acpi_bus.h | 5 +++ include/linux/acpi.h | 22 ++++++++++- include/linux/property.h | 17 +++++++++ 9 files changed, 136 insertions(+), 19 deletions(-) -- 2.4.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
