[PATCH v2 0/6] arm: omap: Add back omap4 support

[Bastien Curutchet]

Hi all,

On 5/21/26 8:45 AM, Bastien Curutchet wrote:
> Hi all,
> 
> This series aims to add back the omap4 support. This support was removed
> by commit b0ee3fe642c ("arm: ti: Remove omap4 platform support") because
> at that moment, none of the OMAP4-based boards had done the migration to
> DM_I2C.
> My use case is an old product based on the Variscite's omap4 system on
> module. I needed to upgrade U-Boot on it for security reasons. I think
> that this work could benefit to other people who may have same kind of
> product to maintain.
> 
> Patch 1 to 3 remove the omap's clock driver dependency to the AM33xx
> as it is also present in omap4 platforms. I tested these changes on the
> beaglebone black to ensure I didn't break the AM33xx case.
> 
> Patch 4 & 5 revert the deletion of the omap4 support. The revert makes
> checkpatch.pl angry. I fixed quite a lots of warnings already but it
> remains two kinds of warnings:
> - CamelCase on timings structure, I left the CamelCase because IMHO it's
>    more readable this way.
> - #ifdef CONFIG_XYZ shouldn't be used anymore. I left one of this because
>    I didn't find a clean way to get rid of it.
> 
> Patch 6 adds support for the Variscite's system on module. This system on
> module is supported by the Linux project through
> ti/omap/omap4-var-som-om44.dtsi
> 
> Signed-off-by: Bastien Curutchet <bastien.curutchet at bootlin.com>
> ---
> Changes in v2:
> - PATCH 5: Set myself as OMAP4 maintainer
> - PATCH 6: Set SYS_CONFIG_NAME to ti_omap4_common to get rid of omap4_var_som.h
> - Link to v1: https://lore.kernel.org/r/20260519-omap4-support-v1-0-b4a2a7435775@bootlin.com
> 

Gentle ping here, has anyone had time to take a look at this ?


Best regards,
Bastien