From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: bingbu.cao@intel.com, laurent.pinchart@ideasonboard.com,
andriy.shevchenko@linux.intel.com, hdegoede@redhat.com,
ilpo.jarvinen@linux.intel.com, claus.stovgaard@gmail.com,
tomi.valkeinen@ideasonboard.com, tfiga@chromium.org,
senozhatsky@chromium.org, andreaskleist@gmail.com,
bingbu.cao@linux.intel.com, tian.shu.qiu@intel.com,
hongju.wang@intel.com
Subject: [PATCH v4 15/19] media: Kconfig: Select MEDIA_CONTROLLER for VIDEO_V4L2_SUBDEV_API
Date: Tue, 16 Apr 2024 23:11:01 +0300 [thread overview]
Message-ID: <20240416201105.781496-16-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <20240416201105.781496-1-sakari.ailus@linux.intel.com>
MEDIA_CONTROLLER has no dependencies and VIDEO_V4L2_SUBDEV_API depends on
it. Select MEDIA_CONTROLLER instead of depending on it. This way Kconfig
options elsewhere do only need to select VIDEO_V4L2_SUBDEV_API, not both.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
drivers/media/v4l2-core/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/media/v4l2-core/Kconfig b/drivers/media/v4l2-core/Kconfig
index 331b8e535e5b..d55eff3f31b0 100644
--- a/drivers/media/v4l2-core/Kconfig
+++ b/drivers/media/v4l2-core/Kconfig
@@ -10,7 +10,8 @@ config VIDEO_V4L2_I2C
config VIDEO_V4L2_SUBDEV_API
bool
- depends on VIDEO_DEV && MEDIA_CONTROLLER
+ depends on VIDEO_DEV
+ select MEDIA_CONTROLLER
help
Enables the V4L2 sub-device pad-level userspace API used to configure
video format, size and frame rate between hardware blocks.
--
2.39.2
next prev parent reply other threads:[~2024-04-16 20:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 20:10 [PATCH v4 00/19] Intel IPU6 and IPU6 input system drivers Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 01/19] media: ipu6: Add PCI device table header Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 02/19] media: ivsc: csi: Use IPU bridge Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 03/19] media: intel/ipu6: add Intel IPU6 PCI device driver Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 04/19] media: intel/ipu6: add IPU auxiliary devices Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 05/19] media: intel/ipu6: add IPU6 buttress interface driver Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 06/19] media: intel/ipu6: CPD parsing for get firmware components Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 07/19] media: intel/ipu6: add IPU6 DMA mapping API and MMU table Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 08/19] media: intel/ipu6: add syscom interfaces between firmware and driver Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 09/19] media: intel/ipu6: input system ABI " Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 10/19] media: intel/ipu6: add IPU6 CSI2 receiver v4l2 sub-device Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 11/19] media: intel/ipu6: add the CSI2 DPHY implementation Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 12/19] media: intel/ipu6: input system video nodes and buffer queues Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 13/19] media: intel/ipu6: add the main input system driver Sakari Ailus
2024-04-16 20:11 ` [PATCH v4 14/19] media: intel/ipu6: add Kconfig and Makefile Sakari Ailus
2024-04-16 20:11 ` Sakari Ailus [this message]
2024-04-16 20:11 ` [PATCH v4 16/19] MAINTAINERS: add maintainers for Intel IPU6 input system driver Sakari Ailus
2024-04-16 20:11 ` [PATCH v4 17/19] media: intel/ipu6: support line-based metadata capture support Sakari Ailus
2024-04-16 20:11 ` [PATCH v4 18/19] Documentation: add Intel IPU6 ISYS driver admin-guide doc Sakari Ailus
2024-04-16 20:11 ` [PATCH v4 19/19] Documentation: add documentation of Intel IPU6 driver and hardware overview Sakari Ailus
2024-04-17 7:56 ` [PATCH v4 00/19] Intel IPU6 and IPU6 input system drivers Hans de Goede
2024-04-17 8:34 ` Sakari Ailus
2024-04-17 8:59 ` Hans de Goede
2024-04-17 11:33 ` Bingbu Cao
2024-04-17 12:29 ` 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=20240416201105.781496-16-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=andreaskleist@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=bingbu.cao@linux.intel.com \
--cc=claus.stovgaard@gmail.com \
--cc=hdegoede@redhat.com \
--cc=hongju.wang@intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=tfiga@chromium.org \
--cc=tian.shu.qiu@intel.com \
--cc=tomi.valkeinen@ideasonboard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.