On Tue, Jul 12, 2022 at 6:42 PM Florian Fainelli <f.fainelli@xxxxxxxxx> wrote:
>
> There are now multiple Broadcom SoCs supported so group them under their
> own menu such that the selection is visually more appealing and we can
> easily add new platforms there in the future. This allows us to move
> ARCH_BRCMSTB back to its siblings.
>
> No functional changes introduced.
>
> Signed-off-by: Florian Fainelli <f.fainelli@xxxxxxxxx>
> ---
>
> Note this is based on "arm64: bcmbca: add arch bcmbca machine entry"
Hi Florian,
So far, we have tried to keep the Kconfig.platforms file rather coarse-grained,
mainly limiting it to company names and high-level families, but avoiding
sub-menus or adding too many sub-families.
If we add per-vendor submenus, we should probably first decide how we
want to structure this across vendors. I've added maintainers and lists to
Cc for a couple of the ones that are in a similar situation.
I can see a couple of ways we can do this:
a) keep the list of platforms as short as possible, combining related
SoC families from a single vendor wherever possible, but no sub-menus
(same as today)
b) Always use sub-menus when there is more than one family, but
keep relatively coarse platform selection.
c) Use sub-menus and also move to a more fine-grained SoC
selection, similar to what we have on 32-bit arm.
I would not really want to go to c), but a) and b) both make sense to
me as long as do it consistently across all platforms.
Any other ideas or opinions?
Arnd
