Devicetree
 help / color / mirror / Atom feed
From: David Laight <david.laight.linux@gmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "Alexandre Torgue" <alexandre.torgue@foss.st.com>,
	"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Leonard Göhrs" <l.goehrs@pengutronix.de>,
	"Marc Kleine-Budde" <mkl@pengutronix.de>,
	"Alexandre Torgue" <alexandre.torgue@st.com>,
	devicetree@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 0/3] ARM: dts: stm32: lxa: change stdout-path baud rate from 9600 to 115200
Date: Fri, 12 Jun 2026 07:53:42 +0100	[thread overview]
Message-ID: <20260612075342.6615d66c@pumpkin> (raw)
In-Reply-To: <b4fd25b6-52e3-4b5e-8440-69545bce43e8@pengutronix.de>

On Thu, 11 Jun 2026 22:33:18 +0200
Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:

> Hi David,
> 
> On 6/11/26 21:43, David Laight wrote:
> > On Thu, 11 Jun 2026 20:12:32 +0200
> > Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
> >   
> >> The LXA boards are the only 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.  
> > 
> > Is it possible to determine the current baud rate (by reading the hardware
> > register) and default to that value.
> > Then if grub has initialised the uart the kernel will use the same
> > baud rate.  
> 
> I think so, yes. In addition to the register divider configuration, one
> would need the input clock rate as well, but that's not a problem.
> 
> Do you know if any drivers already do this?

I've seen it done somewhere, certainly x86, but possibly NetBSD.
That would have been preserving the baud rate set by the bios.
You don't want the baud rate changing half way through the boot sequence.

	David

> 
> Nevertheless, I would like the LXA device trees changed, even if only
> to align them with all other existing STM32 device trees.
> 
> Cheers,
> Ahmad
> 
> 
> > 
> > 	David
> >   
> >>
> >> This series fixes this. As the device trees were added at different
> >> times, they are fixed each in a separate commit with its own Fixes: tag.
> >>
> >> ---
> >> Ahmad Fatoum (3):
> >>       ARM: dts: stm32: lxa-mc1: change stdout-path baud rate from 9600 to 115200
> >>       ARM: dts: stm32: lxa-tac: change stdout-path baud rate from 9600 to 115200
> >>       ARM: dts: stm32: fairytux2: change stdout-path baud rate from 9600 to 115200
> >>
> >>  arch/arm/boot/dts/st/stm32mp153c-lxa-fairytux2.dtsi | 2 +-
> >>  arch/arm/boot/dts/st/stm32mp157c-lxa-mc1.dts        | 2 +-
> >>  arch/arm/boot/dts/st/stm32mp15xc-lxa-tac.dtsi       | 2 +-
> >>  3 files changed, 3 insertions(+), 3 deletions(-)
> >> ---
> >> base-commit: 4549871118cf616eecdd2d939f78e3b9e1dddc48
> >> change-id: 20260611-lxa-stdout-path-baudrate-7cf454cdae07
> >>
> >> Best regards,
> >> --  
> >> Ahmad Fatoum <a.fatoum@pengutronix.de>
> >>
> >>  
> > 
> >   
> 
> 


      reply	other threads:[~2026-06-12  6:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11 18:12 [PATCH 0/3] ARM: dts: stm32: lxa: change stdout-path baud rate from 9600 to 115200 Ahmad Fatoum
2026-06-11 18:12 ` [PATCH 1/3] ARM: dts: stm32: lxa-mc1: " Ahmad Fatoum
2026-06-11 18:12 ` [PATCH 2/3] ARM: dts: stm32: lxa-tac: " Ahmad Fatoum
2026-06-11 18:12 ` [PATCH 3/3] ARM: dts: stm32: fairytux2: " Ahmad Fatoum
2026-06-11 19:43 ` [PATCH 0/3] ARM: dts: stm32: lxa: " David Laight
2026-06-11 20:33   ` Ahmad Fatoum
2026-06-12  6:53     ` David Laight [this message]

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=20260612075342.6615d66c@pumpkin \
    --to=david.laight.linux@gmail.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=alexandre.torgue@foss.st.com \
    --cc=alexandre.torgue@st.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=l.goehrs@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=mkl@pengutronix.de \
    --cc=robh@kernel.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