From: Nishanth Menon <nm@ti.com>
To: Kendall Willis <k-willis@ti.com>
Cc: 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>, <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-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 4/5] arm64: dts: ti: k3-am62p5-sk: Enable Main UART wakeup
Date: Mon, 5 Jan 2026 07:52:02 -0600 [thread overview]
Message-ID: <20260105135202.vnamexwl3afdt4cw@deferral> (raw)
In-Reply-To: <20251230-b4-uart-daisy-chain-dts-v2-4-fa5257ec54bb@ti.com>
On 20:38-20251230, Kendall Willis wrote:
> The Main UART can resume from suspend to RAM states when PIN_WKUP_EN
> is enabled. Add the necessary pins needed to wakeup the system. Add the
> system idle states that the Main UART can wakeup the system from.
Is the tx and rx pin register states both lost? I wonder why during
"wakeup" we set PIN_WKUP_EN ? is'nt that supposed to be set while
entering "suspend" state?
if the tx pin register state is not lost, then all we need to do is
play with the rx pin state (and leave pinctrl-0 as is)?
>
> Signed-off-by: Kendall Willis <k-willis@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-am62p5-sk.dts | 24 ++++++++++++++++++++----
> 1 file changed, 20 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts b/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts
> index ef719c6334fc094f01d9e8185992f2f58320e17d..96bba65f4f16792834567324db6f7f2bdee7bc06 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts
> @@ -328,14 +328,26 @@ AM62PX_IOPAD(0x0164, PIN_INPUT, 0) /* (A20) RGMII2_TX_CTL */
> bootph-all;
> };
>
> - main_uart0_pins_default: main-uart0-default-pins {
> + main_uart0_tx_pins_default: main-uart0-tx-default-pins {
> pinctrl-single,pins = <
> - AM62PX_IOPAD(0x1c8, PIN_INPUT, 0) /* (A22) UART0_RXD */
> AM62PX_IOPAD(0x1cc, PIN_OUTPUT, 0) /* (B22) UART0_TXD */
> >;
> bootph-all;
> };
>
> + main_uart0_rx_pins_default: main-uart0-rx-default-pins {
> + pinctrl-single,pins = <
> + AM62PX_IOPAD(0x1c8, PIN_INPUT, 0) /* (A22) UART0_RXD */
> + >;
> + bootph-all;
> + };
> +
> + main_uart0_rx_pins_wakeup: main-uart0-rx-wakeup-pins {
> + pinctrl-single,pins = <
> + AM62PX_IOPAD(0x1c8, PIN_INPUT | PIN_WKUP_EN, 0) /* (A22) UART0_RXD */
> + >;
> + };
> +
> main_uart1_pins_default: main-uart1-default-pins {
> pinctrl-single,pins = <
> AM62PX_IOPAD(0x0194, PIN_INPUT, 2) /* (D25) MCASP0_AXR3.UART1_CTSn */
> @@ -692,8 +704,12 @@ partition@3fc0000 {
> };
>
> &main_uart0 {
> - pinctrl-names = "default";
> - pinctrl-0 = <&main_uart0_pins_default>;
> + pinctrl-names = "default", "wakeup";
> + pinctrl-0 = <&main_uart0_tx_pins_default>, <&main_uart0_rx_pins_default>;
> + pinctrl-1 = <&main_uart0_tx_pins_default>, <&main_uart0_rx_pins_wakeup>;
> + wakeup-source = <&system_deep_sleep>,
> + <&system_mcu_only>,
> + <&system_standby>;
> status = "okay";
> bootph-all;
> };
>
> --
> 2.34.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
https://ti.com/opensource
next prev parent reply other threads:[~2026-01-05 13:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 2:38 [PATCH v2 0/5] arm64: dts: ti: k3-am62: Support Main UART wakeup Kendall Willis
2025-12-31 2:38 ` [PATCH v2 1/5] arm64: dts: ti: k3-am62l: Define possible system states Kendall Willis
2025-12-31 2:38 ` [PATCH v2 2/5] arm64: dts: ti: k3-am62x-sk-common: Enable Main UART wakeup Kendall Willis
2025-12-31 2:38 ` [PATCH v2 3/5] arm64: dts: ti: k3-am62a7-sk: " Kendall Willis
2025-12-31 2:38 ` [PATCH v2 4/5] arm64: dts: ti: k3-am62p5-sk: " Kendall Willis
2026-01-05 13:52 ` Nishanth Menon [this message]
2026-01-05 22:06 ` Kendall Willis
2026-01-06 11:57 ` Nishanth Menon
2025-12-31 2:38 ` [PATCH v2 5/5] arm64: dts: ti: k3-am62l3-evm: " Kendall Willis
2026-01-05 10:33 ` [PATCH v2 0/5] arm64: dts: ti: k3-am62: Support " Markus Schneider-Pargmann
2026-01-05 13:17 ` Dhruva Gole
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=20260105135202.vnamexwl3afdt4cw@deferral \
--to=nm@ti.com \
--cc=a-kaur@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=k-willis@ti.com \
--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=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