From: Kendall Willis <k-willis@ti.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>
Cc: <d-gole@ti.com>, <vishalm@ti.com>, <sebin.francis@ti.com>,
<msp@baylibre.com>, <khilman@baylibre.com>, <a-kaur@ti.com>,
<s-kochidanadu@ti.com>, <linux-kernel@vger.kernel.org>,
<linux-serial@vger.kernel.org>, Kendall Willis <k-willis@ti.com>
Subject: [PATCH] serial: 8250: omap: set out-of-band wakeup if wakeup pinctrl exists
Date: Tue, 30 Dec 2025 15:24:51 -0600 [thread overview]
Message-ID: <20251230-uart-wakeup-v1-1-13f1bb905f14@ti.com> (raw)
In TI K3 SoCs, I/O daisy chaining is used to allow wakeup from UART when
the UART controller is off. Set UART device as wakeup capable using
out-of-band wakeup if the 'wakeup' pinctrl state exists and the device may
wakeup.
Signed-off-by: Kendall Willis <k-willis@ti.com>
---
Implementation
--------------
This patch is intended to be implemented along with the following
series. This patch has no dependencies on any of the other series:
1. "pmdomain: ti_sci: handle wakeup constraint for out-of-band wakeup":
Skips setting constraints for wakeup sources that have out-of-band
wakeup capability.
https://github.com/kwillis01/linux/commits/v6.19/uart-daisy-chain/pmdomain
2. "serial: 8250: omap: set out-of-band wakeup if wakeup pinctrl exists"
(this patch): Implements out-of-band wakeup from the UARTs for TI K3
SoCs
https://github.com/kwillis01/linux/tree/v6.19/uart-daisy-chain/uart-wakeup
3. "arm64: dts: ti: k3-am62: Support Main UART wakeup": Implements the
functionality to wakeup the system from the Main UART
https://github.com/kwillis01/linux/tree/b4/uart-daisy-chain-dts
Testing
-------
Tested on a AM62P SK EVM board with all series and dependencies
implemented. Suspend/resume verified with the Main UART wakeup source
by entering a keypress on the console.
This github branch has all the necessary patches to test the series
using v6.19-rc1:
https://github.com/kwillis01/linux/tree/v6.19/uart-daisy-chain/all
---
drivers/tty/serial/8250/8250_omap.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/tty/serial/8250/8250_omap.c b/drivers/tty/serial/8250/8250_omap.c
index 9e49ef48b851bf6cd3b04a77a4d0d7b4e064dc5f..6a5722b722650c1710e79fb76fc1a01cdeccc68f 100644
--- a/drivers/tty/serial/8250/8250_omap.c
+++ b/drivers/tty/serial/8250/8250_omap.c
@@ -1363,6 +1363,8 @@ static int omap8250_select_wakeup_pinctrl(struct device *dev,
if (!device_may_wakeup(dev))
return 0;
+ device_set_out_band_wakeup(dev);
+
return pinctrl_select_state(priv->pinctrl, priv->pinctrl_wakeup);
}
---
base-commit: f8f9c1f4d0c7a64600e2ca312dec824a0bc2f1da
change-id: 20251230-uart-wakeup-00faeac7c994
Best regards,
--
Kendall Willis <k-willis@ti.com>
next reply other threads:[~2025-12-30 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 21:24 Kendall Willis [this message]
2026-01-16 5:40 ` [PATCH] serial: 8250: omap: set out-of-band wakeup if wakeup pinctrl exists Dhruva Gole
2026-01-16 13:16 ` Greg Kroah-Hartman
2026-01-16 15:37 ` Kendall Willis
2026-01-16 15:47 ` Greg Kroah-Hartman
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=20251230-uart-wakeup-v1-1-13f1bb905f14@ti.com \
--to=k-willis@ti.com \
--cc=a-kaur@ti.com \
--cc=d-gole@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=s-kochidanadu@ti.com \
--cc=sebin.francis@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