Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Zhentao Guo via B4 Relay" <devnull+zhentao.guo.amlogic.com@kernel.org>
Cc: linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org,
	neil.armstrong@linaro.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH RFC RESEND v5 6/6] arm64: defconfig: Enable CONFIG_VIDEO_AMLOGIC_VDEC
Date: Tue, 26 May 2026 10:52:44 +0000	[thread overview]
Message-ID: <20260526105245.585C01F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260526-b4-s4-vdec-upstream-v5-6-33bc817f93f4@amlogic.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] CONFIG_VIDEO_AMLOGIC_VDEC selects MESON_SM without satisfying its ARM64_4K_PAGES dependency, causing Kconfig warnings under COMPILE_TEST or when using 16K/64K pages.
- [Low] CONFIG_VIDEO_AMLOGIC_VDEC is inserted manually out of order in arm64 defconfig.
--

commit 482a11927128f3e0aa6ba1ce2517d29726af8f3b
Author: Zhentao Guo <zhentao.guo@amlogic.com>

arm64: defconfig: Enable CONFIG_VIDEO_AMLOGIC_VDEC

This commit enables the Amlogic V4L2 stateless video decoder driver as a
module in the arm64 defconfig.

> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 4567f4b34f293..14caac24d2009 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -913,6 +913,7 @@ CONFIG_V4L_PLATFORM_DRIVERS=y
>  CONFIG_SDR_PLATFORM_DRIVERS=y
>  CONFIG_V4L_MEM2MEM_DRIVERS=y
>  CONFIG_VIDEO_AMPHION_VPU=m
> +CONFIG_VIDEO_AMLOGIC_VDEC=m

[Severity: Low]
Does enabling this configuration expose a dependency issue in the driver's
Kconfig?

In the Kconfig definition for VIDEO_AMLOGIC_VDEC introduced earlier in this
patchset, it unconditionally uses select MESON_SM. However, MESON_SM has a
strict dependency on ARM64_4K_PAGES.

Selecting a symbol without meeting its dependencies forces it on, which can
trigger unmet direct dependency warnings during builds on architectures or
configurations where ARM64_4K_PAGES is not met. This can happen on non-ARM64
COMPILE_TEST builds or ARM64 builds configured with 16K or 64K pages.

Could the driver use depends on MESON_SM instead of select to avoid
breaking automated Kconfig build testing?

[Severity: Low]
This isn't a bug, but was this defconfig change generated using make
savedefconfig?

In the media platform Kconfig hierarchy, the Amlogic platform Kconfig is
included before the Amphion platform Kconfig. Running make savedefconfig
would naturally place CONFIG_VIDEO_AMLOGIC_VDEC before
CONFIG_VIDEO_AMPHION_VPU.

Manually inserting it after Amphion will cause unnecessary churn the next
time make savedefconfig is executed.

>  CONFIG_VIDEO_CADENCE_CSI2RX=m
>  CONFIG_VIDEO_WAVE_VPU=m
>  CONFIG_VIDEO_E5010_JPEG_ENC=m

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260526-b4-s4-vdec-upstream-v5-0-33bc817f93f4@amlogic.com?part=6

      reply	other threads:[~2026-05-26 10:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26  8:40 [PATCH RFC RESEND v5 0/6] Add Amlogic stateless H.264 video decoder for S4 Zhentao Guo via B4 Relay
2026-05-26  8:40 ` [PATCH RFC RESEND v5 1/6] firmware: meson: sm: Add video firmware loading SMC call Zhentao Guo via B4 Relay
2026-05-26  9:01   ` sashiko-bot
2026-05-26  8:40 ` [PATCH RFC RESEND v5 2/6] firmware: meson: sm: video firmware loading via secure monitor Zhentao Guo via B4 Relay
2026-05-26  9:18   ` sashiko-bot
2026-05-26  8:40 ` [PATCH RFC RESEND v5 3/6] media: dt-bindings: Add Amlogic V4L2 video decoder Zhentao Guo via B4 Relay
2026-05-26  9:29   ` sashiko-bot
2026-05-26  8:40 ` [PATCH RFC RESEND v5 4/6] decoder: Add V4L2 stateless H.264 decoder driver Zhentao Guo via B4 Relay
2026-05-26 10:04   ` sashiko-bot
2026-05-26  8:40 ` [PATCH RFC RESEND v5 5/6] arm64: dts: amlogic: Add video decoder driver support for S4 SOCs Zhentao Guo via B4 Relay
2026-05-26 10:38   ` sashiko-bot
2026-05-26  8:40 ` [PATCH RFC RESEND v5 6/6] arm64: defconfig: Enable CONFIG_VIDEO_AMLOGIC_VDEC Zhentao Guo via B4 Relay
2026-05-26 10:52   ` sashiko-bot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260526105245.585C01F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=devnull+zhentao.guo.amlogic.com@kernel.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox