From: Nishanth Menon <nm@ti.com>
To: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Nishanth Menon <nm@ti.com>, Udit Kumar <u-kumar1@ti.com>,
Nitin Yadav <n-yadav@ti.com>,
Neha Malcom Francis <n-francis@ti.com>,
Sinthu Raja <sinthu.raja@ti.com>,
Thejasvi Konduru <t-konduru@ti.com>,
Dasnavis Sabiya <sabiya.d@ti.com>
Subject: [PATCH 6/8] arm64: dts: ti: k3-am69-sk: Add mcu and wakeup uarts
Date: Fri, 2 Jun 2023 16:49:35 -0500 [thread overview]
Message-ID: <20230602214937.2349545-7-nm@ti.com> (raw)
In-Reply-To: <20230602214937.2349545-1-nm@ti.com>
Add wakeup and MCU uart. This allows the device tree usage in
bootloader and firmwares that can configure the same appropriately.
Signed-off-by: Nishanth Menon <nm@ti.com>
---
Depends on https://lore.kernel.org/linux-arm-kernel/20230503083143.32369-1-t-konduru@ti.com/
arch/arm64/boot/dts/ti/k3-am69-sk.dts | 31 +++++++++++++++++++++++++++
1 file changed, 31 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am69-sk.dts b/arch/arm64/boot/dts/ti/k3-am69-sk.dts
index ae41ff6249a1..409fcbaf0126 100644
--- a/arch/arm64/boot/dts/ti/k3-am69-sk.dts
+++ b/arch/arm64/boot/dts/ti/k3-am69-sk.dts
@@ -21,6 +21,8 @@ chosen {
};
aliases {
+ serial0 = &wkup_uart0;
+ serial1 = &mcu_uart0;
serial2 = &main_uart8;
mmc1 = &main_sdhci1;
i2c3 = &main_i2c0;
@@ -141,6 +143,22 @@ J784S4_IOPAD(0x0C4, PIN_INPUT, 7) /* (AD36) ECAP0_IN_APWM_OUT.GPIO0_49 */
};
&wkup_pmx2 {
+ wkup_uart0_pins_default: wkup-uart0-pins-default {
+ pinctrl-single,pins = <
+ J721S2_WKUP_IOPAD(0x070, PIN_INPUT, 0) /* (L37) WKUP_GPIO0_6.WKUP_UART0_CTSn */
+ J721S2_WKUP_IOPAD(0x074, PIN_INPUT, 0) /* (L36) WKUP_GPIO0_7.WKUP_UART0_RTSn */
+ J721S2_WKUP_IOPAD(0x048, PIN_INPUT, 0) /* (K35) WKUP_UART0_RXD */
+ J721S2_WKUP_IOPAD(0x04c, PIN_INPUT, 0) /* (K34) WKUP_UART0_TXD */
+ >;
+ };
+
+ mcu_uart0_pins_default: mcu-uart0-pins-default {
+ pinctrl-single,pins = <
+ J784S4_WKUP_IOPAD(0x08c, PIN_INPUT, 0) /* (K38) WKUP_GPIO0_13.MCU_UART0_RXD */
+ J784S4_WKUP_IOPAD(0x088, PIN_OUTPUT, 0) /* (J37) WKUP_GPIO0_12.MCU_UART0_TXD */
+ >;
+ };
+
mcu_cpsw_pins_default: mcu-cpsw-pins-default {
pinctrl-single,pins = <
J784S4_WKUP_IOPAD(0x02c, PIN_INPUT, 0) /* (A35) MCU_RGMII1_RD0 */
@@ -166,6 +184,19 @@ J784S4_WKUP_IOPAD(0x030, PIN_INPUT, 0) /* (B35) MCU_MDIO0_MDIO */
};
};
+&wkup_uart0 {
+ /* Firmware usage */
+ status = "reserved";
+ pinctrl-names = "default";
+ pinctrl-0 = <&wkup_uart0_pins_default>;
+};
+
+&mcu_uart0 {
+ status = "okay";
+ pinctrl-names = "default";
+ pinctrl-0 = <&mcu_uart0_pins_default>;
+};
+
&main_uart8 {
status = "okay";
pinctrl-names = "default";
--
2.40.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-02 21:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 21:49 [PATCH 0/8] arm64: dts: ti: k3-j784s4/am69: Add uart, i2c, eeprom, misc Nishanth Menon
2023-06-02 21:49 ` [PATCH 1/8] arm64: dts: ti: k3-j784s4-evm: Fix main_i2c0 alias Nishanth Menon
2023-06-02 21:49 ` [PATCH 2/8] arm64: dts: ti: k3-j784s4-evm: Add mcu and wakeup uarts Nishanth Menon
2023-06-02 21:49 ` [PATCH 3/8] arm64: dts: ti: k3-j784s4-evm: Enable wakeup_i2c0 and eeprom Nishanth Menon
2023-06-02 21:49 ` [PATCH 4/8] arm64: dts: ti: k3-am69-sk: Fix main_i2c0 alias Nishanth Menon
2023-06-02 21:49 ` [PATCH 5/8] arm64: dts: ti: k3-am69-sk: Enable mcu network port Nishanth Menon
2023-06-02 21:49 ` Nishanth Menon [this message]
2023-06-02 21:49 ` [PATCH 7/8] arm64: dts: ti: k3-am69-sk: Enable wakeup_i2c0 and eeprom Nishanth Menon
2023-06-02 21:49 ` [PATCH 8/8] arm64: dts: ti: k3-am69-sk: Add pinmux for RPi Header Nishanth Menon
2023-06-03 11:09 ` [PATCH 0/8] arm64: dts: ti: k3-j784s4/am69: Add uart, i2c, eeprom, misc Nishanth Menon
2023-06-13 14:00 ` Kumar, Udit
2023-06-15 13:28 ` Vignesh Raghavendra
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=20230602214937.2349545-7-nm@ti.com \
--to=nm@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=n-francis@ti.com \
--cc=n-yadav@ti.com \
--cc=robh+dt@kernel.org \
--cc=sabiya.d@ti.com \
--cc=sinthu.raja@ti.com \
--cc=t-konduru@ti.com \
--cc=u-kumar1@ti.com \
--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