From: Chanwoo Choi <cw00.choi@samsung.com>
To: Hans de Goede <hdegoede@redhat.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Chen-Yu Tsai <wens@csie.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH resend] extcon: axp288: Add wakeup support
Date: Wed, 25 Mar 2020 07:37:59 +0900 [thread overview]
Message-ID: <cf0700cf-caed-0451-f8ba-b536e01488f6@samsung.com> (raw)
In-Reply-To: <20200323215939.79008-1-hdegoede@redhat.com>
On 3/24/20 6:59 AM, Hans de Goede wrote:
> 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.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> drivers/extcon/extcon-axp288.c | 32 ++++++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
> diff --git a/drivers/extcon/extcon-axp288.c b/drivers/extcon/extcon-axp288.c
> index a7f216191493..710a3bb66e95 100644
> --- a/drivers/extcon/extcon-axp288.c
> +++ b/drivers/extcon/extcon-axp288.c
> @@ -443,9 +443,40 @@ static int axp288_extcon_probe(struct platform_device *pdev)
> /* 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" },
> {},
> @@ -457,6 +488,7 @@ static struct platform_driver axp288_extcon_driver = {
> .id_table = axp288_extcon_table,
> .driver = {
> .name = "axp288_extcon",
> + .pm = &axp288_extcon_pm_ops,
> },
> };
>
>
Applied it. Thanks.
--
Best Regards,
Chanwoo Choi
Samsung Electronics
next prev parent reply other threads:[~2020-03-24 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200323215949epcas1p33af2bba09c458dd09ed22e3de200955a@epcas1p3.samsung.com>
2020-03-23 21:59 ` Hans de Goede
2020-03-24 22:37 ` Chanwoo Choi [this message]
2020-03-25 1:01 ` Sasha Levin
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=cf0700cf-caed-0451-f8ba-b536e01488f6@samsung.com \
--to=cw00.choi@samsung.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=stable@vger.kernel.org \
--cc=wens@csie.org \
/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
all inboxes | Powered by JetHome®