ACPI: make /proc/acpi/wakeup more useful
authorDavid Brownell <david-b@pacbell.net>
Wed, 25 Apr 2007 19:20:10 +0000 (15:20 -0400)
committerLen Brown <len.brown@intel.com>
Wed, 25 Apr 2007 19:20:10 +0000 (15:20 -0400)
commit8aa55591bfea25c441117e82711cbfd7c274250a
tree8429241902a2aded2a93b6b7d7ddb99b778b0ddb
parentcf6c6045a06aed2ccd8ebd0a3128ce0f2f8a11aa
ACPI: make /proc/acpi/wakeup more useful

This updates /proc/acpi/wakeup to be more informative, primarily by showing
the sysfs node associated with each wakeup-enabled device.  Example:

Device S-state   Status   Sysfs node
PCI0   S4  disabled  no-bus:pci0000:00
PS2M   S4  disabled  pnp:00:05
PS2K   S4  disabled  pnp:00:06
UAR1   S4  disabled  pnp:00:08
USB1   S3  disabled  pci:0000:00:03.0
USB2   S3  disabled  pci:0000:00:03.1
USB3   S3  disabled
USB4   S3  disabled  pci:0000:00:03.3
S139   S4  disabled
LAN   S4  disabled  pci:0000:00:04.0
MDM   S4  disabled
AUD   S4  disabled  pci:0000:00:02.7
SLPB   S4 *enabled

Eventually this file should be removed, but until then it's almost the only
way we have to tell how the relevant ACPI tables are broken (and cope).  In
that example, two devices don't actually exist (USB3, S139), one can't issue
wakeup events (PCI0), and two seem harmlessly (?) confused (MDM and AUD are
the same PCI device, but it's the _modem_ that does wake-on-ring).

In particular, we need to be sure driver model nodes are properly hooked
up before we can get rid of this ACPI-only interface for wakeup events.

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Len Brown <len.brown@intel.com>
drivers/acpi/sleep/proc.c