Searched hist:"859 ac9a4be0c753cece0e30a2e4a65fd2cdcaeee" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/include/acpi/ |
| H A D | acpi_bus.h | diff 859ac9a4be0c753cece0e30a2e4a65fd2cdcaeee Mon Sep 21 14:29:50 CDT 2009 Bjorn Helgaas <bjorn.helgaas@hp.com> ACPI: identify device tree root by null parent pointer, not ACPI_BUS_TYPE
We can identify the root of the ACPI device tree by the fact that it
has no parent. This is simpler than passing around ACPI_BUS_TYPE_SYSTEM
and will help remove special treatment of the device tree root.
Currently, we add the root by hand with ACPI_BUS_TYPE_SYSTEM. If we
traverse the tree treating the root as just another device and use
acpi_get_type(), the root shows up as ACPI_TYPE_DEVICE.
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Signed-off-by: Len Brown <len.brown@intel.com>
|
| /openbmc/linux/drivers/acpi/ |
| H A D | scan.c | diff 859ac9a4be0c753cece0e30a2e4a65fd2cdcaeee Mon Sep 21 14:29:50 CDT 2009 Bjorn Helgaas <bjorn.helgaas@hp.com> ACPI: identify device tree root by null parent pointer, not ACPI_BUS_TYPE
We can identify the root of the ACPI device tree by the fact that it
has no parent. This is simpler than passing around ACPI_BUS_TYPE_SYSTEM
and will help remove special treatment of the device tree root.
Currently, we add the root by hand with ACPI_BUS_TYPE_SYSTEM. If we
traverse the tree treating the root as just another device and use
acpi_get_type(), the root shows up as ACPI_TYPE_DEVICE.
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Signed-off-by: Len Brown <len.brown@intel.com>
|