From: Fred Lamer <shark.engs@gmail.com>
To: shawnguo@kernel.org, s.hauer@pengutronix.de,
linux-arm-kernel@lists.infradead.org
Cc: kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com
Subject: [PATCH] Add UART4 pinmux in imx28.dtsi
Date: Tue, 23 Nov 2021 22:11:48 -0500 [thread overview]
Message-ID: <ce8e541e-c026-09b1-65a4-9ee7565be7a2@gmail.com> (raw)
From 56d6c6e70d4142e76ed6b69e8292af25ae7d315d Mon Sep 17 00:00:00 2001
From: Fred Lamer <shark.engs@gmail.com>
Date: Tue, 23 Nov 2021 21:43:53 -0500
Subject: [PATCH] Add UART4 pinmux in imx28.dtsi:
To: linux-arm-kernel@lists.infradead.org,
shawnguo@kernel.org,
s.hauer@pengutronix.de
Cc: kernel@pengutronix.de,
festevam@gmail.com,
linux-imx@nxp.com
- Added missing UART4 pinmux in the common imx28.dtsi device tree
include file.
Signed-off-by: Fred Lamer <shark.engs@gmail.com>
---
arch/arm/boot/dts/imx28.dtsi | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.dtsi
index 94dfbf5b3f34..426e497c2ff4 100644
--- a/arch/arm/boot/dts/imx28.dtsi
+++ b/arch/arm/boot/dts/imx28.dtsi
@@ -424,6 +424,17 @@ MX28_PAD_AUART0_RTS__AUART4_TX
fsl,pull-up = <MXS_PULL_DISABLE>;
};
+ auart4_2pins_c: auart4@2 {
+ reg = <2>;
+ fsl,pinmux-ids = <
+ MX28_PAD_SAIF0_BITCLK__AUART4_RX
+ MX28_PAD_SAIF0_SDATA0__AUART4_TX
+ >;
+ fsl,drive-strength = <MXS_DRIVE_4mA>;
+ fsl,voltage = <MXS_VOLTAGE_HIGH>;
+ fsl,pull-up = <MXS_PULL_DISABLE>;
+ };
+
mac0_pins_a: mac0@0 {
reg = <0>;
fsl,pinmux-ids = <
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2021-11-24 3:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ce8e541e-c026-09b1-65a4-9ee7565be7a2@gmail.com \
--to=shark.engs@gmail.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).