Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Sherry Sun <sherry.sun@nxp.com>, gregkh@linuxfoundation.org
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	imx@lists.linux.dev, shenwei.wang@nxp.com, frank.li@nxp.com
Subject: Re: [PATCH V2] tty: serial: fsl_lpuart: disable transmitter before changing RS485 related registers
Date: Tue, 11 Mar 2025 04:44:34 +0100	[thread overview]
Message-ID: <be728f1f-b9bd-4d42-8ecb-9505d558543c@kernel.org> (raw)
In-Reply-To: <20250311025550.1243569-1-sherry.sun@nxp.com>

On 11. 03. 25, 3:55, Sherry Sun wrote:
> According to the LPUART reference manual, TXRTSE and TXRTSPOL of MODIR
> register only can be changed when the transmitter is disabled.
> So disable the transmitter before changing RS485 related registers and
> re-enable it after the change is done.
> 
> Fixes: 67b01837861c ("tty: serial: lpuart: Add RS485 support for 32-bit uart flavour")
> Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
> ---
> Changes in V2:
> 1. Add TE bit polling read to ensure TE is really become 0 before proceeding.
> 2. Add Reviewed-by tag.
> ---
>   drivers/tty/serial/fsl_lpuart.c | 17 +++++++++++++++++
>   1 file changed, 17 insertions(+)
> 
> diff --git a/drivers/tty/serial/fsl_lpuart.c b/drivers/tty/serial/fsl_lpuart.c
> index 91d02c55c470..6b2f3a73a367 100644
> --- a/drivers/tty/serial/fsl_lpuart.c
> +++ b/drivers/tty/serial/fsl_lpuart.c
> @@ -1484,6 +1484,19 @@ static int lpuart32_config_rs485(struct uart_port *port, struct ktermios *termio
>   
>   	unsigned long modem = lpuart32_read(&sport->port, UARTMODIR)
>   				& ~(UARTMODIR_TXRTSPOL | UARTMODIR_TXRTSE);

This is unrelated, but why is the above ulong?

> +	u32 ctrl;
> +
> +	/* TXRTSE and TXRTSPOL only can be changed when transmitter is disabled. */
> +	ctrl = lpuart32_read(&sport->port, UARTCTRL);
> +	if (ctrl & UARTCTRL_TE) {
> +		/* wait transmit engin complete */

wait for the transmit engine to complete

> +		lpuart32_wait_bit_set(&sport->port, UARTSTAT, UARTSTAT_TC);

Both this ^^ and:

> +		lpuart32_write(&sport->port, ctrl & ~UARTCTRL_TE, UARTCTRL);
> +
> +		while (lpuart32_read(&sport->port, UARTCTRL) & UARTCTRL_TE)
> +			cpu_relax();

this ^^ are unbound loops in case the hardware gets mad :(.

Anyway, IIUC, after the TE clear from CTRL by the above write, the TE 
bit is really cleared by the HW from CTRL only after it is really 
disabled, so has to be checked?

> +	}
> +


thanks,
-- 
js
suse labs

  reply	other threads:[~2025-03-11  3:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11  2:55 [PATCH V2] tty: serial: fsl_lpuart: disable transmitter before changing RS485 related registers Sherry Sun
2025-03-11  3:44 ` Jiri Slaby [this message]
2025-03-11  6:28   ` 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=be728f1f-b9bd-4d42-8ecb-9505d558543c@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=frank.li@nxp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=imx@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=shenwei.wang@nxp.com \
    --cc=sherry.sun@nxp.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