From: Martijn Braam <martijn@brixit.nl>
To: "Heiko Stübner" <heiko@sntech.de>,
linux-kernel@vger.kernel.org,
"Javier Martinez Canillas" <javierm@redhat.com>
Cc: Peter Robinson <pbrobinson@gmail.com>,
Caleb Connolly <kc@postmarketos.org>,
Jarrah Gosbell <kernel@undef.tools>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Ondrej Jirman <megi@xff.cz>, 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 13:31:05 +0200 [thread overview]
Message-ID: <52d83a29-0f16-cd4c-9810-7c6bd497fe85@brixit.nl> (raw)
In-Reply-To: <3738011.44csPzL39Z@diego>
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
of having a few devices at weird baudrates and the bootloader already
starts outputting debug logs at 115200 baud.
>
> Personally I don't care that much either way, but would like a comment
> from the other people working on that device - if possible.
>
> I guess if we don't hear anything, I'll apply it nevertheless at some point
>
>
> Heiko
>
>
>> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
>> ---
>>
>> I tried to instead get rid of the baud rate altogether, as suggested by
>> Peter Robinson. AFAIU that should just pick whatever bad rate has been
>> using by the early console.
>>
>> But neither using 'stdout-path = "serial2" nor 'stdout-path = &uart2'
>> worked for me.
>>
>> In both cases I didn't have any output unless setting a baud rate using
>> the 'console='param.
>>
>> arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts b/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts
>> index a0795a2b1cb1..6bbe65bd5bd4 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts
>> +++ b/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts
>> @@ -26,7 +26,7 @@ aliases {
>> };
>>
>> chosen {
>> - stdout-path = "serial2:115200n8";
>> + stdout-path = "serial2:1500000n8";
>> };
>>
>> gpio-keys {
>>
>> base-commit: 3adf89324a2b2a9dbc2c12d8895021e7e34e3346
>>
>
>
>
next prev parent reply other threads:[~2023-04-04 11:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 17:59 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 [this message]
2023-04-04 11:42 ` Javier Martinez Canillas
2023-04-04 12:02 ` Ondřej Jirman
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=52d83a29-0f16-cd4c-9810-7c6bd497fe85@brixit.nl \
--to=martijn@brixit.nl \
--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=megi@xff.cz \
--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
all inboxes | Powered by JetHome®