From: Hans de Goede <hdegoede@redhat.com>
To: Samuel Holland <samuel@sholland.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Chen-Yu Tsai <wens@csie.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sunxi@googlegroups.com
Subject: Re: [PATCH v2 1/2] Input: axp20x-pek - Respect userspace wakeup configuration
Date: Wed, 15 Jan 2020 11:50:08 +0100 [thread overview]
Message-ID: <674932c7-c120-092f-0255-5fa94925155d@redhat.com> (raw)
In-Reply-To: <20200115051253.32603-2-samuel@sholland.org>
Hi,
On 15-01-2020 06:12, Samuel Holland wrote:
> Unlike most other power button drivers, this driver unconditionally
> enables its wakeup IRQ. It should be using device_may_wakeup() to
> respect the userspace configuration of wakeup sources.
>
> Because the AXP20x MFD device uses regmap-irq, the AXP20x PEK IRQs are
> nested off of regmap-irq's threaded interrupt handler. The device core
> ignores such interrupts, so to actually disable wakeup, we must
> explicitly disable all non-wakeup interrupts during suspend.
>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
Patch looks good to me:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
> ---
> drivers/input/misc/axp20x-pek.c | 37 ++++++++++++++++++++++++++++++++-
> 1 file changed, 36 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/input/misc/axp20x-pek.c b/drivers/input/misc/axp20x-pek.c
> index 17c1cca74498..0ace3fe3d7dc 100644
> --- a/drivers/input/misc/axp20x-pek.c
> +++ b/drivers/input/misc/axp20x-pek.c
> @@ -280,7 +280,7 @@ static int axp20x_pek_probe_input_device(struct axp20x_pek *axp20x_pek,
> }
>
> if (axp20x_pek->axp20x->variant == AXP288_ID)
> - enable_irq_wake(axp20x_pek->irq_dbr);
> + device_init_wakeup(&pdev->dev, true);
>
> return 0;
> }
> @@ -352,6 +352,40 @@ static int axp20x_pek_probe(struct platform_device *pdev)
> return 0;
> }
>
> +static int __maybe_unused axp20x_pek_suspend(struct device *dev)
> +{
> + struct axp20x_pek *axp20x_pek = dev_get_drvdata(dev);
> +
> + /*
> + * As nested threaded IRQs are not automatically disabled during
> + * suspend, we must explicitly disable non-wakeup IRQs.
> + */
> + if (device_may_wakeup(dev)) {
> + enable_irq_wake(axp20x_pek->irq_dbf);
> + enable_irq_wake(axp20x_pek->irq_dbr);
> + } else {
> + disable_irq(axp20x_pek->irq_dbf);
> + disable_irq(axp20x_pek->irq_dbr);
> + }
> +
> + return 0;
> +}
> +
> +static int __maybe_unused axp20x_pek_resume(struct device *dev)
> +{
> + struct axp20x_pek *axp20x_pek = dev_get_drvdata(dev);
> +
> + if (device_may_wakeup(dev)) {
> + disable_irq_wake(axp20x_pek->irq_dbf);
> + disable_irq_wake(axp20x_pek->irq_dbr);
> + } else {
> + enable_irq(axp20x_pek->irq_dbf);
> + enable_irq(axp20x_pek->irq_dbr);
> + }
> +
> + return 0;
> +}
> +
> static int __maybe_unused axp20x_pek_resume_noirq(struct device *dev)
> {
> struct axp20x_pek *axp20x_pek = dev_get_drvdata(dev);
> @@ -371,6 +405,7 @@ static int __maybe_unused axp20x_pek_resume_noirq(struct device *dev)
> }
>
> static const struct dev_pm_ops axp20x_pek_pm_ops = {
> + SET_SYSTEM_SLEEP_PM_OPS(axp20x_pek_suspend, axp20x_pek_resume)
> #ifdef CONFIG_PM_SLEEP
> .resume_noirq = axp20x_pek_resume_noirq,
> #endif
>
next prev parent reply other threads:[~2020-01-15 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 5:12 [PATCH v2 0/2] Input: axp20x-pek wakeup enablement Samuel Holland
2020-01-15 5:12 ` [PATCH v2 1/2] Input: axp20x-pek - Respect userspace wakeup configuration Samuel Holland
2020-01-15 10:50 ` Hans de Goede [this message]
2020-01-22 6:04 ` Dmitry Torokhov
2020-01-15 5:12 ` [PATCH v2 2/2] Input: axp20x-pek - Enable wakeup for all AXP variants Samuel Holland
2020-01-22 6:04 ` Dmitry Torokhov
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=674932c7-c120-092f-0255-5fa94925155d@redhat.com \
--to=hdegoede@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=samuel@sholland.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;
as well as URLs for NNTP newsgroup(s).