From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: 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>,
linux-media@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [PATCH 1/1] media: Don't hide I²C or SPI drivers by default
Date: Tue, 22 Sep 2026 09:38:01 +0300 [thread overview]
Message-ID: <arIiSTLWYwELJqvU@kekkonen.localdomain> (raw)
In-Reply-To: <2b067a4a-6da8-4948-ab50-46f1c6193ed1@leemhuis.info>
Hi Thorsten,
On Mon, Sep 21, 2026 at 09:16:12AM +0200, Thorsten Leemhuis wrote:
> On 9/21/26 08:54, Sakari Ailus wrote:
> > On Sun, Sep 20, 2026 at 10:03:47AM +0800, Junjie Cao wrote:
> >> On Sat, Sep 19, 2026 at 09:10:18AM +0200, Thorsten Leemhuis wrote:
> >>> Also wondering if the "olddefconfig" case on Arch was tested to ensure
> >>> we prevent more people running into problems that Junjie's fix linked to
> >>
> >> Ran it: this patch on its base-commit, Arch's
> >> config.x86_64 (7.2.4.arch1):
> >>
> >> olddefconfig, before: no VIDEO_INTEL_CVS line
> >> olddefconfig, after: # CONFIG_VIDEO_INTEL_CVS is not set
> >>
> >> The option has no default, so olddefconfig leaves it
> >> off. With the patch, oldconfig prompts for it as (NEW)
> >> and listnewconfig lists it.
> >
> > Generally drivers are unselected by default and cvs is no exception.
>
> Yup, sure, but it seems we here due to some oddity (details don't matter
> much) ran into a situation that users perceive as regression (which
> matters a lot).
It was really about this option being hidden by default so you couldn't
even select it. (It's no wonder: I had enabled EXPERT in my own .config,
quite possibly more than 10 years ago, to select things without much
thinking about it!)
> > What I think we could possibly do is to add to cvs Kconfig:
> >
> > default VIDEO_INTEL_IPU6
> >
> > As the cvs driver is (at least right now) used with ipu6 driver only.
>
> Due to what I wrote above I'd say: this sounds like a good solution that
> has no significant downsides -- and avoids a problem for everyone that
> manually configures their kernel in the future, which is a good thing,
> too. And we can easily drop the default later if there is a strong need
> (and then likely should add a hint to the help text which other symbols
> are needed in case it doesn't have one already; didn't check)
I can post a patch. I think what also made a difference was that the CVS
chip was in a different menu because it's an I²C device.
--
Regards,
Sakari Ailus
prev parent reply other threads:[~2026-09-22 6:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 8:17 [PATCH 1/1] media: Don't hide I²C or SPI drivers by default Sakari Ailus
2026-09-18 8:46 ` Hans Verkuil
2026-09-19 7:10 ` Thorsten Leemhuis
2026-09-20 2:03 ` Junjie Cao
2026-09-21 6:54 ` Sakari Ailus
2026-09-21 7:16 ` Thorsten Leemhuis
2026-09-22 6:38 ` Sakari Ailus [this message]
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=arIiSTLWYwELJqvU@kekkonen.localdomain \
--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