From: "Markus Schneider-Pargmann" <msp@baylibre.com>
To: "Kendall Willis" <k-willis@ti.com>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: <msp@baylibre.com>, <s-kochidanadu@ti.com>, <a-kaur@ti.com>,
<s-tripathi1@ti.com>, <vishalm@ti.com>,
<linux-input@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] Input: gpio-keys - support wakeup pinctrl state on suspend
Date: Wed, 30 Sep 2026 14:11:55 +0200 [thread overview]
Message-ID: <DLSN3HSWU044.10UYU9AQX2MV4@baylibre.com> (raw)
In-Reply-To: <20260925-upstream-gpio-wakeup-v2-2-6c5533356246@ti.com>
[-- Attachment #1: Type: text/plain, Size: 3039 bytes --]
On Fri Sep 25, 2026 at 11:52 PM CEST, Kendall Willis wrote:
> GPIO can be used as a wakeup source for TI K3 AM62 devices during
> suspend to RAM states. The GPIO controller is powered off in these
> states, so a wakeup enable flag must be set on the GPIO pin in the
> pinctrl in order to allow wakeup.
>
> If the device is wakeup enabled, select the wakeup pinctrl state on
> suspend and restore the default pinctrl state on resume.
>
> Signed-off-by: Kendall Willis <k-willis@ti.com>
> ---
> drivers/input/keyboard/gpio_keys.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/input/keyboard/gpio_keys.c b/drivers/input/keyboard/gpio_keys.c
> index 129fc4212a5ed126496b331ce626682d441c53bf..d3fbc9776ac8cbdc7349a28df990ee609edf9e59 100644
> --- a/drivers/input/keyboard/gpio_keys.c
> +++ b/drivers/input/keyboard/gpio_keys.c
> @@ -28,6 +28,7 @@
> #include <linux/of.h>
> #include <linux/of_irq.h>
> #include <linux/spinlock.h>
> +#include <linux/pinctrl/consumer.h>
> #include <dt-bindings/input/gpio-keys.h>
>
> struct gpio_button_data {
> @@ -60,6 +61,8 @@ struct gpio_keys_drvdata {
> struct input_dev *input;
> struct mutex disable_lock;
> unsigned short *keymap;
> + struct pinctrl *pinctrl;
> + struct pinctrl_state *pinctrl_wakeup;
> struct gpio_button_data data[];
> };
>
> @@ -884,6 +887,10 @@ static int gpio_keys_probe(struct platform_device *pdev)
> platform_set_drvdata(pdev, ddata);
> input_set_drvdata(input, ddata);
>
> + ddata->pinctrl = devm_pinctrl_get(dev);
> + if (!IS_ERR_OR_NULL(ddata->pinctrl))
Should this check for -EPROBE_DEFER and error out in that case?
Otherwise looks good to me.
Best
Markus
> + ddata->pinctrl_wakeup = pinctrl_lookup_state(ddata->pinctrl, "wakeup");
> +
> input->name = pdata->name ? : pdev->name;
> input->phys = "gpio-keys/input0";
> input->dev.parent = dev;
> @@ -1010,6 +1017,12 @@ gpio_keys_enable_wakeup(struct gpio_keys_drvdata *ddata)
> int error;
> int i;
>
> + if (!IS_ERR_OR_NULL(ddata->pinctrl_wakeup)) {
> + error = pinctrl_select_state(ddata->pinctrl, ddata->pinctrl_wakeup);
> + if (error)
> + return error;
> + }
> +
> for (i = 0; i < ddata->pdata->nbuttons; i++) {
> bdata = &ddata->data[i];
> if (bdata->button->wakeup) {
> @@ -1023,6 +1036,9 @@ gpio_keys_enable_wakeup(struct gpio_keys_drvdata *ddata)
> return 0;
>
> err_out:
> + if (!IS_ERR_OR_NULL(ddata->pinctrl_wakeup))
> + pinctrl_pm_select_default_state(ddata->input->dev.parent);
> +
> while (i--) {
> bdata = &ddata->data[i];
> if (bdata->button->wakeup)
> @@ -1039,6 +1055,9 @@ gpio_keys_disable_wakeup(struct gpio_keys_drvdata *ddata)
> struct gpio_button_data *bdata;
> int i;
>
> + if (!IS_ERR_OR_NULL(ddata->pinctrl_wakeup))
> + pinctrl_pm_select_default_state(ddata->input->dev.parent);
> +
> for (i = 0; i < ddata->pdata->nbuttons; i++) {
> bdata = &ddata->data[i];
> bdata->suspended = false;
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 289 bytes --]
next prev parent reply other threads:[~2026-09-30 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 21:52 [PATCH v2 0/2] Input: gpio-keys - support wakeup pinctrl state Kendall Willis
2026-09-25 21:52 ` [PATCH v2 1/2] dt-bindings: input: gpio-keys: add pinctrl states Kendall Willis
2026-09-25 21:52 ` [PATCH v2 2/2] Input: gpio-keys - support wakeup pinctrl state on suspend Kendall Willis
2026-09-30 12:11 ` Markus Schneider-Pargmann [this message]
2026-09-30 20:30 ` Kendall Willis
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=DLSN3HSWU044.10UYU9AQX2MV4@baylibre.com \
--to=msp@baylibre.com \
--cc=a-kaur@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=k-willis@ti.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s-kochidanadu@ti.com \
--cc=s-tripathi1@ti.com \
--cc=vishalm@ti.com \
/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®