From: Ahmad Fatoum <a.fatoum@barebox.org>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@barebox.org>
Subject: [PATCH 2/3] ARM: stm32mp: lxa: change stdout-path baud rate from 9600 to 115200
Date: Thu, 11 Jun 2026 23:14:21 +0200 [thread overview]
Message-ID: <20260611211425.4090757-2-a.fatoum@barebox.org> (raw)
In-Reply-To: <20260611211425.4090757-1-a.fatoum@barebox.org>
The LXA boards are the only upstream STM32 boards that set
stdout-path = &uart* instead of explicitly specifying a baud rate.
This would mean the default of 9600 is used, but it goes unnoticed when
booting normally as barebox fixes up a console= line that includes a
baud rate.
When EFI booting GRUB however, GRUB will not pass along the console=
line and thus the board ends up with a 9600 baud Linux console,
confusing users.
A fix for this has been submitted upstream[1]. Until then, have the fix
in barebox as barebox will pass along its device tree when booting via
EFI.
[1]: https://lore.kernel.org/all/20260611-lxa-stdout-path-baudrate-v1-0-59b60a5069ff@pengutronix.de/
Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
---
arch/arm/dts/stm32mp153c-lxa-fairytux2.dtsi | 2 ++
arch/arm/dts/stm32mp157c-lxa-mc1.dts | 2 ++
arch/arm/dts/stm32mp15xc-lxa-tac.dtsi | 2 ++
3 files changed, 6 insertions(+)
diff --git a/arch/arm/dts/stm32mp153c-lxa-fairytux2.dtsi b/arch/arm/dts/stm32mp153c-lxa-fairytux2.dtsi
index 701981358c68..d373ce04cf83 100644
--- a/arch/arm/dts/stm32mp153c-lxa-fairytux2.dtsi
+++ b/arch/arm/dts/stm32mp153c-lxa-fairytux2.dtsi
@@ -10,6 +10,8 @@ / {
barebox,deep-probe;
chosen {
+ stdout-path = "serial0:115200n8";
+
environment {
compatible = "barebox,environment";
device-path = &sdmmc2, "partname:barebox-environment";
diff --git a/arch/arm/dts/stm32mp157c-lxa-mc1.dts b/arch/arm/dts/stm32mp157c-lxa-mc1.dts
index 392194c20bd6..cfccb5207f43 100644
--- a/arch/arm/dts/stm32mp157c-lxa-mc1.dts
+++ b/arch/arm/dts/stm32mp157c-lxa-mc1.dts
@@ -14,6 +14,8 @@ aliases {
};
chosen {
+ stdout-path = "serial0:115200n8";
+
environment-sd {
compatible = "barebox,environment";
device-path = &sdmmc1, "partname:barebox-environment";
diff --git a/arch/arm/dts/stm32mp15xc-lxa-tac.dtsi b/arch/arm/dts/stm32mp15xc-lxa-tac.dtsi
index 6bd119a799e0..8c605fef2cbc 100644
--- a/arch/arm/dts/stm32mp15xc-lxa-tac.dtsi
+++ b/arch/arm/dts/stm32mp15xc-lxa-tac.dtsi
@@ -9,6 +9,8 @@ / {
barebox,deep-probe;
chosen {
+ stdout-path = "serial0:115200n8";
+
environment {
compatible = "barebox,environment";
device-path = &environment_emmc;
--
2.47.3
next prev parent reply other threads:[~2026-06-11 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 21:14 [PATCH 1/3] efi: loader: fix format string for ARM32 Ahmad Fatoum
2026-06-11 21:14 ` Ahmad Fatoum [this message]
2026-06-15 8:16 ` (subset) [PATCH 2/3] ARM: stm32mp: lxa: change stdout-path baud rate from 9600 to 115200 Sascha Hauer
2026-06-11 21:14 ` [PATCH 3/3] ARM: stm32mp: enable useful options for the LXA Fairy Tux2 Ahmad Fatoum
2026-06-11 21:21 ` [PATCH] fixup! " Ahmad Fatoum
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=20260611211425.4090757-2-a.fatoum@barebox.org \
--to=a.fatoum@barebox.org \
--cc=barebox@lists.infradead.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