Re: [PATCH 1/5] introduce .wakeup_event ops

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 20 Aug 2009, Matthew Garrett wrote:

> > If the wakeup signal isn't squelched at the source, as part of the
> > event handling, will we get an interrupt storm?  Will the uhci-hcd 
> > resume routine be able to handle this or does it need to be done 
> > earlier?  In other words, do we need special-purpose code in the PCI 
> > layer to handler it?
> 
> No, nothing special needs to be done at the PCI level. It seems that 
> (for Intel at least) there's no need to do anything special at the UHCI 
> level either.

This contradicts what Shaohua wrote:

"The only case is UHCI in my mind. Because UHCI has non-standard wakeup
event register. If BIOS doesn't handle it correctly (for example, not
clear the wakeup event after a GPE), we will keep see the wakeup
event."

What code would be responsible for setting and clearing the 
non-standard wakeup register?  Are you assuming that ACPI will always 
handle it?  I guess that's a reasonable assumption -- if ACPI wasn't 
aware of the register then it never would get enabled, and conversely, 
if ACPI was aware and could enable the register, then ACPI ought to 
disable it when necessary.

Alan Stern

--
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

[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux