From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [PATCH 1/5] introduce .wakeup_event ops Date: Thu, 20 Aug 2009 15:14:36 +0100 Message-ID: <20090820141436.GA3722@srcf.ucam.org> References: <20090820030423.GA26357@sli10-desk.sh.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([93.93.128.6]:57148 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754205AbZHTOOt (ORCPT ); Thu, 20 Aug 2009 10:14:49 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Alan Stern Cc: Shaohua Li , linux acpi , pm list , "Rafael J. Wysocki" On Thu, Aug 20, 2009 at 10:11:19AM -0400, Alan Stern wrote: > How is the wakeup event received? Maybe for this one type of device a > PCI quirk will solve the problem. Pretty much the same as PME events on PCI - a GPE is generated, an SCI raised, the ACPI interpreter executes the code that's in the ACPI tables, that generates a notification event on the appropriate UHCI device, we live happily ever after. -- Matthew Garrett | mjg59@srcf.ucam.org