On 2/11/26 11:15 AM, Vitor Soares via lists.yoctoproject.org wrote:
Hi,
While working on our Toradex Aquila AM69 SoM support, we noticed that k3.inc
defines:
SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS2"
This caused systemd to enable [email protected] on our board, where
ttyS0 maps to main_uart4 - a user-facing UART, not a debug/console UART. The
getty continuously outputs a login prompt, interfering with the interface.
This made us question whether SERIAL_CONSOLES belongs in SoC-level include files
at all. Our understanding is that the console getty is already handled
automatically by systemd-getty-generator from the console= kernel command
line argument, which makes SERIAL_CONSOLES potentially redundant for the console
UART. Any additional UARTs beyond the console are board-specific and arguably
belong in each machine config rather than a shared SoC include.
We are not 100% certain about this reasoning and would love to hear the
rationale behind the current approach. Are we missing something? Would it make
sense to either remove SERIAL_CONSOLES from the SoC includes or at minimum use
a weak assignment (?=) to allow boards to override cleanly?
We simply noticed almost all our EVM boards used the same console UARTs and so
refactored the definition into a more common place. But yes you are correct
that a file like k3.inc seems like it should contain only items common to all
users of the K3 SoC family, and not simply common to TI EVM boards. Changing
the assignment in k3.inc to a weak one seem reasonable (although I think you
can still just override regular assignments after you include k3.conf in
your board conf)
Andrew
Thanks,
Vitor Soares
Toradex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19495):
https://lists.yoctoproject.org/g/meta-ti/message/19495
Mute This Topic: https://lists.yoctoproject.org/mt/117760181/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
