From: Bhavya Kapoor <b-kapoor@ti.com>
To: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Cc: <s-sinha@ti.com>, <ankurbaranwal@ti.com>, <b-kapoor@ti.com>,
<u-kumar1@ti.com>, <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: [PATCH] arm64: dts: ti: k3-j722s-evm: Add pinmux for RPi Header
Date: Mon, 28 Oct 2024 13:54:26 +0530 [thread overview]
Message-ID: <20241028082426.1551816-1-b-kapoor@ti.com> (raw)
Add pinmux required to bring out the i2c and gpios on
40-pin RPi expansion header on the J722S EVM.
Signed-off-by: Bhavya Kapoor <b-kapoor@ti.com>
Signed-off-by: Shreyash Sinha <s-sinha@ti.com>
---
Rebased To - next-20241025
arch/arm64/boot/dts/ti/k3-j722s-evm.dts | 62 +++++++++++++++++++++++++
1 file changed, 62 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
index a00f4a7d20d9..7dce021a8a3c 100644
--- a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
+++ b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
@@ -359,6 +359,32 @@ audio_ext_refclk1_pins_default: audio-ext-refclk1-default-pins {
J722S_IOPAD(0x00a0, PIN_OUTPUT, 1) /* (N24) GPMC0_WPn.AUDIO_EXT_REFCLK1 */
>;
};
+
+ rpi_header_gpio0_pins_default: rpi-header-gpio0-default-pins {
+ pinctrl-single,pins = <
+ J722S_IOPAD(0x094, PIN_INPUT, 7) /* (P26) GPIO0_36 */
+ J722S_IOPAD(0x088, PIN_INPUT, 7) /* (N22) GPIO0_33 */
+ J722S_IOPAD(0x0ac, PIN_INPUT, 7) /* (P21) GPIO0_42 */
+ J722S_IOPAD(0x0a8, PIN_INPUT, 7) /* (R27) GPIO0_41 */
+ >;
+ };
+
+ rpi_header_gpio1_pins_default: rpi-header-gpio1-default-pins {
+ pinctrl-single,pins = <
+ J722S_IOPAD(0x1b0, PIN_INPUT, 7) /* (F24) GPIO1_14 */
+ J722S_IOPAD(0x1ac, PIN_INPUT, 7) /* (C27) GPIO1_13 */
+ J722S_IOPAD(0x198, PIN_INPUT, 7) /* (A26) GPIO1_8 */
+ J722S_IOPAD(0x1a4, PIN_INPUT, 7) /* (D25) GPIO1_11 */
+ J722S_IOPAD(0x194, PIN_INPUT, 7) /* (A25) GPIO1_7 */
+ J722S_IOPAD(0x1b8, PIN_INPUT, 7) /* (C20) GPIO1_16 */
+ J722S_IOPAD(0x1a8, PIN_INPUT, 7) /* (C26) GPIO1_12 */
+ J722S_IOPAD(0x1a0, PIN_INPUT, 7) /* (F23) GPIO1_10 */
+ J722S_IOPAD(0x19c, PIN_INPUT, 7) /* (B25) GPIO1_9 */
+ J722S_IOPAD(0x1b4, PIN_INPUT, 7) /* (B20) GPIO1_15 */
+ J722S_IOPAD(0x1bc, PIN_INPUT, 7) /* (D20) GPIO1_17 */
+ J722S_IOPAD(0x1c0, PIN_INPUT, 7) /* (E19) GPIO1_18 */
+ >;
+ };
};
&cpsw3g {
@@ -387,6 +413,8 @@ &cpsw_port1 {
};
&main_gpio1 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&rpi_header_gpio1_pins_default>;
status = "okay";
};
@@ -443,6 +471,25 @@ J722S_MCU_IOPAD(0x050, PIN_INPUT_PULLUP, 0) /* (C6) WKUP_I2C1_SDA */
>;
bootph-all;
};
+
+ mcu_rpi_header_gpio0_pins_default: mcu-rpi-header-gpio0-default-pins {
+ pinctrl-single,pins = <
+ J722S_MCU_IOPAD(0x01c, PIN_INPUT, 7) /* (B5) MCU_GPIO0_7 */
+ J722S_MCU_IOPAD(0x020, PIN_INPUT, 7) /* (C5) MCU_GPIO0_8 */
+ J722S_MCU_IOPAD(0x00c, PIN_INPUT, 7) /* (B12) MCU_GPIO0_3 */
+ J722S_MCU_IOPAD(0x010, PIN_INPUT, 7) /* (C11) MCU_GPIO0_4 */
+ J722S_MCU_IOPAD(0x008, PIN_INPUT, 7) /* (A9) MCU_GPIO0_2 */
+ J722S_MCU_IOPAD(0x000, PIN_INPUT, 7) /* (C12) MCU_GPIO0_0 */
+ J722S_MCU_IOPAD(0x004, PIN_INPUT, 7) /* (A10) MCU_GPIO0_1 */
+ >;
+ };
+
+ mcu_i2c0_pins_default: mcu-i2c0-default-pins {
+ pinctrl-single,pins = <
+ J722S_MCU_IOPAD(0x048, PIN_INPUT, 0) /* (E11) MCU_I2C0_SDA */
+ J722S_MCU_IOPAD(0x044, PIN_INPUT, 0) /* (B13) MCU_I2C0_SCL */
+ >;
+ };
};
&wkup_uart0 {
@@ -810,5 +857,20 @@ &main_mcan0 {
};
&mcu_gpio0 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&mcu_rpi_header_gpio0_pins_default>;
+ status = "okay";
+};
+
+&main_gpio0 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&rpi_header_gpio0_pins_default>;
+ status = "okay";
+};
+
+&mcu_i2c0 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&mcu_i2c0_pins_default>;
+ clock-frequency = <400000>;
status = "okay";
};
--
2.34.1
next reply other threads:[~2024-10-28 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 8:24 Bhavya Kapoor [this message]
2024-11-07 6:13 ` 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=20241028082426.1551816-1-b-kapoor@ti.com \
--to=b-kapoor@ti.com \
--cc=ankurbaranwal@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=s-sinha@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
all inboxes | Powered by JetHome®