public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Sherry Sun <sherry.sun@nxp.com>
Cc: gregkh@linuxfoundation.org, jirislaby@kernel.org,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-imx@nxp.com
Subject: Re: [PATCH] tty: serial: imx: disable UCR4_OREN in .stop_rx()
Date: Tue, 23 Nov 2021 09:43:21 +0100	[thread overview]
Message-ID: <20211123084321.gpblxmqddn3kl44y@pengutronix.de> (raw)
In-Reply-To: <20211123075122.2cwhrdwrsyjgebnk@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 2224 bytes --]

Hello again,

On Tue, Nov 23, 2021 at 08:51:22AM +0100, Uwe Kleine-König wrote:
> On Tue, Nov 23, 2021 at 03:04:37PM +0800, Sherry Sun wrote:
> > From: Fugang Duan <fugang.duan@nxp.com>
> > 
> > Disable UCR4_OREN bit in .stop_rx() to avoid endless
> > interrupt happen while tty port is closing.
> > 
> > Signed-off-by: Fugang Duan <fugang.duan@nxp.com>
> > Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
> > ---
> >  drivers/tty/serial/imx.c | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/tty/serial/imx.c b/drivers/tty/serial/imx.c
> > index fb75e3e0d828..9ecaf051249d 100644
> > --- a/drivers/tty/serial/imx.c
> > +++ b/drivers/tty/serial/imx.c
> > @@ -486,18 +486,21 @@ static void imx_uart_stop_tx(struct uart_port *port)
> >  static void imx_uart_stop_rx(struct uart_port *port)
> >  {
> >  	struct imx_port *sport = (struct imx_port *)port;
> > -	u32 ucr1, ucr2;
> > +	u32 ucr1, ucr2, ucr4;
> >  
> >  	ucr1 = imx_uart_readl(sport, UCR1);
> >  	ucr2 = imx_uart_readl(sport, UCR2);
> > +	ucr4 = imx_uart_readl(sport, UCR4);
> >  
> >  	if (sport->dma_is_enabled) {
> >  		ucr1 &= ~(UCR1_RXDMAEN | UCR1_ATDMAEN);
> >  	} else {
> >  		ucr1 &= ~UCR1_RRDYEN;
> >  		ucr2 &= ~UCR2_ATEN;
> > +		ucr4 &= ~UCR4_OREN;
> >  	}
> >  	imx_uart_writel(sport, ucr1, UCR1);
> > +	imx_uart_writel(sport, ucr4, UCR4);
> 
> I don't understand this yet, but I guess this is just a matter of
> improving the commit log. How does the endless irq happen?
> 
> ... some time later after thinking and reading the driver source ...
> 
> Hmm, when the OR event is triggered the handler does
> 
> 	imx_uart_writel(sport, USR2_ORE, USR2);
> 
> and so clears the event. I would expect that this should be good enough
> to prevent an irq storm even if the receiver is disabled. Doesn't acking
> work with the receiver disabled?

One thing I forgot to mention:

If imx_uart_stop_rx() now clears UCR4_OREN, clearing in
imx_uart_shutdown() should probably be dropped.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-11-23  8:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23  7:04 [PATCH] tty: serial: imx: disable UCR4_OREN in .stop_rx() Sherry Sun
2021-11-23  7:51 ` Uwe Kleine-König
2021-11-23  8:43   ` Uwe Kleine-König [this message]
2021-11-23  9:05     ` 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=20211123084321.gpblxmqddn3kl44y@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --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