Linux Serial subsystem development
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: s.hauer@pengutronix.de, u.kleine-koenig@pengutronix.de,
	baruch@tkos.co.il
Cc: linux-arm-kernel@lists.infradead.org, linux-serial@vger.kernel.org
Subject: serial: imx: half-duplex RS485 operation with RTS active low
Date: Mon, 16 Apr 2018 11:14:32 +0200	[thread overview]
Message-ID: <0e88706a05a302201be396d2f03c3e9e@agner.ch> (raw)

Hi,

Using upstream I noticed that RS-485 does not work in the default
configuration for our platforms (Toradex Apalis/Colibri). Closer
debugging shows that it is related to "serial: imx: default to half
duplex rs485".

We use the i.MX UART in DTE mode and control the RS-485 transceiver
using the RTS signal in low-active mode.

	uart-has-rtscts;
	fsl,dte-mode;
	linux,rs485-enabled-at-boot-time;
	rs485-rts-active-low;

Using this setting leads to the RTS signal not getting asserted (the
oscilloscope only shows a very short fluke before the start bit is
sent).

However, using

	uart-has-rtscts;
	fsl,dte-mode;
	linux,rs485-enabled-at-boot-time;
	rs485-rts-active-low;
	rs485-rx-during-tx;

Asserts the RTS signal low active just fine...

Is this a known problem? Any idea where that could come from? It looks
as if the receiver part is actually enabling RTS...?

Also, isn't enabling RX even in half-duplex mode quite common in order
to detect collisions?

--
Stefan

             reply	other threads:[~2018-04-16  9:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16  9:14 Stefan Agner [this message]
2018-04-16  9:22 ` serial: imx: half-duplex RS485 operation with RTS active low Uwe Kleine-König
2018-04-16 10:29   ` Stefan Agner
2018-04-16 13:01     ` Stefan Agner
2018-04-16 13:42       ` Uwe Kleine-König
2018-04-16 16:12         ` Stefan Agner
2018-04-16 18:02           ` Uwe Kleine-König
2018-04-16  9:54 ` Einar Vading
2018-04-16  9:57   ` Einar Vading
2018-04-16 10:35   ` Stefan Agner

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=0e88706a05a302201be396d2f03c3e9e@agner.ch \
    --to=stefan@agner.ch \
    --cc=baruch@tkos.co.il \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=u.kleine-koenig@pengutronix.de \
    /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