Linux Serial subsystem development
 help / color / mirror / Atom feed
From: Ryan Wilbur <rwilbur633@gmail.com>
To: ilpo.jarvinen@linux.intel.com
Cc: andriy.shevchenko@linux.intel.com, gregkh@linuxfoundation.org,
	hvilleneuve@dimonoff.com, jirislaby@kernel.org,
	john.ogness@linutronix.de, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org, m.felsch@pengutronix.de,
	rwilbur633@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] serial: 8250: clear a stuck RX-timeout interrupt with an empty FIFO
Date: Tue, 21 Jul 2026 16:37:51 -0300	[thread overview]
Message-ID: <20260721193751.22760-1-rwilbur633@gmail.com> (raw)
In-Reply-To: <c8a74142-5704-5ad3-3504-946bf3496cfc@linux.intel.com>

> I suspect Andy meant you should put this into hw specific file into a
> hw-specific handle_irq. That could be setup in 8250_of.c, it already
> seems to do something like that for some specific type.

Thanks. I'll move the fix out of 8250_port.c into a PORT_LPC3220
handle_irq, wired up in 8250_of.c the same way fsl8250_handle_irq is,
with the handler logic following dw8250_handle_irq's empty-FIFO
RX-timeout read.

> (8250_dw include check for LSR_BI bit and this one doesn't seem
> include that bit, not sure if that's an oversight or intentional
> difference [...])

The missing LSR_BI check was an oversight, I'll gate on
!(LSR & (UART_LSR_DR | UART_LSR_BI)) to match dw.

> So 3rd alternative would be to add e.g. UART_BUG_SPURIOUSRXTO but again
> there are the per driver variations. [...] definitely cleaner approach
> than copy-pasting this code around.

I'll go with the per device handler over the UART_BUG_SPURIOUSRXTO
callback because I can only test LPC32xx and I'm not comfortable touching
drivers I can't explicitly test against.

      reply	other threads:[~2026-07-21 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 13:11 [PATCH v2] serial: 8250: clear a stuck RX-timeout interrupt with an empty FIFO Ryan Wilbur
2026-07-20 14:20 ` Ilpo Järvinen
2026-07-21 19:37   ` Ryan Wilbur [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=20260721193751.22760-1-rwilbur633@gmail.com \
    --to=rwilbur633@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hvilleneuve@dimonoff.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jirislaby@kernel.org \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=m.felsch@pengutronix.de \
    --cc=stable@vger.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