From: Jan Beulich <jbeulich@suse.com>
To: Oleksii Kurochko <oleksii.kurochko@gmail.com>
Cc: "Alistair Francis" <alistair.francis@wdc.com>,
"Connor Davis" <connojdavis@gmail.com>,
"Baptiste Le Duc" <baptiste.le-duc@vates.tech>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger@xenproject.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Zhang Zheng" <zhangzheng@iscas.ac.cn>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 1/2] xen/ns16550: detect and preserve UART_IER_UUE
Date: Mon, 12 Oct 2026 14:50:11 +0200 [thread overview]
Message-ID: <f5d4bb6c-69cd-45cc-badc-797ef9fbc96f@suse.com> (raw)
In-Reply-To: <1a6cdfbf-8116-48ca-b2cb-567e39fabe4f@gmail.com>
On 12.10.2026 11:20, Oleksii Kurochko wrote:
> On 10/10/26 5:14 AM, Zhang Zheng wrote:
>> XScale-compatible UARTs require UART_IER_UUE to remain set. Probe the
>> bit during setup and preserve it when enabling receive interrupts, so
>> the xscale/PXA UART remains operational after ns16550 takes over.
>>
>> Signed-off-by: Zhang Zheng <zhangzheng@iscas.ac.cn>
>> ---
>> xen/drivers/char/ns16550.c | 12 +++++++++++-
>> xen/include/xen/8250-uart.h | 1 +
>> 2 files changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/xen/drivers/char/ns16550.c b/xen/drivers/char/ns16550.c
>> index cdda28879e..c174465059 100644
>> --- a/xen/drivers/char/ns16550.c
>> +++ b/xen/drivers/char/ns16550.c
>> @@ -64,6 +64,7 @@ static struct ns16550 {
>> bool intr_works;
>> bool force_polling;
>> bool dw_usr_bsy;
>> + bool xscale;
>> #ifdef NS16550_PCI
>> /* PCI card parameters. */
>> bool pb_bdf_enable; /* if =1, pb-bdf effective, port behind bridge */
>> @@ -352,6 +353,14 @@ static void ns16550_setup_preirq(struct ns16550 *uart)
>> /* No interrupts. */
>> ns_write_reg(uart, UART_IER, 0);
>>
>> + uart->xscale = false;
>> + if ( !(ns_read_reg(uart, UART_IER) & UART_IER_UUE) )
>> + {
>> + ns_write_reg(uart, UART_IER, UART_IER_UUE);
>> + if ( ns_read_reg(uart, UART_IER) & UART_IER_UUE )
>> + uart->xscale = true;
>> + }
>> +
>
> This probe only checks whether IER bit 6 is writable, which isn't
> specific to XScale. On UARTs with an EFR (e.g. ST16C650, TI TL16C752,
> Exar XR17V35x) the upper IER bits become writable once EFR[4] (ECB) is
> set, and bit 6 is then the RTS interrupt enable. If ECB is already set
> when the probe runs, it would report XScale, and the driver would then
> keep the RTS interrupt enabled.
>
> Could the flag be derived from the compatible in ns16550_uart_dt_init()
> instead, the same way dw_usr_bsy is?
>
> uart->xscale = dt_device_is_compatible(dev, "intel,xscale-uart");
>
> That compatible would also need adding to ns16550_dt_match[]. The
> SpacemiT K1 nodes, for example, have no "ns16550a" fallback.
Are you suggesting that Linux'es XScale detection is flawed then, too?
>> @@ -446,7 +455,8 @@ static void ns16550_setup_postirq(struct ns16550 *uart)
>> UART_MCR, UART_MCR_OUT2 | UART_MCR_DTR | UART_MCR_RTS);
>>
>> /* Enable receive interrupts. */
>> - ns_write_reg(uart, UART_IER, UART_IER_ERDAI);
>> + ns_write_reg(uart, UART_IER,
>> + UART_IER_ERDAI | (uart->xscale ? UART_IER_UUE : 0));
>
> It seems like not all cases are covered. For example,
> ns16550_interrupt() writes 0 to IER when it switches to polling, which
> would turn off the UART on XScale. Am I missing something? If not then
> something like:
>
> static void ns_write_ier(const struct ns16550 *uart, uint8_t ier)
> {
> if ( uart->xscale )
> ier |= UART_IER_UUE;
>
> ns_write_reg(uart, UART_IER, ier);
> }
>
> would be needed, used in ns16550_setup_preirq(), ns16550_setup_postirq()
Yes, the more that as per Linux'es driver source, bit 4 may also need keeping
permanently set (not only for XScale, but apparently also for Tegra).
Jan
next prev parent reply other threads:[~2026-10-12 12:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 3:14 [PATCH v2 0/2] xen/ns16550: preserve UART operation across firmware handover Zhang Zheng
2026-10-10 3:14 ` [PATCH v2 1/2] xen/ns16550: detect and preserve UART_IER_UUE Zhang Zheng
2026-10-10 22:11 ` Baptiste Le Duc
2026-10-12 9:27 ` Oleksii Kurochko
2026-10-15 3:22 ` Zhang Zheng
2026-10-12 9:20 ` Oleksii Kurochko
2026-10-12 12:50 ` Jan Beulich [this message]
2026-10-12 13:24 ` Oleksii Kurochko
2026-10-15 4:50 ` Zhang Zheng
2026-10-15 3:44 ` Zhang Zheng
2026-10-12 12:52 ` Jan Beulich
2026-10-15 4:40 ` Zhang Zheng
2026-10-15 7:16 ` Jan Beulich
[not found] ` <20261010031406.2057735-3-zhangzheng@iscas.ac.cn>
2026-10-10 22:13 ` [PATCH v2 2/2] xen/ns16550: drain TX before reinitializing Baptiste Le Duc
2026-10-12 10:20 ` Oleksii Kurochko
2026-10-12 12:56 ` Jan Beulich
2026-10-12 13:25 ` Oleksii Kurochko
2026-10-15 4:52 ` Zhang Zheng
2026-10-12 13:00 ` Jan Beulich
2026-10-15 4:46 ` Zhang Zheng
2026-10-15 6:48 ` Zhang Zheng
[not found] ` <atB2HqxU_D481PBk@iscas-ws>
2026-10-15 7:54 ` Oleksii Kurochko
2026-10-15 8:49 ` Zhang Zheng
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=f5d4bb6c-69cd-45cc-badc-797ef9fbc96f@suse.com \
--to=jbeulich@suse.com \
--cc=alistair.francis@wdc.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=baptiste.le-duc@vates.tech \
--cc=connojdavis@gmail.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=oleksii.kurochko@gmail.com \
--cc=roger@xenproject.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=zhangzheng@iscas.ac.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.