From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
Junjie Cao <junjie.cao@intel.com>,
Miguel Vadillo <miguel.vadillo@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Manuel Knitza <manuel.knitza@googlemail.com>,
Antti Laakso <antti.laakso@linux.intel.com>,
Mehdi Djait <mehdi.djait@linux.intel.com>,
regressions@lists.linux.dev
Subject: [PATCH v2 1/1] media: cvs: Default selection to VIDEO_INTEL_IPU6
Date: Thu, 24 Sep 2026 00:14:49 +0300 [thread overview]
Message-ID: <20260923211449.904157-1-sakari.ailus@linux.intel.com> (raw)
The cvs driver is only usable with the Intel ipu6 driver (as well as the
ipu7 staging driver, as long as it exists in the staging tree) and is
commonly required for the ipu6 (or ipu7 staging) driver to function. Make
the default of the cvs driver the same as what was selected for the ipu6
driver.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Reviewed-by: Antti Laakso <antti.laakso@linux.intel.com>
---
drivers/media/i2c/cvs/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/i2c/cvs/Kconfig b/drivers/media/i2c/cvs/Kconfig
index 4309d20dd726..f482f1ccc38a 100644
--- a/drivers/media/i2c/cvs/Kconfig
+++ b/drivers/media/i2c/cvs/Kconfig
@@ -4,6 +4,7 @@ config VIDEO_INTEL_CVS
tristate "Intel CVS CSI-2 bridge support"
depends on I2C && ACPI && VIDEO_DEV
depends on IPU_BRIDGE || !IPU_BRIDGE
+ default VIDEO_INTEL_IPU6
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
select V4L2_FWNODE
base-commit: 8fef4162ebd9936f540f026edb76ec120cd6ffde
--
2.47.3
next reply other threads:[~2026-09-23 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 21:14 Sakari Ailus [this message]
2026-09-24 13:46 ` [PATCH v2 1/1] media: cvs: Default selection to VIDEO_INTEL_IPU6 Mehdi Djait
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=20260923211449.904157-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=antti.laakso@linux.intel.com \
--cc=junjie.cao@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=manuel.knitza@googlemail.com \
--cc=mchehab@kernel.org \
--cc=mehdi.djait@linux.intel.com \
--cc=miguel.vadillo@intel.com \
--cc=regressions@leemhuis.info \
--cc=regressions@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