From: Frank Li <Frank.li@nxp.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 07/10] arm64: dts: imx8mp-skov: configure uart1 for RS485
Date: Thu, 19 Dec 2024 12:42:56 -0500 [thread overview]
Message-ID: <Z2RbINlmO9UL+MPH@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20241219-skov-dt-updates-v1-7-38bf80dc22df@pengutronix.de>
On Thu, Dec 19, 2024 at 08:25:31AM +0100, Ahmad Fatoum wrote:
> uart1 TX, RX and RTS signals go off the base board and to a RS485
> transceiver. Describe this in the device tree.
Look like it is not related what your did in this patch.
Add uart-has-rtscts in uart1 to ... (because ....)
Frank
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> arch/arm64/boot/dts/freescale/imx8mp-skov-reva.dtsi | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-skov-reva.dtsi b/arch/arm64/boot/dts/freescale/imx8mp-skov-reva.dtsi
> index 7ae686d37dda..bce23d62cd27 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mp-skov-reva.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8mp-skov-reva.dtsi
> @@ -404,6 +404,13 @@ &uart1 {
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_uart1>;
> status = "okay";
> + /*
> + * While there is no CTS line, the property "uart-has-rtscts" is still
> + * the right thing to do to enable the UART to do RS485. In RS485-Mode
> + * CTS isn't used anyhow and there is no dedicated property
> + * "uart-has-rts-but-no-cts".
> + */
> + uart-has-rtscts;
> };
>
> &uart2 {
> @@ -618,6 +625,8 @@ pinctrl_uart1: uart1grp {
> MX8MP_IOMUXC_UART1_RXD__UART1_DCE_RX 0x140
> MX8MP_IOMUXC_UART1_TXD__UART1_DCE_TX 0x140
> MX8MP_IOMUXC_UART3_RXD__UART1_DTE_RTS 0x140
> + /* CTS pin is not connected, but needed as workaround */
what' means here! what's problem to be workaround?
> + MX8MP_IOMUXC_UART3_TXD__UART1_DTE_CTS 0x140
> >;
> };
>
>
> --
> 2.39.5
>
next prev parent reply other threads:[~2024-12-19 17:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 7:25 [PATCH 00/10] arm64: dts: imx8mp-skov: flesh out device trees Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 01/10] arm64: dts: imx8mp-skov: correct PMIC board limits Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 02/10] arm64: dts: imx8mp-skov: operate CPU at 850 mV by default Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 03/10] arm64: dts: imx8mp-skov: use I2C5 for DDC Ahmad Fatoum
2024-12-19 17:34 ` Frank Li
2024-12-19 17:43 ` Ahmad Fatoum
2024-12-19 19:27 ` Frank Li
2025-01-06 15:27 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 04/10] arm64: dts: imx8mp-skov: describe HDMI display pipeline Ahmad Fatoum
2024-12-19 17:35 ` Frank Li
2024-12-19 17:40 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 05/10] dt-bindings: display/lvds-codec: add ti,sn65lvds822 Ahmad Fatoum
2024-12-31 1:04 ` Rob Herring (Arm)
2024-12-19 7:25 ` [PATCH 06/10] arm64: dts: imx8mp-skov: describe LVDS display pipeline Ahmad Fatoum
2024-12-19 17:37 ` Frank Li
2024-12-19 17:45 ` Ahmad Fatoum
2024-12-19 19:24 ` Frank Li
2025-01-06 15:36 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 07/10] arm64: dts: imx8mp-skov: configure uart1 for RS485 Ahmad Fatoum
2024-12-19 17:42 ` Frank Li [this message]
2024-12-19 17:47 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 08/10] arm64: dts: imx8mp-skov: describe mains fail detection Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 09/10] arm64: dts: imx8mp-skov: fix phy-mode Ahmad Fatoum
2024-12-19 17:45 ` Frank Li
2024-12-19 17:49 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 10/10] arm64: dts: imx8mp-skov: increase I2C clock frequency for RTC Ahmad Fatoum
2024-12-19 17:47 ` Frank Li
2024-12-19 17:51 ` Ahmad Fatoum
2024-12-19 19:16 ` Frank Li
2024-12-20 9:12 ` Ahmad Fatoum
2024-12-20 15:38 ` Frank Li
2025-01-06 15:59 ` Ahmad Fatoum
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=Z2RbINlmO9UL+MPH@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=a.fatoum@pengutronix.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh@kernel.org \
--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