[PATCH] ARM: omap: rework platform selection

Rob Herring robherring2 at gmail.com
Tue Jun 17 08:03:07 PDT 2014


On Tue, Jun 17, 2014 at 8:57 AM, Arnd Bergmann <arnd at arndb.de> wrote:
> On Monday 16 June 2014, Rob Herring wrote:
>> > So far I have not come up with no great ideas on fixing this
>> > properly short of requiring all omap .config files to add
>> > CONFIG_ARCH_OMAP=y manually. Anybody got good ideas for that?
>>
>> I've failed to come up with anything...
>>
>
> I have two ideas, but neither is great:
>
> a) we leave the individual per-soc options in the top-level menu
>    and move the sub-options under those. This is a bit or a problem
>    for options concerning all of OMAP, but I'm not sure how many of
>    those are actually required.
>
> b) We go back to Rob's version and make CONFIG_ARCH_OMAP the
>    user-selectable option, and then find another solution for
>    building a kernel with ARCH_OMAP set but none of individual
>    options. This will work for anybody who has a full .config
>    file, but still break the 'make savedefconfig' generated ones.

After playing with this more yesterday, I think ARCH_OMAP2PLUS instead
of ARCH_OMAP is actually a better choice to make the menuconfig item.
It still has the same defconfig issues, but doesn't affect OMAP1.

Doing your trick of a default selection with "select ARCH_OMAP2 if
!(ARCH_OMAP3 || ARCH_OMAP4 || ...)" in the menuconfig option can fix
the build issues. We'd actually need 2 selects for v6 and v7 only
builds.

Rob



More information about the linux-arm-kernel mailing list