http://bugzilla.kernel.org/show_bug.cgi?id=12091





------- Comment #7 from [EMAIL PROTECTED]  2008-11-23 18:35 -------
look at this section in ACPI spec,
"Events that wake may not be intermixed with non-wake (runtime) events on the
same GPE input. The only exception to this rule is made for the special devices
below. Only the following devices are allowed to utilize a single GPE for both
wake and runtime events:
1) Button Devices
     •     PNP0C0C — Power Button Device
     •     PNP0C0D — Lid Device
     •     PNP0C0E — Sleep Button Device
2) PCI Bus Wakeup Event Reporting (PME)
     •     PNP0A03 — PCI Host Bridge
"

the ideal solution should be:
1. revert faee816b1502385dc9bc5abf2960d1cc645844d1 to fix this regression.

2. set Both button devices and PCI host bridge as RUN_WAKE devices according to
ACPI spec.

3. As the PNP0A03 GPE is a RUN_WAKE GPE then, it's always enabled during
suspend/resume. Then it's the PCI device's responsibility to determine when
PMEs should be issued, done by commit 49db139955d3392c6c4facf987905d0a9afed581. 

But in order to prove this, first of all we should make sure bug #10503 can't
be reproduced in the latest kernel after
faee816b1502385dc9bc5abf2960d1cc645844d1 is reverted. 

what do you think?


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to