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 v4 2/2] Input: gpio-keys - support wakeup pinctrl state on suspend
Date: Thu, 22 Oct 2026 09:28:30 +0200 [thread overview]
Message-ID: <DMB6UH6R51LW.1TRHK4HV4GGE9@baylibre.com> (raw)
In-Reply-To: <20261005-upstream-gpio-wakeup-v4-2-96f092de4690@ti.com>
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
On Mon Oct 5, 2026 at 10:47 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>
Reviewed-by: Markus Schneider-Pargmann (TI) <msp@baylibre.com>
Best
Markus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 289 bytes --]
next prev parent reply other threads:[~2026-10-22 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 20:47 [PATCH v4 0/2] Input: gpio-keys - support wakeup pinctrl state Kendall Willis
2026-10-05 20:47 ` [PATCH v4 1/2] dt-bindings: input: gpio-keys: add pinctrl states Kendall Willis
2026-10-05 20:47 ` [PATCH v4 2/2] Input: gpio-keys - support wakeup pinctrl state on suspend Kendall Willis
2026-10-22 7:28 ` Markus Schneider-Pargmann [this message]
2026-10-19 12:59 ` [PATCH v4 0/2] Input: gpio-keys - support wakeup pinctrl state Francesco Dolcini
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=DMB6UH6R51LW.1TRHK4HV4GGE9@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®