From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Vicente Bergas <vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] arm64: dts: rockchip: sapphire: add chosen node
Date: Tue, 30 Oct 2018 15:09:17 +0100 [thread overview]
Message-ID: <5408972.CYYHPefPr5@phil> (raw)
In-Reply-To: <20181026133655.1605-1-vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi Vicente,
Am Freitag, 26. Oktober 2018, 15:36:55 CET schrieb Vicente Bergas:
> In order to use earlycon, the stdout-path property needs to be set in
> the chosen node.
>
> ---
>
> Also, this works around this kexec bug:
> http://lists.infradead.org/pipermail/kexec/2018-October/021746.html
>
> Signed-off-by: Vicente Bergas <vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> arch/arm64/boot/dts/rockchip/rk3399-sapphire.dts | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-sapphire.dts b/arch/arm64/boot/dts/rockchip/rk3399-sapphire.dts
> index 5a5806044..326615018 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399-sapphire.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3399-sapphire.dts
> @@ -9,4 +9,8 @@
> / {
> model = "Sapphire-RK3399 Board";
> compatible = "rockchip,rk3399-sapphire", "rockchip,rk3399";
> +
> + chosen {
> + stdout-path = "serial2:1500000n8";
> + };
shouldn't that maybe live in the shared .dtsi instead?
I do guess the excavator will have the same default serial?
Heiko
next prev parent reply other threads:[~2018-10-30 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 13:36 [PATCH] arm64: dts: rockchip: sapphire: add chosen node Vicente Bergas
[not found] ` <20181026133655.1605-1-vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-10-30 14:09 ` Heiko Stuebner [this message]
2018-10-30 14:59 ` [PATCH v2] " Vicente Bergas
[not found] ` <20181030145941.15975-1-vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-10-30 20:34 ` Heiko Stuebner
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=5408972.CYYHPefPr5@phil \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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