mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kendall Willis <k-willis@ti.com>
To: Markus Schneider-Pargmann <msp@baylibre.com>, <nm@ti.com>,
	<vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <d-gole@ti.com>, <vishalm@ti.com>, <sebin.francis@ti.com>,
	<khilman@baylibre.com>, <a-kaur@ti.com>
Subject: Re: [PATCH 1/3] arm64: dts: ti: k3-am62x-sk-common: Enable Main UART wakeup
Date: Tue, 9 Sep 2025 14:03:54 -0500	[thread overview]
Message-ID: <5eab6ae7-a343-4101-8ae3-fccd5f7ef85c@ti.com> (raw)
In-Reply-To: <DCO4T9E3SGQ5.1J2ARMXFB9ONJ@baylibre.com>

On 9/9/25 03:37, Markus Schneider-Pargmann wrote:
> On Tue Sep 9, 2025 at 10:35 AM CEST, Markus Schneider-Pargmann wrote:
>> On Thu Sep 4, 2025 at 11:28 PM CEST, 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.
>>>
>>> Signed-off-by: Kendall Willis <k-willis@ti.com>
>>> ---
>>>   .../arm64/boot/dts/ti/k3-am62x-sk-common.dtsi | 24 +++++++++++++++----
>>>   1 file changed, 20 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi b/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi
>>> index 13e1d36123d51..72801cf890d20 100644
>>> --- a/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi
>>> +++ b/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi
>>> @@ -163,14 +163,26 @@ &phy_gmii_sel {
>>>   
>>>   &main_pmx0 {
>>>   	/* First pad number is ALW package and second is AMC package */
>>> -	main_uart0_pins_default: main-uart0-default-pins {
>>> +	main_uart0_tx_pins_default: main-uart0-tx-default-pins {
>>>   		bootph-all;
>>>   		pinctrl-single,pins = <
>>> -			AM62X_IOPAD(0x1c8, PIN_INPUT, 0) /* (D14/A13) UART0_RXD */
>>>   			AM62X_IOPAD(0x1cc, PIN_OUTPUT, 0) /* (E14/E11) UART0_TXD */
>>>   		>;
>>>   	};
>>>   
>>> +	main_uart0_rx_pins_default: main-uart0-rx-default-pins {
>>> +		bootph-all;
>>> +		pinctrl-single,pins = <
>>> +			AM62X_IOPAD(0x1c8, PIN_INPUT, 0) /* (D14/A13) UART0_RXD */
>>> +		>;
>>> +	};
>>> +
>>> +	main_uart0_rx_pins_wakeup: main-uart0-rx-wakeup-pins {
>>> +		pinctrl-single,pins = <
>>> +			AM62X_IOPAD(0x1c8, PIN_INPUT | PIN_WKUP_EN, 0) /* (D14/A13) UART0_RXD */
>>> +		>;
>>> +	};
>>> +
>>>   	main_uart1_pins_default: main-uart1-default-pins {
>>>   		bootph-pre-ram;
>>>   		pinctrl-single,pins = <
>>> @@ -342,8 +354,12 @@ &wkup_uart0 {
>>>   &main_uart0 {
>>>   	bootph-all;
>>>   	status = "okay";
>>> -	pinctrl-names = "default";
>>> -	pinctrl-0 = <&main_uart0_pins_default>;
>>> +	pinctrl-names = "default", "wakeup";
>>
>> I think you may need to add this to the DT binding of the uart device
>> as well.
> 
> Nevermind, I just saw your other series, can you please mention the
> other series as a dependency in the cover letter?

Yes, I will make the dependency clear in the cover letter.

> 
>>
>> Best
>> Markus
>>
>>> +	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>;
>>>   };
>>>   
>>>   &main_uart1 {
> 


  reply	other threads:[~2025-09-09 19:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04 21:28 [PATCH 0/3] arm64: dts: ti: k3-am62: Support " Kendall Willis
2025-09-04 21:28 ` [PATCH 1/3] arm64: dts: ti: k3-am62x-sk-common: Enable " Kendall Willis
2025-09-09  8:35   ` Markus Schneider-Pargmann
2025-09-09  8:37     ` Markus Schneider-Pargmann
2025-09-09 19:03       ` Kendall Willis [this message]
2025-09-04 21:28 ` [PATCH 2/3] arm64: dts: ti: k3-am62a7-sk: " Kendall Willis
2025-09-04 21:28 ` [PATCH 3/3] arm64: dts: ti: k3-am62p5-sk: " Kendall Willis
2025-09-05  2:32 ` [PATCH 0/3] arm64: dts: ti: k3-am62: Support " Rob Herring (Arm)
2025-09-09 22:41 ` 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=5eab6ae7-a343-4101-8ae3-fccd5f7ef85c@ti.com \
    --to=k-willis@ti.com \
    --cc=a-kaur@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=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

all inboxes | Powered by JetHome®