From: Kendall Willis <k-willis@ti.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
"Tero Kristo" <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, "Dhruva Gole" <d-gole@ti.com>,
Bryan Brattlof <bb@ti.com>
Cc: <vishalm@ti.com>, <sebin.francis@ti.com>, <msp@baylibre.com>,
<khilman@baylibre.com>, <a-kaur@ti.com>, <s-kochidanadu@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Kendall Willis <k-willis@ti.com>
Subject: [PATCH 0/3] arm64: boot: dts: ti: k3-am62l: enable WKUP UART wakeup
Date: Tue, 30 Dec 2025 20:51:39 -0600 [thread overview]
Message-ID: <20251230-wkup-uart-wakeup-v1-0-cd6e15f8d956@ti.com> (raw)
K3 TI AM62L SoC supports wakeup from WKUP UART when the SoC is in the
DeepSleep low power mode. To enable WKUP UART the target-module device
tree node is enabled. The ti-sysc interconnect target module driver is
used to configure the the SYSCONFIG related registers to allow wakeup
from WKUP UART when the system is suspended. Refer to 14.7.2.5 UART in the
AM62L Techincal Reference Manual for registers referenced [1].
Previous TI SoCs configure the WKUP UART to wakeup from system suspend
using the ti-sysc interconnect target module driver. Refer to commit
ce27f7f9e328 ("arm64: dts: ti: k3-am62-wakeup: Configure ti-sysc for
wkup_uart0") for an example of this.
Testing
-------
Tested on AM62L EVM on v6.19-rc3. Suspend/resume verified with the WKUP
UART wakeup source by entering a keypress on the console.
[1] https://www.ti.com/lit/ug/sprujb4a/sprujb4a.pdf
Signed-off-by: Kendall Willis <k-willis@ti.com>
---
Kendall Willis (3):
arm64: dts: ti: k3-am62l: include WKUP_UART0 in wakeup peripheral window
arm64: boot: dts: ti: k3-am62l-wakeup: create label for target-module
arm64: boot: dts: ti: k3-am62l3-evm: enable WKUP UART wakeup from LPM
arch/arm64/boot/dts/ti/k3-am62l-wakeup.dtsi | 2 +-
arch/arm64/boot/dts/ti/k3-am62l.dtsi | 4 ++--
arch/arm64/boot/dts/ti/k3-am62l3-evm.dts | 4 ++++
3 files changed, 7 insertions(+), 3 deletions(-)
---
base-commit: 5dc233097d4f94776c0c3f6edfd7476281478dc3
change-id: 20251230-wkup-uart-wakeup-8bbc95aa8f8e
Best regards,
--
Kendall Willis <k-willis@ti.com>
next reply other threads:[~2025-12-31 2:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 2:51 Kendall Willis [this message]
2025-12-31 2:51 ` [PATCH 1/3] arm64: dts: ti: k3-am62l: include WKUP_UART0 in wakeup peripheral window Kendall Willis
2026-01-05 13:22 ` Dhruva Gole
2025-12-31 2:51 ` [PATCH 2/3] arm64: boot: dts: ti: k3-am62l-wakeup: create label for target-module Kendall Willis
2026-01-05 13:24 ` Dhruva Gole
2025-12-31 2:51 ` [PATCH 3/3] arm64: boot: dts: ti: k3-am62l3-evm: enable WKUP UART wakeup from LPM Kendall Willis
2026-01-05 13:25 ` Dhruva Gole
2026-01-05 13:55 ` Nishanth Menon
2026-01-05 22:10 ` Kendall Willis
2026-01-06 11:56 ` Nishanth Menon
2026-01-06 17:10 ` Kendall Willis
2026-01-05 14:01 ` Bryan Brattlof
2026-01-05 22:14 ` 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=20251230-wkup-uart-wakeup-v1-0-cd6e15f8d956@ti.com \
--to=k-willis@ti.com \
--cc=a-kaur@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-kochidanadu@ti.com \
--cc=sebin.francis@ti.com \
--cc=vigneshr@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