Re: [RFC} arm architecture board/feature deprecation timeline

["Arnd Bergmann" <arnd@arndb.de>]

On Mon, Aug 5, 2024, at 14:30, Tony Lindgren wrote:
> * Arnd Bergmann <arnd@arndb.de> [240805 07:58]:
>> Thinking about this some more, I wonder if we should just
>> change the Kconfig dependencies now (for 6.12, possibly backported)
>> and forbid ARM1136r0, i.e. OMAP2 and i.MX31, from being enabled
>> in combination with SMP.
>> 
>> This would immediately prevent the bug you are seeing and
>> allow the cleanups we've been wanting to do for a while,
>> and it would avoid the larger-scale rework that I had
>> planned (moving armv6 into an armv5 kernel).
>> 
>> The main reason we didn't do this in the past was that it broke
>> Tony's workflow of testing omap2plus_defconfig across all
>> platforms, but I assume this all changed with the new group
>> maintainership anyway.
>
> Yes please go ahead, no objection from me.
>
> Also related, the 2430 support could be dropped as AFAIK there
> are no active users for it. It's similar to the 2420 support
> that n8x0 use, and only 2420 support should be kept.

I've taken a look at this, and my feeling is that we would
not gain much dropping 2430 since it has very little unique
hardware, except for a few files in mach-omap2 and drivers/clk.

Keeping it around as long as 2420 seems to be less work
overall, so I won't send patches to drop this one. If anyone
else wants to remove it, please go ahead.

While looking at 2430 support, I did notice that musb support
got lost in the DT conversion, which you mentioned as being
incomplete at the time. This does mean it's almost certainly
not been used for over a decade with an upstream kernel.

      Arnd