Re: [PATCH v2 7/8] arm: u8500: Switch Stemmy to upstream Janice device tree

Stephan Gerhold <[email protected]>
Newsgroups org.u-boot-project.lists.u-boot
Message-ID <[email protected]>
On Mon, Aug 17, 2026 at 11:31:56AM +0200, Linus Walleij wrote:
> Use the upstream Samsung Janice device tree as the initial target for
> the Stemmy configuration. This also prepares the board to share the
> upstream Ux500 Samsung device trees with Linux.
> 
> U-Boot does not yet implement the U8500 clock providers used by the
> upstream device tree. Add a U-Boot-specific overlay with the known MTU
> clock rate and a fixed input clock for the external SD controller.
> 
> Signed-off-by: Linus Walleij <[email protected]>

Hm okay so you're basically dropping support for the internal eMMC in
this patch? Can we support both? BOOTSTD should be able to scan multiple
storages for boot targets.

I'm also not really sure about selecting Janice as "default" device tree
here. Do you expect users to change this setting when they want to build
stemmy for another board?

I wonder if we could continue using a single generic binary for all
boards using CONFIG_MULTI_DTB_FIT. We should have "fw_mach" in
board/ste/stemmy/stemmy.c that should tell us which device we are
running on, which seems to be mostly(?) unique:

https://github.com/stericsson-mainline/android_kernel/blob/9508895090960012f916561b2ede5eaf8124fabd/arch/arm/tools/mach-types#L3956-L3965

I'm not sure about codina-tmo, you would need to check which number the
bootloader passes.

If these numbers are unique, it should be easy to implement
board_fit_config_name_match().

Thanks,
Stephan
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.