Linux Media Controller development
 help / color / mirror / Atom feed
From: Bin Du <Bin.Du@amd.com>
To: Arnd Bergmann <arnd@kernel.org>,
	Nirujogi Pratap <pratap.nirujogi@amd.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sultan Alsawaf <sultan@kerneltoast.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	"Mario Limonciello (AMD)" <superm1@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	King.Li@amd.com, Benjamin.Chan@amd.com
Subject: Re: [PATCH] media: platform: amd: add DRM_AMDGPU dependency
Date: Fri, 15 May 2026 18:48:58 +0800	[thread overview]
Message-ID: <496b1a70-613a-4cca-8db0-a39f933ff1a3@amd.com> (raw)
In-Reply-To: <20260515091212.581789-1-arnd@kernel.org>

Hi Arnd,

Thanks for the fix.

On 5/15/2026 5:12 PM, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> With DRM_AMDGPU=m and DRM_AMD_ISP=y, it is possible to configura
> VIDEO_AMD_ISP4_CAPTURE as built-in, but that fails to link:
> 
> aarch64-linux-ld: drivers/media/platform/amd/isp4/isp4_interface.o: in function `isp4if_gpu_mem_alloc.isra.0':
> isp4_interface.c:(.text+0x1d0): undefined reference to `isp_kernel_buffer_alloc'
> aarch64-linux-ld: drivers/media/platform/amd/isp4/isp4_interface.o: in function `isp4if_dealloc_fw_gpumem':
> isp4_interface.c:(.text+0x26c): undefined reference to `isp_kernel_buffer_free'
> 

I verified this. Reproducing the link failure on the unpatched tree
also requires CONFIG_MEDIA_SUPPORT=y and CONFIG_VIDEO_DEV=y; otherwise
Kconfig downgrades CONFIG_VIDEO_AMD_ISP4_CAPTURE to m.

> Add a dependency on the tristate DRM_AMDGPU symbol in addition to
> the boolean DRM_AMD_ISP=y, so this can only be built-in if
> the ISP driver is also linked into the kernel itself.
> 
> Fixes: 9a54c285630c ("media: platform: amd: Introduce amd isp4 capture driver")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
>  drivers/media/platform/amd/isp4/Kconfig | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/media/platform/amd/isp4/Kconfig b/drivers/media/platform/amd/isp4/Kconfig
> index 55dd2dc453a2..9d1927af1cb8 100644
> --- a/drivers/media/platform/amd/isp4/Kconfig
> +++ b/drivers/media/platform/amd/isp4/Kconfig
> @@ -2,7 +2,9 @@
>  
>  config VIDEO_AMD_ISP4_CAPTURE
>  	tristate "AMD ISP4 and camera driver"
> -	depends on DRM_AMD_ISP && VIDEO_DEV && HAS_DMA
> +	depends on DRM_AMDGPU && DRM_AMD_ISP
> +	depends on HAS_DMA
> +	depends on VIDEO_DEV
>  	select VIDEOBUF2_CORE
>  	select VIDEOBUF2_MEMOPS
>  	select VIDEOBUF2_V4L2

With this patch applied, olddefconfig correctly changes
CONFIG_VIDEO_AMD_ISP4_CAPTURE to m when CONFIG_DRM_AMDGPU=m, avoiding
the link failure.

Reviewed-by: Bin Du <Bin.Du@amd.com>
Tested-by: Bin Du <Bin.Du@amd.com>


      reply	other threads:[~2026-05-15 10:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15  9:12 [PATCH] media: platform: amd: add DRM_AMDGPU dependency Arnd Bergmann
2026-05-15 10:48 ` Bin Du [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=496b1a70-613a-4cca-8db0-a39f933ff1a3@amd.com \
    --to=bin.du@amd.com \
    --cc=Benjamin.Chan@amd.com \
    --cc=King.Li@amd.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=pratap.nirujogi@amd.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sultan@kerneltoast.com \
    --cc=superm1@kernel.org \
    /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