From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Tony Lindgren <tony@atomide.com>,
Bruno Thomsen <bruno.thomsen@gmail.com>,
Judith Mendez <jm@ti.com>, Kevin Hilman <khilman@baylibre.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: am33xx: Add missing serial console speed
Date: Thu, 2 Oct 2025 15:32:53 +0300 [thread overview]
Message-ID: <609ec2e6-c877-4fc5-95b7-935ae2549b3a@gmail.com> (raw)
In-Reply-To: <63cef5c3643d359e8ec13366ca79377f12dd73b1.1759398641.git.geert+renesas@glider.be>
On 02/10/2025 12:53, Geert Uytterhoeven wrote:
> Without a serial console speed specified in chosen/stdout-path in the
> DTB, the serial console uses the default speed of the serial driver,
> unless explicitly overridden in a legacy console= kernel command-line
> parameter.
>
> After dropping "ti,omap3-uart" from the list of compatible values in DT,
> AM33xx serial ports can no longer be used with the legacy OMAP serial
> driver, but only with the OMAP-flavored 8250 serial driver (which is
> mutually-exclusive with the former). However, replacing
> CONFIG_SERIAL_OMAP=y by CONFIG_SERIAL_8250_OMAP=y (with/without enabling
> CONFIG_SERIAL_8250_OMAP_TTYO_FIXUP) may not be sufficient to restore
> serial console functionality: the legacy OMAP serial driver defaults to
> 115200 bps, while the 8250 serial driver defaults to 9600 bps, causing
> no visible output on the serial console when no appropriate console=
> kernel command-line parameter is specified.
>
> Fix this for all AM33xx boards by adding ":115200n8" to
> chosen/stdout-path. This requires replacing the "&uartN" reference by
> the corresponding "serialN" DT alias.
>
> Fixes: ca8be8fc2c306efb ("ARM: dts: am33xx-l4: fix UART compatible")
> Fixes: 077e1cde78c3f904 ("ARM: omap2plus_defconfig: Enable 8250_OMAP")
> Closes: https://lore.kernel.org/CAMuHMdUb7Jb2=GqK3=Rn+Gv5G9KogcQieqDvjDCkJA4zyX4VcA@mail.gmail.com
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Matti Vaittinen <mazziesaccount@gmail.com>
Tested-by: Matti Vaittinen <mazziesaccount@gmail.com>
(Tested booting on Beaglebone black with a config and kernel command
line which were NOT affected by the issue. Well, prints do still get
through the UART to my minicom, so things seem to work for me after this
change as well :) )
The change does also look Ok to me.
Yours,
-- Matti
next prev parent reply other threads:[~2025-10-02 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 9:53 [PATCH] ARM: dts: am33xx: Add missing serial console speed Geert Uytterhoeven
2025-10-02 12:32 ` Matti Vaittinen [this message]
2025-10-02 19:19 ` Bruno Thomsen
2025-11-04 23:06 ` Kevin Hilman
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=609ec2e6-c877-4fc5-95b7-935ae2549b3a@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=arnd@arndb.de \
--cc=bruno.thomsen@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jm@ti.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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).