From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
Cc: Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-snps-arc@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] console: don't select first registered console if stdout-path used
Date: Sat, 26 Aug 2017 02:44:48 +0900 [thread overview]
Message-ID: <20170825174448.GC5535@tigerII.localdomain> (raw)
In-Reply-To: <20170825131451.15944-1-Eugeniy.Paltsev@synopsys.com>
On (08/25/17 16:14), Eugeniy Paltsev wrote:
> In the current implementation we take the first console that
> registers if we didn't select one.
>
> But if we specify console via "stdout-path" property in device tree
> we don't want first console that registers here to be selected.
> Otherwise we may choose wrong console - for example if some console
> is registered earlier than console is pointed in "stdout-path"
> property because console pointed in "stdout-path" property can be add as
> preferred quite late - when it's driver is probed.
>
> Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
hm... this is not the first time we see DT and stdout-path.
and so far it was pretty painful :) e.g. commits c6c7d83b9c9e, 05fd007e4629.
-ss
> ---
> kernel/printk/printk.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index 512f7c2..23262c1 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -26,6 +26,7 @@
> #include <linux/nmi.h>
> #include <linux/module.h>
> #include <linux/moduleparam.h>
> +#include <linux/of.h>
> #include <linux/delay.h>
> #include <linux/smp.h>
> #include <linux/security.h>
> @@ -2431,6 +2432,16 @@ void register_console(struct console *newcon)
> if (!has_preferred || bcon || !console_drivers)
> has_preferred = preferred_console >= 0;
>
> +
> + /*
> + * If we specify console via "stdout-path" property in device tree
> + * we don't want first console that registers here to be selected.
> + */
> +#ifdef CONFIG_OF
> + if (of_stdout)
> + has_preferred = true;
> +#endif
> +
> /*
> * See if we want to use this console driver. If we
> * didn't select a console we take the first one
> --
> 2.9.3
>
next prev parent reply other threads:[~2017-08-25 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 13:14 Eugeniy Paltsev
2017-08-25 13:20 ` Steven Rostedt
2017-08-25 17:44 ` Sergey Senozhatsky [this message]
2017-08-28 12:41 ` Eugeniy Paltsev
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=20170825174448.GC5535@tigerII.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.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
Powered by JetHome