From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [RFC][PATCH 1/10] PM: Add flag for devices capable of generating run-time wake-up events Date: Mon, 16 Nov 2009 21:05:45 +0000 Message-ID: <20091116210545.GA29696@srcf.ucam.org> References: <200911162152.38333.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-pci-owner@vger.kernel.org To: Alan Stern Cc: "Rafael J. Wysocki" , pm list , LKML , Linux PCI , ACPI Devel Maling List , Jesse Barnes , Oliver Neukum , Shaohua Li , Bjorn Helgaas List-Id: linux-acpi@vger.kernel.org On Mon, Nov 16, 2009 at 04:00:49PM -0500, Alan Stern wrote: > On Mon, 16 Nov 2009, Rafael J. Wysocki wrote: > > Yes, in general. The platform. > > And for non-platform devices (hot-pluggable, for example)? Presumably > you would want the driver that detects and registers the device to set > this flag. Are there any cases where the bus code won't know this? > > > What if the kernel can't tell whether or not the device can generate > > > runtime wake-up events? > > > > Do you have any specific examples in mind? > > What about Matthew's example of an ACPI GPE which might or might not > cause a runtime wake-up event, depending on the AML code in the BIOS? The platform knows whether or not that's the case. -- Matthew Garrett | mjg59@srcf.ucam.org