From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Russell King <linux@armlinux.org.uk>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: [PATCH] ARM: early_printk: respect keep parameter
Date: Wed, 11 Jul 2018 20:32:39 +0200 [thread overview]
Message-ID: <20180711183239.21023-1-alexandre.belloni@bootlin.com> (raw)
Parse and use the keep parameter of earlyprintk to avoid having the kernel
output stop with:
Console: colour dummy device 80x30
console [tty0] enabled
bootconsole [earlycon0] disabled
This happens because once tty0, the virtual terminal console is registered,
it is selected as the default console, disregarding an existing stdout-path
DT property and the early console is shutdown before the console driver is
probed.
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
---
arch/arm/kernel/early_printk.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/kernel/early_printk.c b/arch/arm/kernel/early_printk.c
index 9257736ec9fa..bbb10150b11a 100644
--- a/arch/arm/kernel/early_printk.c
+++ b/arch/arm/kernel/early_printk.c
@@ -42,6 +42,9 @@ static struct console early_console_dev = {
static int __init setup_early_printk(char *buf)
{
+ if (buf && strstr(buf, "keep"))
+ early_console_dev.flags &= ~CON_BOOT;
+
early_console = &early_console_dev;
register_console(&early_console_dev);
return 0;
--
2.18.0
next reply other threads:[~2018-07-11 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 18:32 Alexandre Belloni [this message]
2018-07-17 20:16 ` [PATCH] ARM: early_printk: respect keep parameter Nicolas Pitre
2018-07-17 20:31 ` Alexandre Belloni
2018-07-17 20:48 ` Nicolas Pitre
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=20180711183239.21023-1-alexandre.belloni@bootlin.com \
--to=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nicolas.pitre@linaro.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;
as well as URLs for NNTP newsgroup(s).