From: Arnd Bergmann <arnd@arndb.de>
To: Chunyan Zhang <zhang.lyra@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
DTML <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chunyan Zhang <chunyan.zhang@unisoc.com>,
SoC Team <soc@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Baolin Wang <baolin.wang7@gmail.com>,
Orson Zhai <orsonzhai@gmail.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RESEND PATCH] arm64: dts: specify console via command line
Date: Wed, 11 Mar 2020 15:31:24 +0100 [thread overview]
Message-ID: <CAK8P3a12iN4HzN3HsRSBJPLpwJzdVwhrK7Mje0V6eW3Lvd77iw@mail.gmail.com> (raw)
In-Reply-To: <20200311112120.30890-1-zhang.lyra@gmail.com>
On Wed, Mar 11, 2020 at 12:21 PM Chunyan Zhang <zhang.lyra@gmail.com> wrote:
>
> diff --git a/arch/arm64/boot/dts/sprd/sp9863a-1h10.dts b/arch/arm64/boot/dts/sprd/sp9863a-1h10.dts
> index 2047f7a74265..510f65f4d8b8 100644
> --- a/arch/arm64/boot/dts/sprd/sp9863a-1h10.dts
> +++ b/arch/arm64/boot/dts/sprd/sp9863a-1h10.dts
> @@ -28,7 +28,7 @@
>
> chosen {
> stdout-path = "serial1:115200n8";
> - bootargs = "earlycon";
> + bootargs = "earlycon console=ttyS1";
> };
> };
Hi Chunyan,
I would expect that you need to either specify the stdout-path, or the console=
kernel parameter, but not both.
If earlycon was used, shouldn't the driver know which port is the console?
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-11 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 11:21 [RESEND PATCH] arm64: dts: specify console via command line Chunyan Zhang
2020-03-11 14:31 ` Arnd Bergmann [this message]
2020-03-12 7:34 ` Chunyan Zhang
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=CAK8P3a12iN4HzN3HsRSBJPLpwJzdVwhrK7Mje0V6eW3Lvd77iw@mail.gmail.com \
--to=arnd@arndb.de \
--cc=baolin.wang7@gmail.com \
--cc=chunyan.zhang@unisoc.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=orsonzhai@gmail.com \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=zhang.lyra@gmail.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).