From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Miguel Vadillo <miguel.vadillo@intel.com>,
linux-acpi@vger.kernel.org, rafael@kernel.org, lenb@kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
mehdi.djait@linux.intel.com, wei.a.xu@intel.com,
atul.raut@intel.com,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH] ACPI: scan: Honor _DEP for Intel CVS devices
Date: Sun, 13 Sep 2026 23:21:48 +0300 [thread overview]
Message-ID: <aqcF3JmvMKDJSQaE@kekkonen.localdomain> (raw)
In-Reply-To: <d7f4a573-1a2e-4274-8c8f-41d398592356@leemhuis.info>
Hi Thorsten,
On Sun, Sep 13, 2026 at 10:27:15AM +0200, Thorsten Leemhuis wrote:
> On 9/12/26 18:50, Thorsten Leemhuis wrote:
> > On 6/1/26 21:40, Miguel Vadillo wrote:
> >> CVS (Computer Vision Sensing) is an ACPI-enumerated device that sits
> >> inline in the CSI-2 path between the camera sensor and Intel IPU.
> >> On platforms where CVS is present, the camera sensor's ACPI node
> >> declares a _DEP dependency on the CVS device.
> >>
> >> The CVS driver must be fully initialized before camera sensor drivers
> >> probe, because CVS controls the CSI-2 link ownership handshake (via
> >> GPIO REQ/RESP), the MIPI/CSI-2 lane configuration, and the camera
> >> power domain. Without CVS ready, the sensor driver can bind but the
> >> CSI-2 stream will not function correctly.
> >>
> >> The CVS driver calls acpi_dev_clear_dependencies() at the end of its
> >> probe() to unblock waiting consumers once it is ready.
> >>
> >> Move the CVS HIDs from acpi_ignore_dep_ids[] to acpi_honor_dep_ids[]
> >> so that camera sensor enumeration is deferred until the CVS driver has
> >> finished probing, matching the behavior already in place for IVSC.
> >
> > TWIMC, there is a bug report where one or two people claim that this
> > change caused a regression; the report is quite verbose (guess LLM
> > assisted) and hard to grasp for me as outsider; requests for
> > clarifications from my side were not really fruitful. Not sure what to
> > make of this, but I thought I'd let you know; for details see:
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=221988
>
> For completeness, a report that is more straight forward to read (at
> least for me) was now posted here:
> https://lore.kernel.org/all/20260912185836.309071-1-manuel.knitza@googlemail.com/
Thanks for the link, I've replied to the bug report.
--
Kind regards,
Sakari Ailus
prev parent reply other threads:[~2026-09-13 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 19:40 [PATCH] ACPI: scan: Honor _DEP for Intel CVS devices Miguel Vadillo
2026-06-03 7:43 ` Sakari Ailus
2026-06-08 12:21 ` Rafael J. Wysocki
2026-09-12 16:50 ` Thorsten Leemhuis
2026-09-13 8:27 ` Thorsten Leemhuis
2026-09-13 10:38 ` Rafael J. Wysocki (Intel)
2026-09-13 20:21 ` 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=aqcF3JmvMKDJSQaE@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=atul.raut@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mehdi.djait@linux.intel.com \
--cc=miguel.vadillo@intel.com \
--cc=rafael@kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=wei.a.xu@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.