On Wed, 2007-04-04 at 08:41 +0800, David Brownell wrote: > 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). > Well, ACPI can't find the sysfs node for all the wakeup-enabled devices. In fact, only pci and pnp devices can be found now. ACPI needs the ability to distinguish all the physical devices, i.e. map ACPI device to physical device nodes in sysfs, which I mentioned before. Thanks, Rui - 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
