Re: [PATCH v16 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] Defconfig regression: legacy driver disabled without enabling replacement
--

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

arm64: defconfig: disable deprecated MAX96712 driver

This commit removes the legacy staging MAX96712 driver configuration from
the arm64 defconfig as part of migrating functionality to the MAX96724
driver framework.

> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 654a102cb5bc5..a5419f2a4d5ba 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -1411,7 +1411,6 @@ CONFIG_GREYBUS=m
>  CONFIG_GREYBUS_BEAGLEPLAY=m
>  CONFIG_STAGING=y
>  CONFIG_STAGING_MEDIA=y
> -CONFIG_VIDEO_MAX96712=m

[Severity: Medium]
Does removing this configuration without adding a replacement result in a
regression for arm64 defconfig users?

The legacy driver configuration is removed here, but no corresponding entry
for the new driver (e.g., CONFIG_VIDEO_MAX96724=m) is added. While the actual
MAX96724 driver code is added later in this patch series (in the patch
"media: i2c: maxim-serdes: add MAX96724 driver"), the defconfig is never
updated to include the new CONFIG_VIDEO_MAX96724=m configuration in any
subsequent patch.

Should CONFIG_VIDEO_MAX96724=m be added to maintain out-of-the-box support
for these devices when building the kernel using the default arm64 defconfig?

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

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260831-gmsl2-3_serdes-v16-0-4fa6e08bb514@analog.com?part=18