public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bhavya Kapoor <b-kapoor@ti.com>
To: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>, <conor+dt@kernel.org>,
	<krzk+dt@kernel.org>, <robh@kernel.org>, <kristo@kernel.org>,
	<vigneshr@ti.com>, <nm@ti.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-j722s-evm: Enable main_uart5
Date: Wed, 12 Jun 2024 12:10:40 +0530	[thread overview]
Message-ID: <d8b802dc-e65c-4b76-bfe0-a5b5c9dad472@ti.com> (raw)
In-Reply-To: <27a350e5-b3e0-427d-8897-89e1d34a4c00@ti.com>

Hi all, please ignore this patch as main_uart5 needs to be kept 
reserved. I will send another patch for the same

regards

On 28/05/24 4:38 pm, Bhavya Kapoor wrote:
>
> On 28/05/24 3:09 pm, Bhavya Kapoor wrote:
>> main_uart5 node defined in the SoC dtsi file is incomplete
>> and will not be functional unless it is extended with pinmux
>> information at board integration level.
>>
>> Thus, add pinmux for main_uart5 in the board dts file and
>> enable it to make it functional.
>>
>> Signed-off-by: Bhavya Kapoor <b-kapoor@ti.com>
>> ---
> Test Logs: 
> https://gist.github.com/a0498981/dc8b0cb670a5726eeb6c10f6de1f468e
>>   arch/arm64/boot/dts/ti/k3-j722s-evm.dts | 16 ++++++++++++++++
>>   1 file changed, 16 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts 
>> b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
>> index bf3c246d13d1..e3892a6f2fab 100644
>> --- a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
>> +++ b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
>> @@ -18,6 +18,7 @@ / {
>>       aliases {
>>           serial0 = &wkup_uart0;
>>           serial2 = &main_uart0;
>> +        serial3 = &main_uart5;
>>           mmc0 = &sdhci0;
>>           mmc1 = &sdhci1;
>>       };
>> @@ -142,6 +143,14 @@ J722S_IOPAD(0x01cc, PIN_OUTPUT, 0)    /* (B22) 
>> UART0_TXD */
>>           bootph-all;
>>       };
>>   +    main_uart5_pins_default: main-uart5-default-pins {
>> +        pinctrl-single,pins = <
>> +            J722S_IOPAD(0x0108, PIN_INPUT, 3)    /* (J27) UART5_RXD */
>> +            J722S_IOPAD(0x010c, PIN_OUTPUT, 3)    /* (H27) UART5_TXD */
>> +        >;
>> +        bootph-all;
>> +    };
>> +
>>       vdd_sd_dv_pins_default: vdd-sd-dv-default-pins {
>>           pinctrl-single,pins = <
>>               J722S_IOPAD(0x0120, PIN_INPUT, 7) /* (F27) 
>> MMC2_CMD.GPIO0_70 */
>> @@ -240,6 +249,13 @@ &main_uart0 {
>>       bootph-all;
>>   };
>>   +&main_uart5 {
>> +    pinctrl-names = "default";
>> +    pinctrl-0 = <&main_uart5_pins_default>;
>> +    status = "okay";
>> +    bootph-all;
>> +};
>> +
>>   &mcu_pmx0 {
>>         wkup_uart0_pins_default: wkup-uart0-default-pins {

      reply	other threads:[~2024-06-12  6:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28  9:39 [PATCH] arm64: dts: ti: k3-j722s-evm: Enable main_uart5 Bhavya Kapoor
2024-05-28  9:39 ` Bhavya Kapoor
2024-05-28 11:08 ` Bhavya Kapoor
2024-06-12  6:40   ` Bhavya Kapoor [this message]

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=d8b802dc-e65c-4b76-bfe0-a5b5c9dad472@ti.com \
    --to=b-kapoor@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=vigneshr@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