From: Manuel Knitza <manuel.knitza@googlemail.com>
To: junjie.cao@intel.com
Cc: miguel.vadillo@intel.com, mchehab@kernel.org,
sakari.ailus@linux.intel.com, hpa@redhat.com,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Manuel Knitza <manuel.knitza@googlemail.com>
Subject: Re: [PATCH] media: i2c: cvs: Get the wake IRQ without claiming the GPIO
Date: Mon, 14 Sep 2026 11:13:51 +0200 [thread overview]
Message-ID: <20260914091355.148477-1-manuel.knitza@googlemail.com> (raw)
In-Reply-To: <20260908105717.496232-1-junjie.cao@intel.com>
Tested-by: Manuel Knitza <manuel.knitza@googlemail.com>
Answering the DA16260 question you asked in the ipu-bridge thread, and
giving the tag here where it belongs.
Dell XPS 16 DA16260, INTC10E1, ov08x40, linux-ptl 7.2.3. No spk-id
conflict: all four CS35L56 amplifiers bind, no -EBUSY, audio works.
Note what that does and does not show. I am running your change, but as
a DKMS copy of drivers/media/i2c/cvs rather than a kernel build - Arch
derived configs cannot enable CONFIG_VIDEO_INTEL_CVS, exactly as you
described, so the Omarchy packaging carries the in-tree driver as a DKMS
module and applies this patch verbatim on top (omacom/omarchy-pkgs#418).
So it is a test of the patched code, not of the unpatched driver on this
model - I never ran that, and cannot say whether the DA16260 would have
hit the conflict without it.
The rest of your analysis matches what I see. With vision-drivers gated
out and the in-tree driver bound, the graph is as intended:
intel_cvs i2c-INTC10E1:00: Quirks: 0x7a (VID:0x06cb PID:0x0701)
intel_ipu7_isys: bind Intel CVS nlanes is 2 port is 0
intel_ipu7_isys: All sensor registration completed.
"Intel CVS" sits between ov08x40 and Intel IPU7 CSI2 0 on
/dev/v4l-subdev4, the sensor enumerates and frames flow. The
manage.c:1502 WARNING from the out-of-tree module is gone too, since that
driver never had the IRQF_ONESHOT issue.
Thanks for the correction in the other thread - I had claimed there was
no in-tree CVS driver, which was wrong.
Assisted-by: Claude Code:claude-opus-5
prev parent reply other threads:[~2026-09-14 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 10:57 Junjie Cao
2026-09-14 7:50 ` Manuel Knitza
2026-09-14 9:34 ` Junjie Cao
2026-09-14 9:13 ` Manuel Knitza [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=20260914091355.148477-1-manuel.knitza@googlemail.com \
--to=manuel.knitza@googlemail.com \
--cc=hpa@redhat.com \
--cc=junjie.cao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=miguel.vadillo@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®