public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: imx@lists.linux.dev
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Roelf-Erik Carsjens <rca@thorsis.com>,
	Josua Mayer <josua@solid-run.com>
Subject: rts-gpios support in fsl_lpuart driver?
Date: Tue, 10 Feb 2026 12:48:05 +0100	[thread overview]
Message-ID: <20260210-rearview-hungrily-536a95fc3385@thorsis.com> (raw)

Hello everyone,

we are currently experimenting with the SolidRun 8XLite SoM featuring
an i.MX 8XLite SoC on a custom base board.  Due to how our peripheral
hardware is connected we need to use rs485 with uart3, which has no
native soc controlled rts line.  On different SoCs you just use
'rts-gpios' in devicetree then, letting the kernel switch this line
through gpio.  Alas it does not work on this SoC, the RTS line is not
switched at all. :-/

According to my analysis the i.MX8 family has different variants using
different uarts with different drivers.  For the variants using the
imx.c driver, you find dts files using rts-gpios, but for variants
using the fsl_lpuart.c driver you find none.

The rts-gpios property is evaluated by the serial core in
`mctrl_gpio_init()` right?  And the actual switching is also done
through that mctrl_gpio interface, right?  As far as I understand the
source code, the serial core calls the .set_mctrl function pointer,
and then it is up to the driver what to do?  Some (like atmel_serial.c
and imx.c) call mctrl_gpio_set() in the function mapped to that
pointer, some (like fsl_lpuart.c) don't.  Correct so far?

Up to this point I'm somewhat confused this is no generic feature in
the core which works for any uart, but there's probably a reason for
that?  Maybe interaction with the actual uart registers in some way?

If it is like described, I'd say the fsl_lpuart driver currently just
does not support this usecase?  Is it possible to implement the
necessary things?  Is anybody already working on that?  I looked in my
mailing list archive and in the imx downstream kernel, but could not
find any hints.

Any advice welcome. :-)

Greets
Alex


             reply	other threads:[~2026-02-10 11:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 11:48 Alexander Dahl [this message]
2026-02-10 15:56 ` rts-gpios support in fsl_lpuart driver? Frank Li
2026-02-10 17:10   ` Manikanta guntupalli
2026-02-11  9:59   ` Sherry Sun

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=20260210-rearview-hungrily-536a95fc3385@thorsis.com \
    --to=ada@thorsis.com \
    --cc=imx@lists.linux.dev \
    --cc=josua@solid-run.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=rca@thorsis.com \
    /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