From: Paul Walmsley <paul.walmsley@sifive.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Christoph Hellwig <hch@lst.de>, Andreas Schwab <schwab@suse.de>
Subject: [PATCH] Documentation: admin-guide: add earlycon documentation for RISC-V
Date: Wed, 9 Oct 2019 12:53:50 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1910091252160.11044@viisi.sifive.com> (raw)
Kernels booting on RISC-V can specify "earlycon" with no options on
the Linux command line, and the generic DT earlycon support will query
the "chosen/stdout-path" property (if present) to determine which
early console device to use. Document this appropriately in the
admin-guide.
Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Andreas Schwab <schwab@suse.de>
---
Documentation/admin-guide/kernel-parameters.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index c7ac2f3ac99f..011fee969ece 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -990,6 +990,10 @@
[X86] When used with no options the early console is
determined by the ACPI SPCR table.
+ [RISCV] When used with no options, the early
+ console is determined by the stdout-path
+ property in the device tree's chosen node.
+
cdns,<addr>[,options]
Start an early, polled-mode console on a Cadence
(xuartps) serial port at the specified address. Only
--
2.23.0
next reply other threads:[~2019-10-09 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 19:53 Paul Walmsley [this message]
2019-10-10 7:10 ` [PATCH] Documentation: admin-guide: add earlycon documentation for RISC-V Geert Uytterhoeven
2019-10-10 17:23 ` Jonathan Corbet
2019-11-08 6:10 ` Christoph Hellwig
2019-11-11 17:30 ` Paul Walmsley
2019-11-12 16:44 ` Jonathan Corbet
2019-10-17 16:10 ` Christoph Hellwig
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=alpine.DEB.2.21.9999.1910091252160.11044@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=corbet@lwn.net \
--cc=geert@linux-m68k.org \
--cc=hch@lst.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=schwab@suse.de \
/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).