From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH 1/2] serial: qcom-geni: Convert console to nbcon
Date: Thu, 30 Jul 2026 18:19:12 +0200 [thread overview]
Message-ID: <ef2a2f3a-1051-4527-8e13-0af263a443ba@oss.qualcomm.com> (raw)
In-Reply-To: <20260729-qcom-geni-nbcon-v1-1-3053b96465ed@oss.qualcomm.com>
On 7/29/26 11:44 PM, Bjorn Andersson wrote:
> The legacy GENI console writer serializes every message around a
> synchronous polled M-side transfer. It blocks printk callers for UART
> wire time and cannot provide atomic output while normal console output is
> active.
>
> Convert the console to nbcon threaded and atomic writers. Use the UART
> port lock as the device lock and bound threaded M-side commands so
> urgent diagnostics can take over atomic output. The threaded writer is
> batching the output in 32-source-byte commands, a value chosen to
> balance the command setup overhead with atomic-handoff latency.
>
> Atomic output can cancel an active normal TX command. Use irq_work to
> resume queued TTY output afterward, honor flow control, and prevent the
> deferred restart from accessing the port during shutdown or removal.
>
> Assisted-by: OpenCode:GPT-5.5
> Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
> ---
[...]
> + while (offset < wctxt->len) {
Other nbcon drivers access wctxt->len in write_thread with READ_ONCE,
I believe we need to do the same
[...]
> +static void qcom_geni_serial_console_write_atomic(struct console *co,
> + struct nbcon_write_context *wctxt)
> +{
> struct qcom_geni_serial_port *port;
> + struct uart_port *uport;
> u32 m_irq_en, s_irq_en;
> - bool locked = true;
> - unsigned long flags;
> -
> - WARN_ON(co->index < 0 || co->index >= GENI_UART_CONS_PORTS);
Unrelated?
[...]
> +/* Caller holds the UART port lock. */
> +static void qcom_geni_serial_resume_tx(struct uart_port *uport)
> +{
> + if (!uart_tx_stopped(uport) &&
> + !kfifo_is_empty(&uport->state->port.xmit_fifo))
> + qcom_geni_serial_start_tx_fifo(uport);
> +}
This is a single-use oneliner, but perhaps having 3+2 conditions
is better than having 5 conditions to an if statement..
> +
> +static void qcom_geni_serial_restart_tx(struct irq_work *work)
> +{
> + struct qcom_geni_serial_port *port = container_of(work,
> + struct qcom_geni_serial_port, tx_kick);
> + struct uart_port *uport = &port->uport;
> +
> + if (!READ_ONCE(port->tx_kick_enabled) || !uport->state || uport->suspended)
> + return;
> +
> + uart_port_lock(uport);
> + if (READ_ONCE(port->tx_kick_enabled) && uport->state && !uport->suspended)
> + qcom_geni_serial_resume_tx(uport);
> + uart_port_unlock(uport);
> +}
> +
> static void qcom_geni_serial_stop_tx_fifo(struct uart_port *uport)
> {
> u32 irq_en;
> @@ -1182,6 +1284,11 @@ static int setup_fifos(struct qcom_geni_serial_port *port)
>
> static void qcom_geni_serial_shutdown(struct uart_port *uport)
> {
> + struct qcom_geni_serial_port *port = to_dev_port(uport);
> +
> + /* Atomic console output queues tx_kick without taking the port lock. */
non-atomic?
Konrad
next prev parent reply other threads:[~2026-07-30 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 21:44 [PATCH 0/2] serial: qcom-geni: Convert console to nbcon and handle RX overflow Bjorn Andersson
2026-07-29 21:44 ` [PATCH 1/2] serial: qcom-geni: Convert console to nbcon Bjorn Andersson
2026-07-30 16:19 ` Konrad Dybcio [this message]
2026-08-06 13:29 ` Aniket RANDIVE
2026-07-29 21:44 ` [PATCH 2/2] serial: qcom-geni: Keep FIFO RX active during console TX Bjorn Andersson
2026-07-30 16:34 ` Konrad Dybcio
2026-08-06 13:49 ` Aniket RANDIVE
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=ef2a2f3a-1051-4527-8e13-0af263a443ba@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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
all inboxes | Powered by JetHome®