From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Martin Fuzzey <martin.fuzzey@flowbird.group>
Cc: linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <festevam@gmail.com>, Marek Vasut <marex@denx.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: serial: imx: fix rs485 rx after tx
Date: Fri, 16 Jun 2023 15:40:29 +0300 (EEST) [thread overview]
Message-ID: <c3e02d8-fba8-5ae3-15f3-fe378567932@linux.intel.com> (raw)
In-Reply-To: <20230616104838.2729694-1-martin.fuzzey@flowbird.group>
[-- Attachment #1: Type: text/plain, Size: 2964 bytes --]
On Fri, 16 Jun 2023, Martin Fuzzey wrote:
> Since commit 79d0224f6bf2 ("tty: serial: imx: Handle RS485 DE signal
> active high") RS485 reception no longer works after a transmission.
>
> The following scenario shows the problem:
> 1) Open a port in RS485 mode
> 2) Receive data from remote (OK)
> 3) Transmit data to remote (OK)
> 4) Receive data from remote (Nothing received)
>
> In RS485 mode, imx_uart_start_tx() calls imx_uart_stop_rx() and, when the
> transmission is complete, imx_uart_stop_tx() calls imx_uart_start_rx().
>
> Since the above commit imx_uart_stop_rx() now sets the loopback bit but
> imx_uart_start_rx() does not clear it causing the hardware to remain in
> loopback mode and not receive external data.
>
> Fix this by moving the existing loopback disable code to a helper function
> and calling it from imx_uart_start_rx() too.
>
> Fixes: 79d0224f6bf2 ("tty: serial: imx: Handle RS485 DE signal active high")
> Cc: stable@vger.kernel.org
> Signed-off-by: Martin Fuzzey <martin.fuzzey@flowbird.group>
> ---
> drivers/tty/serial/imx.c | 18 +++++++++++++-----
> 1 file changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/tty/serial/imx.c b/drivers/tty/serial/imx.c
> index c5e17569c3ad..3fe8ff241522 100644
> --- a/drivers/tty/serial/imx.c
> +++ b/drivers/tty/serial/imx.c
> @@ -369,6 +369,16 @@ static void imx_uart_soft_reset(struct imx_port *sport)
> sport->idle_counter = 0;
> }
>
> +static void imx_uart_disable_loopback_rs485(struct imx_port *sport)
> +{
> + unsigned int uts;
> +
> + /* See SER_RS485_ENABLED/UTS_LOOP comment in imx_uart_probe() */
> + uts = imx_uart_readl(sport, imx_uart_uts_reg(sport));
> + uts &= ~UTS_LOOP;
> + imx_uart_writel(sport, uts, imx_uart_uts_reg(sport));
> +}
> +
> /* called with port.lock taken and irqs off */
> static void imx_uart_start_rx(struct uart_port *port)
> {
> @@ -390,6 +400,7 @@ static void imx_uart_start_rx(struct uart_port *port)
> /* Write UCR2 first as it includes RXEN */
> imx_uart_writel(sport, ucr2, UCR2);
> imx_uart_writel(sport, ucr1, UCR1);
> + imx_uart_disable_loopback_rs485(sport);
> }
>
> /* called with port.lock taken and irqs off */
> @@ -1422,7 +1433,7 @@ static int imx_uart_startup(struct uart_port *port)
> int retval;
> unsigned long flags;
> int dma_is_inited = 0;
> - u32 ucr1, ucr2, ucr3, ucr4, uts;
> + u32 ucr1, ucr2, ucr3, ucr4;
>
> retval = clk_prepare_enable(sport->clk_per);
> if (retval)
> @@ -1521,10 +1532,7 @@ static int imx_uart_startup(struct uart_port *port)
> imx_uart_writel(sport, ucr2, UCR2);
> }
>
> - /* See SER_RS485_ENABLED/UTS_LOOP comment in imx_uart_probe() */
> - uts = imx_uart_readl(sport, imx_uart_uts_reg(sport));
> - uts &= ~UTS_LOOP;
> - imx_uart_writel(sport, uts, imx_uart_uts_reg(sport));
> + imx_uart_disable_loopback_rs485(sport);
>
> spin_unlock_irqrestore(&sport->port.lock, flags);
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
--
i.
next prev parent reply other threads:[~2023-06-16 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 10:47 Martin Fuzzey
2023-06-16 11:16 ` Marek Vasut
2023-07-06 22:11 ` Marek Vasut
2023-06-16 12:40 ` Ilpo Järvinen [this message]
2023-08-07 9:48 ` Sebastien Laveze
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=c3e02d8-fba8-5ae3-15f3-fe378567932@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=marex@denx.de \
--cc=martin.fuzzey@flowbird.group \
--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
all inboxes | Powered by JetHome®