From: Antti Laakso <antti.laakso@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org,
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>,
Mehdi Djait <mehdi.djait@linux.intel.com>,
regressions@lists.linux.dev
Subject: Re: [PATCH 1/1] media: cvs: Default selection to VIDEO_INTEL_IPU6
Date: Wed, 23 Sep 2026 15:21:39 +0300 [thread overview]
Message-ID: <arPEU7Sk9NCBbSdh@alaakso-desk> (raw)
In-Reply-To: <20260922064017.371437-1-sakari.ailus@linux.intel.com>
On Tue, Sep 22, 2026 at 09:40:17AM +0300, Sakari Ailus wrote:
> The cvs driver is only usable with the Intel ipu6 driver and is commonly
> required for the ipu6 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>
> ---
> 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: 508a3559448684c4c0110a0c1614deaface399c4
> --
> 2.47.3
>
Reviewed-by: Antti Laakso <antti.laakso@linux.intel.com>
next prev parent reply other threads:[~2026-09-23 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 6:40 [PATCH 1/1] media: cvs: Default selection to VIDEO_INTEL_IPU6 Sakari Ailus
2026-09-23 12:21 ` Antti Laakso [this message]
2026-09-23 12:44 ` Mehdi Djait
2026-09-23 21:04 ` Sakari Ailus
2026-09-23 18:10 ` Vadillo, Miguel
2026-09-23 21:06 ` 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=arPEU7Sk9NCBbSdh@alaakso-desk \
--to=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 \
--cc=sakari.ailus@linux.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 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.