From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org,
qianfan Zhao <qianfanguijin@163.com>,
Adriana Nicolae <adriana@arista.com>,
linux-kernel@vger.kernel.org, "Bandal,
Shankar" <shankar.bandal@intel.com>,
"Murthy, Shanth" <shanth.murthy@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 3/7] serial: 8250: Add serial8250_handle_irq_locked()
Date: Wed, 28 Jan 2026 15:20:07 +0200 [thread overview]
Message-ID: <aXoNB7pnQMpPd8xY@smile.fi.intel.com> (raw)
In-Reply-To: <20260128105301.1869-4-ilpo.jarvinen@linux.intel.com>
On Wed, Jan 28, 2026 at 12:52:57PM +0200, Ilpo Järvinen wrote:
> 8250_port exports serial8250_handle_irq() to HW specific 8250 drivers.
> It takes port's lock within but a HW specific 8250 driver may want to
> take port's lock itself, do something, and then call the generic
> handler in 8250_port but to do that, the caller has to release port's
> lock for no good reason.
>
> Introduce serial8250_handle_irq_locked() which a HW specific driver can
> call while already holding port's lock.
>
> As this is new export, put it straight into a namespace (where all 8250
> exports should eventually be moved).
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
...
> +void serial8250_handle_irq_locked(struct uart_port *port, unsigned int iir);
> int serial8250_handle_irq(struct uart_port *port, unsigned int iir);
Looking at these I think at some point we can move to 'u32 iir'.
> u16 serial8250_rx_chars(struct uart_8250_port *up, u16 lsr);
> void serial8250_read_char(struct uart_8250_port *up, u16 lsr);
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-01-28 13:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 10:52 [PATCH v2 0/7] 8250 DW UART fixes when under constant Rx pressure Ilpo Järvinen
2026-01-28 10:52 ` [PATCH v2 1/7] serial: 8250: Protect LCR write in shutdown Ilpo Järvinen
2026-01-28 13:12 ` Andy Shevchenko
2026-01-28 10:52 ` [PATCH v2 2/7] serial: 8250_dw: Avoid unnecessary LCR writes Ilpo Järvinen
2026-01-28 13:36 ` Andy Shevchenko
2026-01-28 10:52 ` [PATCH v2 3/7] serial: 8250: Add serial8250_handle_irq_locked() Ilpo Järvinen
2026-01-28 13:20 ` Andy Shevchenko [this message]
2026-01-28 13:26 ` Ilpo Järvinen
2026-01-28 10:52 ` [PATCH v2 4/7] serial: 8250_dw: Rework dw8250_handle_irq() locking and IIR handling Ilpo Järvinen
2026-01-28 13:48 ` Andy Shevchenko
2026-01-28 14:00 ` Ilpo Järvinen
2026-01-28 10:52 ` [PATCH v2 5/7] serial: 8250_dw: Rework IIR_NO_INT handling to stop interrupt storm Ilpo Järvinen
2026-01-28 14:03 ` Andy Shevchenko
2026-01-28 10:53 ` [PATCH v2 6/7] serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY Ilpo Järvinen
2026-01-28 14:37 ` Andy Shevchenko
2026-01-28 15:07 ` Ilpo Järvinen
2026-01-28 10:53 ` [PATCH v2 7/7] serial: 8250_dw: Ensure BUSY is deasserted Ilpo Järvinen
2026-01-28 15:42 ` Andy Shevchenko
2026-01-30 12:44 ` Ilpo Järvinen
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=aXoNB7pnQMpPd8xY@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=adriana@arista.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=qianfanguijin@163.com \
--cc=shankar.bandal@intel.com \
--cc=shanth.murthy@intel.com \
--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