On Wednesday, August 17, 2016 02:38:15 AM Rafael J. Wysocki wrote: > On Thursday, July 28, 2016 02:25:41 AM Lukas Wunner wrote: > > Following the fwnode of a device is currently a one-way road: We provide > > ACPI_COMPANION() to obtain the fwnode but there's no (public) method to > > do the reverse. Granted, there may be multiple physical_nodes, but often > > the first one in the list is sufficient. > > > > A handy function to obtain it was introduced with commit 3b95bd160547 > > ("ACPI: introduce a function to find the first physical device"), but > > currently it's only available internally. > > > > We're about to add an EFI Device Path parser which needs this function. > > Consider the following device path: ACPI(PNP0A03,0)/PCI(28,2)/PCI(0,0) > > The PCI root is encoded as an ACPI device in the path, so the parser > > has to find the corresponding ACPI device, then find its physical node, > > find the PCI bridge in slot 1c (decimal 28), function 2 below it and > > finally find the PCI device in slot 0, function 0. > > > > To this end, make acpi_get_first_physical_node() public. > > > > Cc: Aleksey Makarov <aleksey.makarov@xxxxxxxxxx> > > Cc: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx> > > Signed-off-by: Lukas Wunner <lukas@xxxxxxxxx> > > ACK I've applied this one, thanks! Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html