On Wed, Aug 19, 2009 at 07:52:10PM +0800, Matthew Garrett wrote:
> On Wed, Aug 19, 2009 at 03:24:11PM +0800, Shaohua Li wrote:
>
> > Usually driver should does nothing in the op as bus can handle it. But in some
> > cases, like pci bus, UHCI controller doesn't use standard PME registers for
> > wakeup, instead of using special approach. In this case, UHCI controller driver
> > should implement this op.
>
> I'm not averse to the general concept, but I'm not entirely sold on it
> being necessary. All the hardware I'm aware of will send non-PME events
> as a notification on a specific device. Under what circumstances will we
> get a wakeup GPE for a non-PME device without knowing which device
> should be woken?
Below code is gotten from a laptop (samsung-x10), the PCIB is the PCI bridge.
We can't guarantee the device which gets a wakeup event notification is really
the device which invokes the wakeup event.
Device (PCIB)
{
Name (_ADR, 0x001E0000)
Device (CDB0)
{
Name (_ADR, 0x00030000)
}
Device (CDB1)
{
Name (_ADR, 0x00030001)
}
}
Method (_L0B, 0, NotSerialized)
{
Notify (\_SB.PCI0.PCIB, 0x02)
Notify (\_SB.PWRB, 0x02)
Store (0x01, \_SB.PCI0.PCIB.CDB0.PMES)
Store (0x01, \_SB.PCI0.PCIB.CDB1.PMES)
}
Thanks,
Shaohua
--
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
