[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <201102251928.22328.rwys@fuw.edu.pl>
Date: Fri, 25 Feb 2011 19:28:22 +0100
From: "R. J. Wysocki" <Rafal.Wysocki@....edu.pl>
To: Matthew Garrett <mjg59@...f.ucam.org>
Cc: "Tardy, Pierre" <pierre.tardy@...el.com>,
Chris Ball <cjb@...top.org>, Pierre Tardy <tardyp@...il.com>,
"linux-pm@...ts.linux-foundation.org"
<linux-pm@...ts.linux-foundation.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Gao, Yunpeng" <yunpeng.gao@...el.com>
Subject: Re: [PATCH v2 2/3] sdhci-pci : Enable runtime PM support
On Friday, February 25, 2011, Matthew Garrett wrote:
> On Fri, Feb 25, 2011 at 07:33:12AM +0000, Tardy, Pierre wrote:
>
> > My understanding is the pci driver is not supposed to do any set_power_state/pci_save_state/wake_enable.
> > Everything is supposed to be generically handle by pci frameworks's runtime_pm impl.
> > Need confirmation from Rafael.
>
> The core can only enable PME generation, it can't configure what
> generates PMEs. There's a register in sdhci that needs to be programmed
> to enable wakeups on card insert/removal/interrupt. If you don't then
> you won't get a PME no matter what the core does.
That's correct. The driver shoulnd't touch the generic-PCI part of wakeup
preparation, but it _should_ configure the device-specific part of it.
It's quite similar to network adapters where you have to configure the adapter
to react to magic packets, for example, in addition to the PCI PME setup done
by the core.
Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists