Linux Media Controller development
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: hverkuil@xs4all.nl, laurent.pinchart@ideasonboard.com
Subject: [PATCH 1/1] media: Kconfig: Select MEDIA_CONTROLLER for VIDEO_V4L2_SUBDEV_API
Date: Mon,  4 Mar 2024 20:51:25 +0200	[thread overview]
Message-ID: <20240304185125.33713-1-sakari.ailus@linux.intel.com> (raw)

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>
---
Mostly untested but seems reasonable. MEDIA_CONTROLLER has no dependencies
anymore.

 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


             reply	other threads:[~2024-03-04 18:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 18:51 Sakari Ailus [this message]
2024-03-04 22:59 ` [PATCH 1/1] media: Kconfig: Select MEDIA_CONTROLLER for VIDEO_V4L2_SUBDEV_API Laurent Pinchart
2024-03-05  6:50   ` Sakari Ailus
2024-05-23  8:53     ` Laurent Pinchart
2024-05-23  9:48       ` 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=20240304185125.33713-1-sakari.ailus@linux.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.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