From: Oleksij Rempel <o.rempel@pengutronix.de>
To: barebox@lists.infradead.org, david@protonic.nl
Cc: Oleksij Rempel <o.rempel@pengutronix.de>
Subject: [PATCH v5 10/12] ARM: dts: protonic: lanmcu: use UART_CTS instead of GPIO based CTS
Date: Thu, 20 Aug 2020 09:34:52 +0200 [thread overview]
Message-ID: <20200820073454.17500-11-o.rempel@pengutronix.de> (raw)
In-Reply-To: <20200820073454.17500-1-o.rempel@pengutronix.de>
Sync it with Protonic PLYBAS board to have same, reproducible behavior
on all boards.
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
---
arch/arm/dts/imx6dl-lanmcu.dts | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/arm/dts/imx6dl-lanmcu.dts b/arch/arm/dts/imx6dl-lanmcu.dts
index 65f6cbf395..42f8c91ece 100644
--- a/arch/arm/dts/imx6dl-lanmcu.dts
+++ b/arch/arm/dts/imx6dl-lanmcu.dts
@@ -201,7 +201,7 @@
fsl,pins = <
MX6QDL_PAD_EIM_D26__UART2_RX_DATA 0x1b0b1
MX6QDL_PAD_EIM_D27__UART2_TX_DATA 0x1b0b1
- MX6QDL_PAD_EIM_D28__GPIO3_IO28 0x130b1
+ MX6QDL_PAD_EIM_D28__UART2_CTS_B 0x130b1
>;
};
@@ -209,7 +209,7 @@
fsl,pins = <
MX6QDL_PAD_EIM_D24__UART3_TX_DATA 0x1b0b1
MX6QDL_PAD_EIM_D25__UART3_RX_DATA 0x1b0b1
- MX6QDL_PAD_EIM_D30__GPIO3_IO30 0x130b1
+ MX6QDL_PAD_EIM_D30__UART3_CTS_B 0x130b1
>;
};
@@ -320,7 +320,6 @@
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_uart2>;
linux,rs485-enabled-at-boot-time;
- rts-gpios = <&gpio3 28 GPIO_ACTIVE_HIGH>;
status = "okay";
};
@@ -328,7 +327,6 @@
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_uart3>;
linux,rs485-enabled-at-boot-time;
- rts-gpios = <&gpio3 30 GPIO_ACTIVE_HIGH>;
status = "okay";
};
--
2.28.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-08-20 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 7:34 [PATCH v5 00/12] prepare Protonic board code for mainline Oleksij Rempel
2020-08-20 7:34 ` [PATCH v5 01/12] of: base: register DT root as device Oleksij Rempel
2020-08-20 7:34 ` [PATCH v5 02/12] gpiolib: add gpio_array_to_id helper to get ID out of GPIO array Oleksij Rempel
2020-08-20 7:34 ` [PATCH v5 03/12] common: console_common: add of_console_get_by_alias() helper Oleksij Rempel
2020-08-20 7:34 ` [PATCH v5 04/12] of: of_device_get_match_compatible() helper Oleksij Rempel
2020-08-20 7:34 ` [PATCH v5 05/12] ARM: protonic-imx6: port Protonic specific board code Oleksij Rempel
2020-08-20 7:34 ` [PATCH v5 06/12] ARM: dts: unify barebox and barebox, env partitions for all Protonic boards Oleksij Rempel
2020-08-20 7:34 ` [PATCH v5 07/12] ARM: dts: imx6q-prti6q: add pstore/ramoops node Oleksij Rempel
2020-08-20 7:34 ` [PATCH v5 08/12] ARM: dts: protonic: lanmcu: add eMMC partition table Oleksij Rempel
2020-08-20 7:34 ` [PATCH v5 09/12] ARM: dts: protonic: add fixed clock for the FEC node Oleksij Rempel
2020-08-20 7:34 ` Oleksij Rempel [this message]
2020-08-20 7:34 ` [PATCH v5 11/12] ARM: dts: protonic: properly define PHY nodes on lanmcu and plym2m boards Oleksij Rempel
2020-08-20 7:34 ` [PATCH v5 12/12] ARM: dts: protonic: lanmcu: add uart-has-rtscts to enable rs485 functionality Oleksij Rempel
2020-08-24 6:51 ` [PATCH v5 00/12] prepare Protonic board code for mainline Sascha Hauer
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=20200820073454.17500-11-o.rempel@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=david@protonic.nl \
/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