Messages in this thread | | | Date | Mon, 11 Apr 2011 21:19:42 -0700 | Subject | Re: [PATCH v3] gpio-charger: Add gpio_charger_resume | From | Benson Leung <> |
| |
Thanks Lars.
Hi Anton,
Can this patch be applied?
Thanks, Benson
On Wed, Apr 6, 2011 at 5:15 PM, Lars-Peter Clausen <lars@metafoo.de> wrote: > On 04/07/2011 01:55 AM, Benson Leung wrote: >> Gpio charger should notify if the gpio state had changed >> during suspend. This will send a CHANGED event each time >> the system resumes, ensuring a plug/unplug of the charger >> is not missed. >> >> Signed-off-by: Benson Leung <bleung@chromium.org> > Acked-By: Lars-Peter Clausen <lars@metafoo.de> > >> >> -- >> Version history : >> v3 : Use SIMPLE_DEV_PM_OPS >> v2 : Changed to use dev_ms_ops >> v1 : Initial >> --- >> drivers/power/gpio-charger.c | 15 +++++++++++++++ >> 1 files changed, 15 insertions(+), 0 deletions(-) >> >> diff --git a/drivers/power/gpio-charger.c b/drivers/power/gpio-charger.c >> index 25b88ac..718f2c5 100644 >> --- a/drivers/power/gpio-charger.c >> +++ b/drivers/power/gpio-charger.c >> @@ -161,12 +161,27 @@ static int __devexit gpio_charger_remove(struct platform_device *pdev) >> return 0; >> } >> >> +#ifdef CONFIG_PM_SLEEP >> +static int gpio_charger_resume(struct device *dev) >> +{ >> + struct platform_device *pdev = to_platform_device(dev); >> + struct gpio_charger *gpio_charger = platform_get_drvdata(pdev); >> + >> + power_supply_changed(&gpio_charger->charger); >> + >> + return 0; >> +} >> +#endif >> + >> +static SIMPLE_DEV_PM_OPS(gpio_charger_pm_ops, NULL, gpio_charger_resume); >> + >> static struct platform_driver gpio_charger_driver = { >> .probe = gpio_charger_probe, >> .remove = __devexit_p(gpio_charger_remove), >> .driver = { >> .name = "gpio-charger", >> .owner = THIS_MODULE, >> + .pm = &gpio_charger_pm_ops, >> }, >> }; >> > > -- 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/
| |