From: Tom Hebb <tommyhebb@gmail.com>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
Cc: linux-kernel@vger.kernel.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"moderated list:ARM/Synaptics Berlin SoC support"
<linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: berlin: switch to earlycon
Date: Wed, 4 Jul 2018 17:14:24 -0400 [thread overview]
Message-ID: <03049848-f627-41aa-0808-152c4f959ed8@gmail.com> (raw)
In-Reply-To: <20180704171435.6b6113de@xhacker.debian>
Hi Jisheng,
On 07/04/2018 05:14 AM, Jisheng Zhang wrote:
> Hi Thomas,
>
> On Tue, 29 May 2018 11:41:42 -0400 Thomas Hebb wrote:
>
>> The Synopsys DesignWare 8250 UART in Berlin SoCs is now supported by
>> 8250_early, so we can use earlycon for early console output instead
>> of earlyprintk, which requires an SoC-specific kernel.
>
> IIRC, earlyprintk still works during the decompress progress while the
> earlycon doesn't.
Yes, I believe that's correct. My original rationale for this patch was
that earlycon is generally preferred over earlyprintk since it doesn't
require SoC-specific kernels, but now I'm not convinced that either of
the two parameters belongs in the dts file. As you point out,
earlyprintk can do things that earlycon cannot, and in the common case,
neither are needed.
Perhaps removing the bootargs property altogether is more correct. I'm
happy to send another patch to do that if you concur.
>>
>> Signed-off-by: Thomas Hebb <tommyhebb@gmail.com>
>> ---
>> arch/arm/boot/dts/berlin2-sony-nsz-gs7.dts | 2 +-
>> arch/arm/boot/dts/berlin2cd-google-chromecast.dts | 2 +-
>> arch/arm/boot/dts/berlin2q-marvell-dmp.dts | 2 +-
>> 3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/berlin2-sony-nsz-gs7.dts b/arch/arm/boot/dts/berlin2-sony-nsz-gs7.dts
>> index 1c475796d17f..f98798bb684f 100644
>> --- a/arch/arm/boot/dts/berlin2-sony-nsz-gs7.dts
>> +++ b/arch/arm/boot/dts/berlin2-sony-nsz-gs7.dts
>> @@ -45,7 +45,7 @@
>> compatible = "sony,nsz-gs7", "marvell,berlin2", "marvell,berlin";
>>
>> chosen {
>> - bootargs = "earlyprintk";
>> + bootargs = "earlycon";
>
> Is there something missing here? example, uart8250,mmio,<addr>?
No explicit MMIO info is needed for earlycon on DT systems where an
stdout-path property is present. I've tested the patch as-is and the
early output works fine.
>> stdout-path = "serial0:115200n8";
>> };
>>
>> diff --git a/arch/arm/boot/dts/berlin2cd-google-chromecast.dts b/arch/arm/boot/dts/berlin2cd-google-chromecast.dts
>> index ca24def0ce13..20f31cdeaf38 100644
>> --- a/arch/arm/boot/dts/berlin2cd-google-chromecast.dts
>> +++ b/arch/arm/boot/dts/berlin2cd-google-chromecast.dts
>> @@ -46,7 +46,7 @@
>> compatible = "google,chromecast", "marvell,berlin2cd", "marvell,berlin";
>>
>> chosen {
>> - bootargs = "earlyprintk";
>> + bootargs = "earlycon";
>> stdout-path = "serial0:115200n8";
>> };
>>
>> diff --git a/arch/arm/boot/dts/berlin2q-marvell-dmp.dts b/arch/arm/boot/dts/berlin2q-marvell-dmp.dts
>> index 57aa5f8a7c77..9834e84a0797 100644
>> --- a/arch/arm/boot/dts/berlin2q-marvell-dmp.dts
>> +++ b/arch/arm/boot/dts/berlin2q-marvell-dmp.dts
>> @@ -49,7 +49,7 @@
>> };
>>
>> chosen {
>> - bootargs = "earlyprintk";
>> + bootargs = "earlycon";
>> stdout-path = "serial0:115200n8";
>> };
>>
>
prev parent reply other threads:[~2018-07-04 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 15:41 [PATCH] ARM: dts: berlin: switch to earlycon Thomas Hebb
2018-07-04 9:14 ` Jisheng Zhang
2018-07-04 21:14 ` Tom Hebb [this message]
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=03049848-f627-41aa-0808-152c4f959ed8@gmail.com \
--to=tommyhebb@gmail.com \
--cc=Jisheng.Zhang@synaptics.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=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@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