Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932074Ab1CAUab (ORCPT ); Tue, 1 Mar 2011 15:30:31 -0500 Received: from iolanthe.rowland.org ([192.131.102.54]:51145 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1757148Ab1CAUaa (ORCPT ); Tue, 1 Mar 2011 15:30:30 -0500 Date: Tue, 1 Mar 2011 15:30:29 -0500 (EST) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Pierre Tardy cc: linux-kernel@vger.kernel.org, , Subject: Re: [linux-pm] [RFC,PATCHv3 0/3] sdhci runtime_pm implementation In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1095 Lines: 26 On Tue, 1 Mar 2011, Pierre Tardy wrote: > >> > Other drivers do it, but they use PCI PME# instead of interrupts. > >> Could you please elaborate? > >> My understanding is that PCI PME will generate MSI, which translate in > >> interrupt. > > > > It depends on the platform. ?On systems with ACPI, PCI PME generates an > > ACPI I/O event, which is handled by the ACPI and PM cores. ?It does not > > invoke the device driver's interrupt handler. > So, let's say, in the ACPI case, if the interrupt handler dont get > called, how would the driver know that he got a sdcard insert event, > and trigger a mmc_rescan() ? When the ACPI and PCI cores process the PME event, they call pm_runtime_resume(). The driver's runtime_resume routine would read the device status and see the insert event, which would cause it to trigger mmc_rescan(). Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/