From: Chris Down <chris@chrisdown.name>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Petr Mladek <pmladek@suse.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kernel Team <kernel-team@fb.com>
Subject: Re: [RFC PATCH] printk: console: Allow each console to have its own loglevel
Date: Thu, 19 May 2022 15:37:10 +0100 [thread overview]
Message-ID: <YoZWFi0AtmA9fvv/@chrisdown.name> (raw)
In-Reply-To: <CAMuHMdU2tUU6FAM-nK9oxd0GwcO3WwvZp9Um4=w5By+N0P0kXA@mail.gmail.com>
Hey Geert,
Geert Uytterhoeven writes:
>All of the above options are appropriate for "classic" systems,
>where the console device is selected using the "console=" option.
>
>On systems using Device tree, the serial console device is selected
>using the "chosen/stout-path" property in DT, and the graphical
>console is usually auto-detected and auto-enabled through DRM.
>Do you envision a way to specify a specific console loglevel on the
>kernel command line on such systems?
Interesting question! I hadn't really thought about device tree. I actually
have very little understanding of how it works to be honest :-)
I'm happy to add loglevel support to device tree, I assume I'd add another
property under the chosen node, like chosen/stdout-loglevel.
I have some questions, though:
1. It looks like DT is standardised. Do I need to get standards approval first?
2. Is there documentation on how to reliably test DT changes?
Thanks!
Chris
next prev parent reply other threads:[~2022-05-19 14:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 14:24 [RFC PATCH] printk: console: Allow each console to have its own loglevel Chris Down
2022-05-18 14:32 ` Chris Down
2022-05-18 15:34 ` Greg Kroah-Hartman
2022-05-18 19:46 ` Chris Down
2022-05-18 19:54 ` Greg Kroah-Hartman
2022-05-18 20:27 ` Chris Down
2022-05-19 7:04 ` Greg Kroah-Hartman
2022-05-19 14:12 ` Chris Down
2022-05-19 14:35 ` Greg Kroah-Hartman
2022-05-19 15:08 ` Chris Down
2022-05-19 15:24 ` Greg Kroah-Hartman
2022-05-19 15:25 ` Greg Kroah-Hartman
2022-05-19 15:55 ` Chris Down
2022-05-19 17:45 ` Greg Kroah-Hartman
2022-05-19 17:55 ` Chris Down
2022-05-24 9:19 ` Petr Mladek
2022-05-30 10:48 ` [OFFLIST] " Chris Down
2022-05-30 10:49 ` Chris Down
2022-05-19 7:26 ` Geert Uytterhoeven
2022-05-19 14:37 ` Chris Down [this message]
2022-05-19 17:48 ` Geert Uytterhoeven
2022-05-19 18:05 ` Chris Down
2022-05-19 13:59 ` [printk] 6f922c8d53: BUG:kernel_NULL_pointer_dereference,address kernel test robot
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=YoZWFi0AtmA9fvv/@chrisdown.name \
--to=chris@chrisdown.name \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.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).