From: "Ondřej Jirman" <megi@xff.cz>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: "Martijn Braam" <martijn@brixit.nl>,
"Heiko Stübner" <heiko@sntech.de>,
linux-kernel@vger.kernel.org,
"Peter Robinson" <pbrobinson@gmail.com>,
"Caleb Connolly" <kc@postmarketos.org>,
"Jarrah Gosbell" <kernel@undef.tools>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Tom Fitzhenry" <tom@tom-fitzhenry.me.uk>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: rockchip: Change serial baud rate for Pinephone Pro to 1.5 MB
Date: Tue, 4 Apr 2023 14:02:31 +0200 [thread overview]
Message-ID: <20230404120231.2enpesad2lhde6sb@core> (raw)
In-Reply-To: <87ttxvdgb7.fsf@minerva.mail-host-address-is-not-set>
Hello,
On Tue, Apr 04, 2023 at 01:42:36PM +0200, Javier Martinez Canillas wrote:
> Martijn Braam <martijn@brixit.nl> writes:
>
> > On 4/4/23 09:51, Heiko Stübner wrote:
> >> Hi,
> >>
> >> Am Montag, 3. April 2023, 19:59:37 CEST schrieb Javier Martinez Canillas:
> >>> This baud rate is set for the device by mainline u-boot and is also what
> >>> is set in the Pinebook Pro Device Tree, which is a device similar to the
> >>> PinePhone Pro but with a different form factor.
> >>>
> >>> Otherwise, the baud rate of the firmware and Linux don't match by default
> >>> and a 'console=ttyS2,1500000n8' kernel command line parameter is required
> >>> to have proper output for both.
> >> The interesting question is always if this will break someone else's setup.
> >> I've never really understood the strange setting of 1.5MBps, but on the
> >> other hand it _is_ a reality on most boards.
> >
> > It breaks my device test setup at least. The extra speed isn't worth the
> > hassle
>
> More than the extra speed is to have consistency accross all the rockchip
> devices in upstream and also sync with mainline u-boot.
>
> > of having a few devices at weird baudrates and the bootloader already
> > starts outputting debug logs at 115200 baud.
> >
>
> And mine starts outputting at 1.5MBps :) I guess that there isn't a one
> size fits all, so the question is whether the bikeshed color is what was
> painted in all other rockchip boards or the one that Tow-Boot has chosen.
For what it's worth, levinboot also defaults to 1.5 Mbaud.
https://gitlab.com/DeltaGem/levinboot/-/blob/release/rk3399/entry.S#L65
https://gitlab.com/DeltaGem/levinboot/-/blob/release/configure.py#L67
And it's very nice anything above >115200 is not broken by bad HW design,
like on original Pinephone, so this higher speed actually works. ;)
kind regards,
o.
> --
> Best regards,
>
> Javier Martinez Canillas
> Core Platforms
> Red Hat
>
next prev parent reply other threads:[~2023-04-04 12:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 17:59 [PATCH] arm64: dts: rockchip: Change serial baud rate for Pinephone Pro to 1.5 MB Javier Martinez Canillas
2023-04-04 7:51 ` Heiko Stübner
2023-04-04 8:08 ` Javier Martinez Canillas
2023-04-04 8:13 ` Jarrah
2023-04-04 8:18 ` Peter Robinson
2023-04-04 8:25 ` Javier Martinez Canillas
2023-04-04 8:24 ` Javier Martinez Canillas
2023-04-04 8:38 ` Peter Robinson
2023-04-04 8:46 ` Javier Martinez Canillas
2023-04-04 11:31 ` Martijn Braam
2023-04-04 11:42 ` Javier Martinez Canillas
2023-04-04 12:02 ` Ondřej Jirman [this message]
2023-04-04 12:36 ` Ondřej Jirman
2023-04-04 14:04 ` Javier Martinez Canillas
2023-04-04 15:40 ` Ondřej Jirman
2023-04-04 12:52 ` Peter Geis
2023-04-04 16:55 ` Heiko Stübner
2023-04-18 12:11 ` Javier Martinez Canillas
2023-04-18 14:26 ` Heiko Stübner
2023-07-21 23:06 ` Javier Martinez Canillas
2023-07-28 18:59 ` Heiko Stuebner
2023-07-28 19:55 ` Maya Matuszczyk
2023-07-28 23:05 ` Javier Martinez Canillas
2023-07-28 20:10 ` Ondřej Jirman
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=20230404120231.2enpesad2lhde6sb@core \
--to=megi@xff.cz \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=javierm@redhat.com \
--cc=kc@postmarketos.org \
--cc=kernel@undef.tools \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=martijn@brixit.nl \
--cc=pbrobinson@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tom@tom-fitzhenry.me.uk \
/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).