summaryrefslogtreecommitdiff
path: root/scripts/objdiff
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2026-06-11 20:12:33 +0200
committerAlexandre Torgue <alexandre.torgue@foss.st.com>2026-08-10 10:38:17 +0200
commit40afa1b1a56c1e3d7713c0f1f37b95174dfa25c8 (patch)
treec0844005fe50c27fb4ad064990591454835cf929 /scripts/objdiff
parent3a886e93febd468e3c59487c3af91b8388ad71a3 (diff)
downloadlinux-next-40afa1b1a56c1e3d7713c0f1f37b95174dfa25c8.tar.gz
linux-next-40afa1b1a56c1e3d7713c0f1f37b95174dfa25c8.zip
ARM: dts: stm32: lxa-mc1: change stdout-path baud rate from 9600 to 115200
The default baud rate when none is specified is up to the DT consumer. In the case of the Linux STM32 serial driver, it defaults to 9600 baud, which differs from the 115200 baud that this board's barebox bootloader configured. This went unnoticed, because barebox automatically fixes up a console= command-line option that looks like this on the LXA boards: console=ttySTM0,115200n8 This had precedence over the 9600 fallback baud rate. But when EFI booting a kernel via GRUB, we run into this issue, because the barebox-provided command-line is disregarded by GRUB. Fix this by explicitly setting the baud rate to the correct 115200. Fixes: 666b5ca85cd3 ("ARM: dts: stm32: add STM32MP1-based Linux Automation MC-1 board") Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.kernel.org/r/20260611-lxa-stdout-path-baudrate-v1-1-59b60a5069ff@pengutronix.de Signed-off-by: Alexandre Torgue <alexandre.torgue@foss.st.com>
Diffstat (limited to 'scripts/objdiff')
0 files changed, 0 insertions, 0 deletions