From: "Ionut Nechita (Wind River)" <ionut.nechita@windriver.com>
To: ilpo.jarvinen@linux.intel.com, gregkh@linuxfoundation.org
Cc: stable@vger.kernel.org, linux-serial@vger.kernel.org,
andriy.shevchenko@linux.intel.com, ionut.nechita@windriver.com,
chris.friesen@windriver.com
Subject: [REQUEST] Backport 8250_dw BUSY deassert series to 6.12.y stable
Date: Fri, 8 May 2026 18:16:14 +0300 [thread overview]
Message-ID: <20260508151614.498810-1-ionut.nechita@windriver.com> (raw)
From: Ionut Nechita <ionut.nechita@windriver.com>
Hi Ilpo, Greg,
We're running kernel 6.12 (LTS) on production systems with DesignWare
8250 UARTs and are hitting the BUSY assertion issue that your recent
series addresses in 6.18:
Ilpo Järvinen (7):
serial: 8250: Protect LCR write in shutdown
serial: 8250_dw: Avoid unnecessary LCR writes
serial: 8250: Add serial8250_handle_irq_locked()
serial: 8250_dw: Rework dw8250_handle_irq() locking and IIR handling
serial: 8250_dw: Rework IIR_NO_INT handling to stop interrupt storm
serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY
serial: 8250_dw: Ensure BUSY is deasserted
Patch 7/7 has Cc: stable, but it depends on patches 1-6 for the new
infrastructure (serial8250_handle_irq_locked(), the reworked locking in
dw8250_handle_irq(), etc.).
Could the full series be nominated for 6.12.y stable backport? Or if
that's too invasive for stable, could you advise on the minimal subset
that would allow patch 7 to apply cleanly on 6.12?
We've attempted a standalone backport of patch 7 (squashing the
necessary helpers from 8250_port.c), but the IRQ handler refactoring
in patches 3-5 changes the locking model significantly, and we'd
rather carry the maintainer-blessed version than risk introducing
subtle races.
Our environment:
- Kernel: 6.12.57-rt/6.12.87-rt (PREEMPT_RT)
- Hardware: Intel platforms with DW APB UART (snps,dw-apb-uart)
- Symptom: LCR writes silently ignored under Rx load, causing
baud rate / framing mismatches after set_termios
We are available to test any backport candidates on our hardware.
Thanks,
Ionut
---
next reply other threads:[~2026-05-08 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 15:16 Ionut Nechita (Wind River) [this message]
2026-05-08 15:21 ` [REQUEST] Backport 8250_dw BUSY deassert series to 6.12.y stable Greg KH
2026-05-08 15:46 ` Ionut Nechita (Wind River)
2026-05-08 17:13 ` 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=20260508151614.498810-1-ionut.nechita@windriver.com \
--to=ionut.nechita@windriver.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chris.friesen@windriver.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-serial@vger.kernel.org \
--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