Re: [PATCH v17 18/22] arm64: defconfig: disable deprecated MAX96712 driver

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Hardware support regression in defconfig due to missing replacement driver configuration.
--

commit 6d2a73bbf4a355a233e8e7a8d94395d3c7941765
Author: Cosmin Tanislav <demonsingur@gmail.com>

arm64: defconfig: disable deprecated MAX96712 driver

This commit removes the deprecated CONFIG_VIDEO_MAX96712 from the arm64
defconfig. The commit message states that the driver's functionality has
been moved to the MAX96724 driver framework.

> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 6ec8d3a69c98e..e0bdfffd9c525 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -1420,7 +1420,6 @@ CONFIG_GREYBUS=m
>  CONFIG_GREYBUS_BEAGLEPLAY=m
>  CONFIG_STAGING=y
>  CONFIG_STAGING_MEDIA=y
> -CONFIG_VIDEO_MAX96712=m

[Severity: Medium]
Will this cause an out-of-the-box hardware support regression when building
an arm64 kernel using defconfig?

When deploying a kernel built with make defconfig to a board equipped with
the MAX96712 deserializer (such as the Renesas Falcon or White Hawk), it
appears this change will result in lost hardware support. While the old
driver config is removed here, the replacement driver config
(CONFIG_VIDEO_MAX96724) is never added to the defconfig in this patch or
in any subsequent patch in the series.

Could we add CONFIG_VIDEO_MAX96724=m to the defconfig at the same time to
ensure these platforms maintain support for this hardware?

>  CONFIG_VIDEO_MESON_VDEC=m
>  CONFIG_SND_BCM2835=m
>  CONFIG_CHROME_PLATFORMS=y

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260909-gmsl2-3_serdes-v17-0-002499e534e8@analog.com?part=18