]> pilppa.com Git - linux-2.6-omap-h63xx.git/commit
ACPI: crosslink ACPI and "real" device nodes
authorDavid Brownell <david-b@pacbell.net>
Sat, 23 Feb 2008 05:54:24 +0000 (21:54 -0800)
committerLen Brown <len.brown@intel.com>
Sat, 23 Feb 2008 06:32:56 +0000 (01:32 -0500)
commit1071695f17daf050638e0bc550db647f8237c3bb
tree4770e712c2293d0156fbb53bebc6fa059a8a99eb
parent39273b58a409cd6d65c9732bdca00bacd1626672
ACPI: crosslink ACPI and "real" device nodes

Add cross-links between ACPI device and "real" devices in sysfs,
exposing otherwise-hidden interrelationships between the various
device nodes for ACPI stuff.  As a representative example, one
hardware device is exposed as two logical devices (PNP and ACPI):

  .../pnp0/00:06/
  .../LNXSYSTM:00/device:00/PNP0A03:00/device:15/PNP0B00:00/

The PNP device gets a "firmware_node" link pointing to the ACPI device,
and is what a Linux device driver binds to.  The ACPI device has instead
a "physical_node" link pointing back to the PNP device.  Other firmware
frameworks, like OpenFirmware, could do the same thing to couple their
firmware tables to the rest of the system.

(Based on a patch from Zhang Rui.  This version is modified to not
depend on the patch makig ACPI initialize driver model wakeup flags.)

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Cc: Zhang Rui <rui.zhang@intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
drivers/acpi/glue.c