From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Samuel Holland <samuel@sholland.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@siol.net>,
devicetree@vger.kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev,
Ondrej Jirman <megous@megous.com>
Subject: Re: [RERESEND PATCH v3] Input: sun4i-lradc-keys - Add wakup support
Date: Wed, 17 Nov 2021 21:55:45 -0800 [thread overview]
Message-ID: <YZXq4Z/7HHNtn2bj@google.com> (raw)
In-Reply-To: <20211118033013.43116-1-samuel@sholland.org>
Hi,
On Wed, Nov 17, 2021 at 09:30:13PM -0600, Samuel Holland wrote:
> From: Ondrej Jirman <megous@megous.com>
>
> Allow the driver to wake the system on key press if the "wakeup-source"
> property is provided in the device tree. Using the LRADC as a wakeup
> source requires keeping the AVCC domain active during sleep. Since this
> has a nontrivial impact on power consumption (sometimes doubling it),
> disable the LRADC wakeup source by default.
>
> Acked-by: Maxime Ripard <mripard@kernel.org>
> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
> Signed-off-by: Ondrej Jirman <megous@megous.com>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
> ---
>
> Changes since resend v3:
> - An entirely different, but equivalent, DT binding patch was merged,
> so there is only one patch left...
>
> Changes since v2:
> - Dropped unnecessary pr_err in platform_get_irq() error path
> - Dropped patch 3 (DT update) as it was merged
> - Added Acked-by/Reviewed-by tags
>
> Changes since v1:
> - Add requisite DT binding change
> - Only add wakeup capability if "wakeup-source" is present
> - Warn but do not error out if setting the wake IRQ fails
> - Add "wakeup-source" property to PinePhone device tree
>
> ---
> drivers/input/keyboard/sun4i-lradc-keys.c | 20 ++++++++++++++++----
> 1 file changed, 16 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/input/keyboard/sun4i-lradc-keys.c b/drivers/input/keyboard/sun4i-lradc-keys.c
> index 4a796bed48ac..af1683d68c8c 100644
> --- a/drivers/input/keyboard/sun4i-lradc-keys.c
> +++ b/drivers/input/keyboard/sun4i-lradc-keys.c
> @@ -22,6 +22,8 @@
> #include <linux/module.h>
> #include <linux/of_platform.h>
> #include <linux/platform_device.h>
> +#include <linux/pm_wakeirq.h>
> +#include <linux/pm_wakeup.h>
> #include <linux/regulator/consumer.h>
> #include <linux/slab.h>
>
> @@ -226,8 +228,7 @@ static int sun4i_lradc_probe(struct platform_device *pdev)
> {
> struct sun4i_lradc_data *lradc;
> struct device *dev = &pdev->dev;
> - int i;
> - int error;
> + int error, i, irq;
>
> lradc = devm_kzalloc(dev, sizeof(struct sun4i_lradc_data), GFP_KERNEL);
> if (!lradc)
> @@ -272,8 +273,11 @@ static int sun4i_lradc_probe(struct platform_device *pdev)
> if (IS_ERR(lradc->base))
> return PTR_ERR(lradc->base);
>
> - error = devm_request_irq(dev, platform_get_irq(pdev, 0),
> - sun4i_lradc_irq, 0,
> + irq = platform_get_irq(pdev, 0);
> + if (irq < 0)
> + return irq;
> +
> + error = devm_request_irq(dev, irq, sun4i_lradc_irq, 0,
> "sun4i-a10-lradc-keys", lradc);
> if (error)
> return error;
> @@ -282,6 +286,14 @@ static int sun4i_lradc_probe(struct platform_device *pdev)
> if (error)
> return error;
>
> + if (device_property_read_bool(dev, "wakeup-source")) {
> + device_set_wakeup_capable(dev, true);
> +
> + error = dev_pm_set_wake_irq(dev, irq);
> + if (error)
> + dev_warn(dev, "Failed to set wake IRQ\n");
Should we make it
else
device_set_wakeup_capable(dev, true);
?
Thanks.
--
Dmitry
prev parent reply other threads:[~2021-11-18 5:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 3:30 [RERESEND PATCH v3] Input: sun4i-lradc-keys - Add wakup support Samuel Holland
2021-11-18 5:55 ` Dmitry Torokhov [this message]
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=YZXq4Z/7HHNtn2bj@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=jernej.skrabec@siol.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=megous@megous.com \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--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).