From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Bingbu Cao <bingbu.cao@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Andreas Helbech Kleist <andreaskleist@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Tianshu Qiu <tian.shu.qiu@intel.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: ipu-bridge: fix ipu6 Kconfig dependencies
Date: Mon, 29 Jul 2024 07:03:17 +0000 [thread overview]
Message-ID: <Zqc-tY7LPLdEbZ-9@kekkonen.localdomain> (raw)
In-Reply-To: <20240719095403.3607027-1-arnd@kernel.org>
Hi Arnd,
On Fri, Jul 19, 2024 at 11:53:50AM +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> Commit 4670c8c3fb04 ("media: ipu-bridge: Fix Kconfig dependencies") changed
> how IPU_BRIDGE dependencies are handled for all drivers, but the IPU6 variant
> was added the old way, which causes build time warnings when I2C is turned
> off:
>
> WARNING: unmet direct dependencies detected for IPU_BRIDGE
> Depends on [n]: MEDIA_SUPPORT [=m] && PCI [=y] && MEDIA_PCI_SUPPORT [=y] && (ACPI [=y] || COMPILE_TEST [=y]) && I2C [=n]
> Selected by [m]:
> - VIDEO_INTEL_IPU6 [=m] && MEDIA_SUPPORT [=m] && PCI [=y] && MEDIA_PCI_SUPPORT [=y] && (ACPI [=y] || COMPILE_TEST [=y]) && VIDEO_DEV [=m] && X86 [=y] && X86_64 [=y] && HAS_DMA [=y]
>
> To make it consistent with the other IPU drivers as well as avoid this warning,
> change the 'select' into 'depends on'.
Thanks for the patch. I'm not sure how I managed to miss the IPU6 driver...
I think we also need, besides IPU_BRIDGE, || !IPU_BRIDGE, as the IPU_BRIDGE
has additional dependencies (I2C) compared to VIDEO_INTEL_IPU6. I'll add
that while applying. Please let me know if you have concerns.
>
> Fixes: c70281cc83d6 ("media: intel/ipu6: add Kconfig and Makefile")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/media/pci/intel/ipu6/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/pci/intel/ipu6/Kconfig b/drivers/media/pci/intel/ipu6/Kconfig
> index 154343080c82..ffadf03478a8 100644
> --- a/drivers/media/pci/intel/ipu6/Kconfig
> +++ b/drivers/media/pci/intel/ipu6/Kconfig
> @@ -3,13 +3,13 @@ config VIDEO_INTEL_IPU6
> depends on ACPI || COMPILE_TEST
> depends on VIDEO_DEV
> depends on X86 && X86_64 && HAS_DMA
> + depends on IPU_BRIDGE
> select DMA_OPS
> select IOMMU_IOVA
> select VIDEO_V4L2_SUBDEV_API
> select MEDIA_CONTROLLER
> select VIDEOBUF2_DMA_CONTIG
> select V4L2_FWNODE
> - select IPU_BRIDGE
> help
> This is the 6th Gen Intel Image Processing Unit, found in Intel SoCs
> and used for capturing images and video from camera sensors.
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2024-07-29 7:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 9:53 Arnd Bergmann
2024-07-29 7:03 ` Sakari Ailus [this message]
2024-07-29 7:24 ` Arnd Bergmann
2024-07-29 7:37 ` Sakari Ailus
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=Zqc-tY7LPLdEbZ-9@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=andreaskleist@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bingbu.cao@intel.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=tian.shu.qiu@intel.com \
/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
all inboxes | Powered by JetHome®