From: Nishanth Menon <nm@ti.com>
To: Bhavya Kapoor <b-kapoor@ti.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-j722s-evm: Describe main_uart5
Date: Sat, 24 Aug 2024 13:14:34 -0500 [thread overview]
Message-ID: <20240824181434.53m2ik3ozvc74pjf@dormitory> (raw)
In-Reply-To: <20240822053538.10475-1-b-kapoor@ti.com>
On 11:05-20240822, Bhavya Kapoor wrote:
> main_uart5 in J722S platform is used by the firmware. Thus,
what platform? what firmware?
> describe it for completeness, adding the pinmux and mark
> it as reserved.
>
> Signed-off-by: Bhavya Kapoor <b-kapoor@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-j722s-evm.dts | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
> index 24e9f2ea509b..5addf1c0afc2 100644
> --- a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
> +++ b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
> @@ -20,6 +20,7 @@ / {
> aliases {
> serial0 = &wkup_uart0;
> serial2 = &main_uart0;
> + serial3 = &main_uart5;
> mmc0 = &sdhci0;
> mmc1 = &sdhci1;
> };
> @@ -211,6 +212,13 @@ 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 */
> + >;
> + };
> +
> vdd_sd_dv_pins_default: vdd-sd-dv-default-pins {
> pinctrl-single,pins = <
> J722S_IOPAD(0x0120, PIN_INPUT, 7) /* (F27) MMC2_CMD.GPIO0_70 */
> @@ -330,6 +338,12 @@ &main_uart0 {
> bootph-all;
> };
>
> +&main_uart5 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&main_uart5_pins_default>;
Document specifically why reserved.
> + status = "reserved";
> +};
> +
> &mcu_pmx0 {
>
> mcu_mcan0_pins_default: mcu-mcan0-default-pins {
> --
> 2.34.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2024-08-24 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 5:35 [PATCH] arm64: dts: ti: k3-j722s-evm: Describe main_uart5 Bhavya Kapoor
2024-08-24 18:14 ` Nishanth Menon [this message]
2024-08-27 8:48 ` Bhavya Kapoor
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=20240824181434.53m2ik3ozvc74pjf@dormitory \
--to=nm@ti.com \
--cc=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=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