Hi!
commit 9c94553099efb2ba873cbdddfd416a8a09d0e5f1 upstream.
On devices with an AXP288, we need to wakeup from suspend when a charger is plugged in, so that we can do charger-type detection and so that the axp288-charger driver, which listens for our extcon events, can configure the input-current-limit accordingly.
Will it do the same on charger disconnect?
Is that a tiny bit anti-social? I suspend a machine, unplug a charger, put it into a bag.. but machine is now running.
On some machines (sharp zaurus) we catch such wakeups, do whatever charging magic we need to do, and put machine back to sleep, so that user does not see the wakeups (and so that we don't drain the battery).
Best regards, Pavel
--- a/drivers/extcon/extcon-axp288.c +++ b/drivers/extcon/extcon-axp288.c @@ -428,9 +428,40 @@ static int axp288_extcon_probe(struct pl /* Start charger cable type detection */ axp288_extcon_enable(info);
- device_init_wakeup(dev, true);
- platform_set_drvdata(pdev, info);
- return 0;
+}
+static int __maybe_unused axp288_extcon_suspend(struct device *dev) +{
- struct axp288_extcon_info *info = dev_get_drvdata(dev);
- if (device_may_wakeup(dev))
enable_irq_wake(info->irq[VBUS_RISING_IRQ]);- return 0;
} +static int __maybe_unused axp288_extcon_resume(struct device *dev) +{
- struct axp288_extcon_info *info = dev_get_drvdata(dev);
- /*
* Wakeup when a charger is connected to do charger-type* connection and generate an extcon event which makes the* axp288 charger driver set the input current limit.*/- if (device_may_wakeup(dev))
disable_irq_wake(info->irq[VBUS_RISING_IRQ]);- return 0;
+}
+static SIMPLE_DEV_PM_OPS(axp288_extcon_pm_ops, axp288_extcon_suspend,
axp288_extcon_resume);static const struct platform_device_id axp288_extcon_table[] = { { .name = "axp288_extcon" }, {}, @@ -442,6 +473,7 @@ static struct platform_driver axp288_ext .id_table = axp288_extcon_table, .driver = { .name = "axp288_extcon",
.pm = &axp288_extcon_pm_ops,};