From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [PATCH 1/5] introduce .wakeup_event ops Date: Fri, 21 Aug 2009 10:23:16 +0100 Message-ID: <20090821092316.GA19617@srcf.ucam.org> References: <1250666651.23178.116.camel@sli10-desk.sh.intel.com> <20090819115210.GC12216@srcf.ucam.org> <20090820032450.GD26357@sli10-desk.sh.intel.com> <20090820074050.GA30288@srcf.ucam.org> <20090821063350.GA16694@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]:43974 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755111AbZHUJX1 (ORCPT ); Fri, 21 Aug 2009 05:23:27 -0400 Content-Disposition: inline In-Reply-To: <20090821063350.GA16694@sli10-desk.sh.intel.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Shaohua Li Cc: linux acpi , pm list , "Rafael J. Wysocki" , Alan Stern On Fri, Aug 21, 2009 at 02:33:50PM +0800, Shaohua Li wrote: > On Thu, Aug 20, 2009 at 03:40:51PM +0800, Matthew Garrett wrote: > > _L0B will only be triggered if a PME is generated, so we'll be able to > > determine which device generated the wakeup by looking at the PME > > registers. > Right, but the event is sent to a bridge. The devices under the bridge invoke > wakeup event, not the bridge itself. So you must scan all devices under the > bridge to check which device has its PME registers set. > So the bridge case isn't what you said (notification always sent to a specific > device which invokes the wakeup event) Yes, but that's fine because the PME state tells us exactly which device caused the wakeup. We'll never get a bus notification if the wakeup is triggered by UHCI on Intel. -- Matthew Garrett | mjg59@srcf.ucam.org