From: John Ogness <john.ogness@linutronix.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Petr Mladek" <pmladek@suse.com>,
"Sergey Senozhatsky" <senozhatsky@chromium.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
"Tony Lindgren" <tony@atomide.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Serge Semin" <fancer.lancer@gmail.com>,
"Rengarajan S" <rengarajan.s@microchip.com>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH next v1 1/2] serial: 8250: Switch to nbcon console
Date: Thu, 05 Sep 2024 21:29:06 +0206 [thread overview]
Message-ID: <877cbp3nxh.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <Ztm85Y_mo5-OJveq@smile.fi.intel.com>
On 2024-09-05, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> On Thu, Sep 05, 2024 at 03:53:18PM +0206, John Ogness wrote:
>> Implement the necessary callbacks to switch the 8250 console driver
>> to perform as an nbcon console.
>>
>> Add implementations for the nbcon console callbacks (write_atomic,
>> write_thread, device_lock, device_unlock) and add CON_NBCON to the
>> initial flags.
>>
>> The legacy code is kept in order to easily switch back to legacy mode
>> by defining USE_SERIAL_8250_LEGACY_CONSOLE.
>
> ...
>
>> static struct console univ8250_console = {
>> .name = "ttyS",
>> +#ifdef USE_SERIAL_8250_LEGACY_CONSOLE
>
> Can it be done at run-time (theoretically or even practically)?
> (Note that we have already knob to disable / enable consoles.)
We don't want to maintain the legacy variant and really people should
not be using it either. NBCON is the way forward for all console
drivers.
I will just remove it for v2. If someone wants to use the old code, they
will need to revert the patch.
>> + if (nbcon_exit_unsafe(wctxt)) {
>> + int len = READ_ONCE(wctxt->len);
>
>> + int i;
>
> unsigned ?
ACK.
>> + /* Atomic console not supported for rs485 mode. */
>
> RS485
ACK.
> Feels like parts (1) and (2) duplicates existing pieces of code. May it be
> refactored to minimize the duplication?
When I remove the unused legacy code, the duplication
disappears. write_thread() and write_atomic() have very little in
common.
John Ogness
next prev parent reply other threads:[~2024-09-05 19:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 13:47 [PATCH tty-next v1 0/2] convert 8250 to nbcon John Ogness
2024-09-05 13:47 ` [PATCH next v1 1/2] serial: 8250: Switch to nbcon console John Ogness
2024-09-05 14:15 ` Andy Shevchenko
2024-09-05 19:23 ` John Ogness [this message]
2024-09-05 19:30 ` Andy Shevchenko
2024-09-06 10:10 ` Greg Kroah-Hartman
2024-09-06 12:37 ` Petr Mladek
2024-09-06 13:35 ` John Ogness
2024-09-06 16:38 ` John Ogness
2024-09-07 20:39 ` Thomas Gleixner
2024-09-09 9:53 ` Andy Shevchenko
2024-09-09 12:13 ` Thomas Gleixner
2024-09-09 9:50 ` Andy Shevchenko
2024-09-05 13:47 ` [PATCH next v1 2/2] serial: 8250: Revert "drop lockdep annotation from serial8250_clear_IER()" John Ogness
2024-09-05 13:53 ` [PATCH tty-next v1 0/2] convert 8250 to nbcon Andy Shevchenko
2024-09-05 14:05 ` John Ogness
2024-09-05 14:09 ` Greg Kroah-Hartman
2024-09-05 14:12 ` John Ogness
2024-09-05 14:17 ` Andy Shevchenko
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=877cbp3nxh.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fancer.lancer@gmail.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=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rengarajan.s@microchip.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).