From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH v2] dt-bindings: serial: imx: clarify rs485 support usage Date: Tue, 3 Jul 2018 17:10:40 -0600 Message-ID: <20180703231040.GA5749@rob-hp-laptop> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Baruch Siach Cc: devicetree@vger.kernel.org, linux-serial@vger.kernel.org, Greg Kroah-Hartman , Sascha Hauer , NXP Linux Team , Pengutronix Kernel Team , Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= , Fabio Estevam , Shawn Guo , linux-arm-kernel@lists.infradead.org, Lothar =?iso-8859-1?Q?Wa=DFmann?= List-Id: devicetree@vger.kernel.org On Thu, Jun 28, 2018 at 10:25:32AM +0300, Baruch Siach wrote: > The i.MX UART peripheral uses the RST_B signal as input, and CTS_B as s/RST_B/RTS_B/ > output. This is just like the DCE role in RS-232. This is true > regardless of the "DTE mode" setting of this peripheral. > = > As a result, rs485 support hardware must use the CTS_B signal to control > the RS-485 transceiver. This is in contrast to generic rs485 kernel > code, documentation, and DT property names that consistently refer to > the RTS as transceiver control signal. > = > Add a note in the DT binding document about that, to reduce the > confusion somewhat. > = > Signed-off-by: Baruch Siach > --- > v2: Fix commit log typos (Lothar Wa=DFmann) > --- > Documentation/devicetree/bindings/serial/fsl-imx-uart.txt | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) With that, Reviewed-by: Rob Herring