From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: "Sergey Senozhatsky" <senozhatsky@chromium.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Marcos Paulo de Souza" <mpdesouza@suse.com>,
"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Hugo Villeneuve" <hvilleneuve@dimonoff.com>,
"Fushuai Wang" <wangfushuai@baidu.com>,
"Kees Cook" <kees@kernel.org>,
"Stepan Ionichev" <sozdayvek@gmail.com>,
linux-serial@vger.kernel.org,
"Manuel Lauss" <manuel.lauss@gmail.com>,
linux-kernel@vger.kernel.org, "Petr Mladek" <pmladek@suse.com>
Subject: [PATCH 0/2] braille: nbcon: Allow using a serial driver converted to nbcon API as a Braille console
Date: Tue, 22 Sep 2026 09:25:56 +0200 [thread overview]
Message-ID: <20260922072558.98854-1-pmladek@suse.com> (raw)
Hi,
I have been working on v5 [1] of the patchset cleaning console registration
code and I found that the system did not boot when I selected a Braille
on the command line, for example:
console=brl,ttyS0,115200 console=tty0
Bisection went down to the commit d3539347022a ("serial: 8250: Switch to
nbcon console, take 2"). I found that the Braille console driver called
braille_co->write() internally where braille_co pointed to the uart
8250 driver.
I added the support for the nbcon console API similar way as we did
for kdb [2].
Note 1: I believe that we have a bug in the kdb patch because we call
con->write() atomic callback after entering the unsafe mode.
But we should do so in the default "safe" mode.
Note 2: I am not completely sure about the locking. It might be better
to use NBCON_PRIO_PANIC in panic().
Also I thought about using con->write_thread(). But I think
that we have to use the atomic variant because the Braille
console can be called from printk() via the VT code, aka
graphical console.
Note 3: I do not have any device to read the Braille output so I am not
sure if the output is correct. I just checked the output on
the serial console and it is a bit suspicious. It looks like
it prints every message N-times when N is the length of the string.
And it adds one character in each iteration, for example:
<paste>
E>[ E>[ E>[ O *>[ OK A>[ OK A>[ OK A>[ OK ] <>[ OK ] <>[ OK ] R N>[ OK ] Re
>[ OK ] Rea J>[ OK ] Reac >[ OK ] Reach A>[ OK ] Reache D>[ OK ] Reached @>[ OK ] Reached @>[ OK ] Reached t
</paste>
But I think that this is not caused by the NBCON console API.
[1] https://lore.kernel.org/all/20260604101459.393162-1-pmladek@suse.com/
[2] https://lore.kernel.org/all/20251016-nbcon-kgdboc-v6-0-866aac60a80e@suse.com/
Petr Mladek (2):
printk: nbcon: Introduce Braille helpers
braille: nbcon: Use nbcon atomic console callbacks
.../accessibility/braille/braille_console.c | 38 +++++++++++-
drivers/tty/serial/8250/8250_port.c | 5 +-
include/linux/console.h | 8 +++
kernel/printk/nbcon.c | 59 +++++++++++++++++++
4 files changed, 107 insertions(+), 3 deletions(-)
--
2.55.0
next reply other threads:[~2026-09-22 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 7:25 Petr Mladek [this message]
2026-09-22 7:25 ` [PATCH 1/2] printk: nbcon: Introduce Braille helpers Petr Mladek
2026-09-22 7:25 ` [PATCH 2/2] braille: nbcon: Use nbcon atomic console callbacks Petr Mladek
[not found] ` <20260922073728.2ADCD1F000FF@smtp.kernel.org>
2026-09-23 14:39 ` Petr Mladek
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=20260922072558.98854-1-pmladek@suse.com \
--to=pmladek@suse.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=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=manuel.lauss@gmail.com \
--cc=mpdesouza@suse.com \
--cc=rostedt@goodmis.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=senozhatsky@chromium.org \
--cc=sozdayvek@gmail.com \
--cc=wangfushuai@baidu.com \
/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®