From: Daniel Mack <daniel@caiaq.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-pm@lists.linux-foundation.org,
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 14:59:09 +0200 [thread overview]
Message-ID: <20090806125909.GJ19257@buzzloop.caiaq.de> (raw)
In-Reply-To: <200908060251.55157.rjw@sisk.pl>
On Thu, Aug 06, 2009 at 02:51:55AM +0200, Rafael J. Wysocki wrote:
> 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".
Hence, In case of this driver which only calls disable_irq/enable_irq,
setting .poweroff and .restore seems to suffice? So does the patch
below.
Thanks,
Daniel
>From afa35cebccf49a24613e711afb8009fb6aadce0e Mon Sep 17 00:00:00 2001
From: Daniel Mack <daniel@caiaq.de>
Date: Wed, 5 Aug 2009 15:28:54 +0200
Subject: [PATCH 3/3] input: gpio-keys: switch to new dev_pm_ops
The callbacks for the implemented functions are .poweroff and .restore,
as they only care for {dis,en}able_irq(). Renamed the functions
to reflect that.
Signed-off-by: Daniel Mack <daniel@caiaq.de>
Cc: Phil Blundell <pb@handhelds.org>
Cc: linux-input@vger.kernel.org
---
drivers/input/keyboard/gpio_keys.c | 26 ++++++++++++++++----------
1 files changed, 16 insertions(+), 10 deletions(-)
diff --git a/drivers/input/keyboard/gpio_keys.c b/drivers/input/keyboard/gpio_keys.c
index efed0c9..8e670d4 100644
--- a/drivers/input/keyboard/gpio_keys.c
+++ b/drivers/input/keyboard/gpio_keys.c
@@ -216,12 +216,12 @@ static int __devexit gpio_keys_remove(struct platform_device *pdev)
#ifdef CONFIG_PM
-static int gpio_keys_suspend(struct platform_device *pdev, pm_message_t state)
+static int gpio_keys_poweroff(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) {
@@ -234,12 +234,12 @@ static int gpio_keys_suspend(struct platform_device *pdev, pm_message_t state)
return 0;
}
-static int gpio_keys_resume(struct platform_device *pdev)
+static int gpio_keys_restore(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,25 @@ static int gpio_keys_resume(struct platform_device *pdev)
return 0;
}
+
+static struct dev_pm_ops gpio_keys_pm_ops = {
+ .poweroff = gpio_keys_poweroff,
+ .restore = gpio_keys_restore,
+};
+
+#define GPIO_KEYS_PM_OPS (&gpio_keys_pm_ops)
+
#else
-#define gpio_keys_suspend NULL
-#define gpio_keys_resume NULL
+#define GPIO_KEYS_PM_OPS NULL
#endif
static struct platform_driver gpio_keys_device_driver = {
.probe = gpio_keys_probe,
.remove = __devexit_p(gpio_keys_remove),
- .suspend = gpio_keys_suspend,
- .resume = gpio_keys_resume,
.driver = {
.name = "gpio-keys",
.owner = THIS_MODULE,
+ .pm = GPIO_KEYS_PM_OPS,
}
};
--
1.6.3.3
next prev parent reply other threads:[~2009-08-06 12:59 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 18:29 [PATCH 1/5] w1_gpio: switch to new dev_pm_ops Daniel Mack
2009-08-05 18:29 ` [PATCH 2/5] pda-power: " Daniel Mack
2009-08-05 18:29 ` Daniel Mack
2009-08-05 18:29 ` [PATCH 3/5] ds2760: " Daniel Mack
2009-08-05 18:29 ` [PATCH 4/5] input: gpio-keys: " Daniel Mack
2009-08-05 18:29 ` [PATCH 5/5] net: smsc911x: " Daniel Mack
2009-08-05 18:29 ` Daniel Mack
2009-08-06 3:29 ` David Miller
2009-08-06 3:29 ` David Miller
2009-08-06 11:53 ` Steve.Glendinning
2009-08-06 11:53 ` Steve.Glendinning
2009-08-06 20:26 ` David Miller
2009-08-06 20:26 ` David Miller
2009-08-06 20:26 ` David Miller
2009-08-06 11:53 ` Steve.Glendinning
2009-08-05 20:15 ` [PATCH 4/5] input: gpio-keys: " pHilipp Zabel
2009-08-05 20:15 ` pHilipp Zabel
2009-08-05 22:33 ` Daniel Mack
2009-08-05 22:33 ` Daniel Mack
2009-08-06 0:51 ` [linux-pm] " Rafael J. Wysocki
2009-08-06 12:59 ` Daniel Mack [this message]
2009-08-06 15:19 ` Rafael J. Wysocki
2009-08-06 15:19 ` [linux-pm] " Rafael J. Wysocki
2009-08-07 13:39 ` pHilipp Zabel
2009-08-07 13:39 ` pHilipp Zabel
2009-08-07 13:39 ` pHilipp Zabel
2009-08-06 12:59 ` Daniel Mack
2009-08-06 0:51 ` Rafael J. Wysocki
2009-08-05 20:15 ` pHilipp Zabel
2009-08-05 18:29 ` Daniel Mack
2009-08-05 18:29 ` [PATCH 3/5] ds2760: " Daniel Mack
2009-08-05 19:49 ` [PATCH 2/5] pda-power: " Frans Pop
2009-08-05 19:49 ` Frans Pop
2009-08-05 22:29 ` Daniel Mack
2009-08-06 11:52 ` pHilipp Zabel
2009-08-06 11:52 ` pHilipp Zabel
2009-08-06 12:56 ` Daniel Mack
2009-08-07 13:35 ` pHilipp Zabel
2009-09-04 16:34 ` Anton Vorontsov
2009-09-04 16:34 ` Anton Vorontsov
2009-08-07 13:35 ` pHilipp Zabel
2009-08-06 12:56 ` Daniel Mack
2009-08-05 22:29 ` Daniel Mack
2009-08-05 18:44 ` [PATCH 1/5] w1_gpio: " Rafael J. Wysocki
2009-08-05 18:45 ` Daniel Mack
2009-08-05 18:45 ` Daniel Mack
2009-08-05 18:44 ` Rafael J. Wysocki
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=20090806125909.GJ19257@buzzloop.caiaq.de \
--to=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 \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.