From: Stephan Gerhold <stephan.gerhold@linaro.org>
To: Linus Walleij <linusw@kernel.org>
Cc: u-boot@lists.u-boot-project.org, Tom Rini <trini@konsulko.com>,
Stefan Hansson <newbyte@postmarketos.org>
Subject: Re: [PATCH v2 7/8] arm: u8500: Switch Stemmy to upstream Janice device tree
Date: Mon, 17 Aug 2026 18:45:28 +0200 [thread overview]
Message-ID: <aoM6qJ32H35aumPL@linaro.org> (raw)
In-Reply-To: <20260817-ux500-external-sdcard-v2-7-ca9a110bd9c6@kernel.org>
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 <linusw@kernel.org>
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
next prev parent reply other threads:[~2026-08-17 16:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 9:31 [PATCH v2 0/8] arm: u8500: Enable upstream DT based SD card boot Linus Walleij
2026-08-17 9:31 ` [PATCH v2 1/8] pinctrl: Add compact Nomadik pin controller Linus Walleij
2026-08-17 15:57 ` Stephan Gerhold
2026-08-17 9:31 ` [PATCH v2 2/8] mmc: arm_pl180: Configure Ux500 signal direction Linus Walleij
2026-08-17 15:59 ` Stephan Gerhold
2026-08-17 9:31 ` [PATCH v2 3/8] mmc: arm_pl180: Set initial supply voltages Linus Walleij
2026-08-17 16:15 ` Stephan Gerhold
2026-08-17 9:31 ` [PATCH v2 4/8] power: regulator: Add AB8500 AUX3 support Linus Walleij
2026-08-17 16:21 ` Stephan Gerhold
2026-08-17 9:31 ` [PATCH v2 5/8] configs: stemmy: Enable SD card regulators Linus Walleij
2026-08-17 16:24 ` Stephan Gerhold
2026-08-17 9:31 ` [PATCH v2 6/8] configs: stemmy: Boot EFI from external SD card Linus Walleij
2026-08-17 16:29 ` Stephan Gerhold
2026-08-17 9:31 ` [PATCH v2 7/8] arm: u8500: Switch Stemmy to upstream Janice device tree Linus Walleij
2026-08-17 16:45 ` Stephan Gerhold [this message]
2026-08-17 20:54 ` Linus Walleij
2026-08-17 9:31 ` [PATCH v2 8/8] arm: u8500: Give Golden panel regulators unique names Linus Walleij
2026-08-17 16:47 ` Stephan Gerhold
2026-08-17 20:36 ` Linus Walleij
2026-08-17 21:14 ` Tom Rini
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=aoM6qJ32H35aumPL@linaro.org \
--to=stephan.gerhold@linaro.org \
--cc=linusw@kernel.org \
--cc=newbyte@postmarketos.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.