From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-pm@lists.linux-foundation.org
Cc: Daniel Mack <daniel@caiaq.de>,
pHilipp Zabel <philipp.zabel@gmail.com>,
Phil Blundell <pb@handhelds.org>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [linux-pm] [PATCH 4/5] input: gpio-keys: switch to new dev_pm_ops
Date: Thu, 6 Aug 2009 02:51:55 +0200 [thread overview]
Message-ID: <200908060251.55157.rjw@sisk.pl> (raw)
In-Reply-To: <20090805223342.GG19257@buzzloop.caiaq.de>
On Thursday 06 August 2009, Daniel Mack wrote:
> On Wed, Aug 05, 2009 at 10:15:52PM +0200, pHilipp Zabel wrote:
> > On Wed, Aug 5, 2009 at 8:29 PM, Daniel Mack<daniel@caiaq.de> wrote:
> > > -static int gpio_keys_resume(struct platform_device *pdev)
> > > +static int gpio_keys_resume(struct device *dev)
> > > {
> > > - struct gpio_keys_platform_data *pdata = pdev->dev.platform_data;
> > > + struct gpio_keys_platform_data *pdata = dev->platform_data;
> > > int i;
> > >
> > > - if (device_may_wakeup(&pdev->dev)) {
> > > + if (device_may_wakeup(dev)) {
> > > for (i = 0; i < pdata->nbuttons; i++) {
> > > struct gpio_keys_button *button = &pdata->buttons[i];
> > > if (button->wakeup) {
> > > @@ -251,19 +251,27 @@ static int gpio_keys_resume(struct platform_device *pdev)
> > >
> > > return 0;
> > > }
> > > +
> > > +static struct dev_pm_ops gpio_keys_pm_ops = {
> > > + .suspend = gpio_keys_suspend,
> > > + .freeze = gpio_keys_suspend,
> > > + .resume = gpio_keys_resume,
> > > + .thaw = gpio_keys_resume,
> >
> > I'm not sure I understand hibernation correctly, but isn't
> > .freeze/.thaw about saving state and halting/resuming the device
> > operation only?
It is.
> > It seems to me that enabling system wakeup functionality should go
> > into .poweroff. (See <linux/pm.h>)
That's correct.
And .restore() plays the role of ".resume() from hibernation".
> Frankly, I'm not sure either. But luckily, the linux-pm list is copied
> so someone can elborate on this :)
HTH
Best,
Rafael
next prev parent reply other threads:[~2009-08-06 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1249496971-9019-1-git-send-email-daniel@caiaq.de>
[not found] ` <1249496971-9019-2-git-send-email-daniel@caiaq.de>
[not found] ` <1249496971-9019-3-git-send-email-daniel@caiaq.de>
2009-08-05 18:29 ` [PATCH 4/5] input: gpio-keys: switch to new dev_pm_ops Daniel Mack
2009-08-05 20:15 ` pHilipp Zabel
2009-08-05 22:33 ` Daniel Mack
2009-08-06 0:51 ` Rafael J. Wysocki [this message]
2009-08-06 12:59 ` [linux-pm] " Daniel Mack
2009-08-06 15:19 ` Rafael J. Wysocki
2009-08-07 13:39 ` pHilipp Zabel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200908060251.55157.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=daniel@caiaq.de \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pb@handhelds.org \
--cc=philipp.zabel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).