mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Ogness <john.ogness@linutronix.de>
To: Chris Down <chris@chrisdown.name>, Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Marcos Paulo de Souza <mpdesouza@suse.com>,
	Naveen Kumar Chaudhary <naveen.osdev@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 09/16] printk: Allow to override options via the command line
Date: Fri, 30 Oct 2026 18:10:47 +0106	[thread overview]
Message-ID: <871p97i0gg.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <auLyEcr_gqE3CBBi@chrisdown.name>

On 2026-10-29, Chris Down <chris@chrisdown.name> wrote:
>>Consoles can be preferred either via the console= command line parameter
>>or by some platform specific code, e.g. SPCR, device tree.
>
> On v4 I recall you said you would probably do the change in a separate series. 
> I think that is still the better plan: the rest of the series is a clean-up and 
> it would be nice to keep it that way.
>
>>-	 * Historically, the preferred options are stored only by the first
>>-	 * caller who prefers the particular console.
>>+	 * Allow to override options via the command line but always
>>+	 * prefer the Braille variant.
>> 	 */
>>-	if (is_new_entry) {
>>+	if (is_new_entry || brl_options ||
>>+	    (user_specified && !is_braille_console_preferred(pc))) {
>
> This also clears options when the later console= has none, which v4 did not do. 
> That breaks at least the MIPS boards that pass the firmware baud rate from 
> setup_arch():
>
>     arch/mips/sgi-ip22/ip22-setup.c: add_preferred_console("ttyS", n, dbaud)
>     arch/mips/sgi-ip32/ip32-setup.c: add_preferred_console("ttyS", n, dbaud)
>     arch/mips/sni/setup.c:           add_preferred_console("ttyS"/"ttySC", port, baud)
>
> With "console=ttyS0" and no options, the drivers there (ip22zilog, 8250, 
> sccnxp) fall back to 9600, and anyone with the firmware set to another rate is 
> gonna have a bad time.
>
> It also makes a bare "console=uart" after an SPCR "uart" entry oops because 
> univ8250_console_match() hands the now-NULL options to uart_parse_earlycon().
>
> (A bare console=uart on its own already oopses in the base, so that part is an 
> older 8250 problem, but this patch adds a fun new way to get there.)
>
> If you want to keep it here, could it at least only override when the command 
> line actually provides options?

Agreed. It should be (user_specified && options && ...)

A console specified with no options should not be interpretted as "clear
options" but rather "not overriding options, just specifying that it is
preferred".

John

  reply	other threads:[~2026-10-30 17:04 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 12:05 [PATCH v5 00/16] printk: Clean up preferred console handling Petr Mladek
2026-09-29 12:05 ` [PATCH v5 01/16] printk: Rename struct console_cmdline to preferred_console Petr Mladek
2026-10-29  7:03   ` Chris Down
2026-09-29 12:05 ` [PATCH v5 02/16] printk: Rename preferred_console to preferred_dev_console Petr Mladek
2026-09-29 12:05 ` [PATCH v5 03/16] printk: Cleanup _braille_(un)register_console() wrappers Petr Mladek
2026-09-29 12:05 ` [PATCH v5 04/16] printk: Separate code for adding/updating preferred console metadata Petr Mladek
2026-10-27 12:05   ` John Ogness
2026-10-29  7:05   ` Chris Down
2026-09-29 12:05 ` [PATCH v5 05/16] printk: Prefer the console either via name or devname exclusively Petr Mladek
2026-10-27 12:14   ` John Ogness
2026-10-29  7:06   ` Chris Down
2026-09-29 12:05 ` [PATCH v5 06/16] printk: Check that index is not defined when a console is preferred via devname Petr Mladek
2026-10-27 18:08   ` John Ogness
2026-10-29  7:07   ` Chris Down
2026-09-29 12:05 ` [PATCH v5 07/16] printk: Ensure consistent name and devname when updating preferred console Petr Mladek
2026-10-29  7:09   ` Chris Down
2026-09-29 12:05 ` [PATCH v5 08/16] printk: Do not quietly ignore adding entry for a preferred console when there is no space Petr Mladek
2026-10-29  7:10   ` Chris Down
2026-10-29 16:23   ` John Ogness
2026-09-29 12:05 ` [PATCH v5 09/16] printk: Allow to override options via the command line Petr Mladek
2026-10-29  7:13   ` Chris Down
2026-10-30 17:04     ` John Ogness [this message]
2026-09-29 12:05 ` [PATCH v5 10/16] printk: Allow to debug misuse of add_or_update_preferred_console() Petr Mladek
2026-10-29  7:13   ` Chris Down
2026-09-29 12:05 ` [PATCH v5 11/16] console/braille: Lock console->setup() call during the registration Petr Mladek
2026-10-29  7:15   ` Chris Down
2026-09-29 12:05 ` [PATCH v5 12/16] printk: Separate code for enabling console Petr Mladek
2026-10-29  7:15   ` Chris Down
2026-09-29 12:05 ` [PATCH v5 13/16] printk: Try to register each console as Braille first Petr Mladek
2026-10-29  7:17   ` Chris Down
2026-09-29 12:05 ` [PATCH v5 14/16] printk: Do not set Braille console as preferred_console Petr Mladek
2026-10-29  7:19   ` Chris Down
2026-09-29 12:05 ` [PATCH v5 15/16] printk: Modify try_enable_default_console() to return error/success Petr Mladek
2026-10-29  7:20   ` Chris Down
2026-09-29 12:05 ` [PATCH v5 16/16] printk: Try enable preferred consoles only when there are any Petr Mladek
2026-10-29  7:20   ` Chris Down

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=871p97i0gg.fsf@jogness.linutronix.de \
    --to=john.ogness@linutronix.de \
    --cc=chris@chrisdown.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpdesouza@suse.com \
    --cc=naveen.osdev@gmail.com \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.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®