From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Richard Leitner <richard.leitner@linux.dev>
Cc: "David R. Piegdon" <lkml@p23q.org>,
linux-tegra@vger.kernel.org, Dmitry Osipenko <digetx@gmail.com>,
Mikko Perttunen <mperttunen@nvidia.com>,
Nicolas Chauvet <kwizart@gmail.com>,
Jiri Slaby <jirislaby@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial <linux-serial@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] serial8250 on tegra hsuart: recover from spurious interrupts due to tegra2 silicon bug
Date: Thu, 22 Dec 2022 12:30:14 +0200 (EET) [thread overview]
Message-ID: <e48e8030-f15e-fe5b-84b7-44406937e51@linux.intel.com> (raw)
In-Reply-To: <Y3tUWPCVnauLeuG2@skidata.com>
On Mon, 21 Nov 2022, Richard Leitner wrote:
> Hi,
>
> On Fri, Jul 13, 2018 at 11:32:42AM +0000, David R. Piegdon wrote:
> > Hi,
> > a while back I sent a few mails regarding spurious interrupts in the
> > UARTA (hsuart) block of the Tegra2 SoC, when using the 8250 driver for
> > it instead of the hsuart driver. After going down a pretty deep
> > debugging/testing hole, I think I found a patch that fixes the issue. So
> > far testing in a reboot-cycle suggests that the error frequency dropped
> > from >3% of all reboots to at least <0.05% of all reboots. Tests
> > continue to run over the weekend.
> >
> > The patch below already is a second iteration; the first did not reset
> > the MCR or contain the lines below '// clear interrupts'. This resulted
> > in no more spurious interrupts, but in a few % of spurious interrupts
> > that were recovered the UART block did not receive any characters any
> > more. So further resetting was required to fully reacquire operational
> > state of the UART block.
> >
> > I'd love any comments/suggestions on this!
>
> I'd like to follow up on this ancient patch as we are using it
> successfully for a few years with different kernel versions on a
> tegra20 SOM (tamonten) now and I'm currently cleaning up our tree.
>
> David, have you done any work in regarding this issue since 2018?
>
> What would be needed to get this solution mainline?
It seems that the code would belong to ->handle_irq() rather than
8250_core. Do the affected device belong under 8250_tegra.c? If they do,
then just create .handle_irq for it and detect this condition there after
call to serial8250_handle_irq().
> The recipient of this mail are from the initial thread [1] and
> a current get_maintainers.pl run.
>
> regards;rl
>
> [1] https://patchwork.ozlabs.org/project/linux-tegra/patch/4676ea34-69ce-5422-1ded-94218b89f7d9@p23q.org/
>
> >
> > Cheers,
> >
> > David
> >
> > diff --git a/drivers/tty/serial/8250/8250_core.c b/drivers/tty/serial/8250/8250_core.c
> > index e8819aa20415..1d76eebefd4e 100644
> > --- a/drivers/tty/serial/8250/8250_core.c
> > +++ b/drivers/tty/serial/8250/8250_core.c
> > @@ -140,6 +140,38 @@ static irqreturn_t serial8250_interrupt(int irq, void *dev_id)
> > "serial8250: too much work for irq%d\n", irq);
> > break;
> > }
> > +
> > +#ifdef CONFIG_ARCH_TEGRA_2x_SOC
> > + if (!handled && (port->type == PORT_TEGRA)) {
> > + /*
> > + * Fix Tegra 2 CPU silicon bug where sometimes
> > + * "TX holding register empty" interrupts result in a
> > + * bad (metastable?) state in Tegras HSUART IP core.
> > + * Only way to recover seems to be to reset all
> > + * interrupts as well as the TX queue and the MCR.
> > + * But we don't want to loose any outgoing characters,
> > + * so only do it if the RX and TX queues are empty.
> > + */
> > + unsigned char lsr = port->serial_in(port, UART_LSR);
serial_lsr_in(), make sure you take the port's lock btw.
> > + const unsigned char fifo_empty_mask =
> > + (UART_LSR_TEMT | UART_LSR_THRE);
> > + if (((lsr & (UART_LSR_DR | fifo_empty_mask)) ==
> > + fifo_empty_mask)) {
uart_lsr_tx_empty(lsr) && !(lsr & UART_LSR_DR)
fifo_empty_mask can be dropped.
--
i.
> > + port->serial_out(port, UART_IER, 0);
> > + port->serial_out(port, UART_MCR, 0);
> > + serial8250_clear_and_reinit_fifos(up);
> > + port->serial_out(port, UART_MCR, up->mcr);
> > + port->serial_out(port, UART_IER, up->ier);
> > + // clear interrupts
> > + serial_port_in(port, UART_LSR);
> > + serial_port_in(port, UART_RX);
> > + serial_port_in(port, UART_IIR);
> > + serial_port_in(port, UART_MSR);
> > + up->lsr_saved_flags = 0;
> > + up->msr_saved_flags = 0;
> > + }
> > + }
> > +#endif
> > } while (l != end);
> >
> > spin_unlock(&i->lock);
>
prev parent reply other threads:[~2022-12-22 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4676ea34-69ce-5422-1ded-94218b89f7d9@p23q.org>
2022-11-21 10:35 ` [PATCH] serial8250 on tegra hsuart: recover from spurious interrupts due to tegra2 silicon bug Richard Leitner
[not found] ` <73C64EC3-3F03-426F-833B-CC9FBA9205D8@p23q.org>
2022-12-22 7:07 ` Richard Leitner
2022-12-22 10:30 ` Ilpo Järvinen [this message]
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=e48e8030-f15e-fe5b-84b7-44406937e51@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=digetx@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kwizart@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lkml@p23q.org \
--cc=mperttunen@nvidia.com \
--cc=richard.leitner@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).