From: Kate Hsuan <hpa@redhat.com>
To: Hans de Goede <hansg@kernel.org>,
Miguel Vadillo <miguel.vadillo@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Kate Hsuan <hpa@redhat.com>
Subject: [PATCH] media: i2c: cvs: Add Lattice device quirk for VID:0x2ac1 PID:0x20d1
Date: Fri, 4 Sep 2026 11:43:44 +0800 [thread overview]
Message-ID: <20260904034344.105034-1-hpa@redhat.com> (raw)
On Dell laptops such as the XPS 14 (DA14250), the IPU6 camera fails to
initialize due to a missing device quirk for the Lattice device. The
kernel logs the following error during probe:
[ 7.299665] intel_cvs i2c-INTC10E0:00: No quirks for device (VID:0x2ac1 PID:0x20d1)
[ 7.299976] intel_cvs i2c-INTC10E0:00: error -EREMOTEIO: get caps failed
[ 7.300026] intel_cvs i2c-INTC10E0:00: probe with driver intel_cvs failed with error -121
Add a matching quirk entry for VID 0x2ac1 and PID 0x20d1 to allow
intel_cvs to configure the device properly and enable the camera.
Link: https://bugzilla.redhat.com/show_bug.cgi?id=2526246
Signed-off-by: Kate Hsuan <hpa@redhat.com>
---
drivers/media/i2c/cvs/core.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/media/i2c/cvs/core.c b/drivers/media/i2c/cvs/core.c
index d4a3b9c3bab1..acf8a4f7e79f 100644
--- a/drivers/media/i2c/cvs/core.c
+++ b/drivers/media/i2c/cvs/core.c
@@ -70,6 +70,13 @@ static const struct icvs_device_quirk cvs_quirk_table[] = {
ICVS_NO_CAPS |
ICVS_NO_FW_UPDATE
}, /* Lattice NX33 */
+ { 0x2ac1, 0x20d1, ICVS_NO_MIPI_CONFIG |
+ ICVS_NO_CAPS |
+ ICVS_NO_FW_UPDATE
+ }, /*
+ * The Lattice device was found on a Dell laptop
+ * XPS 14 (Dell 14 Premium) DA14250
+ */
{ 0x06CB, 0x0701, ICVS_SKIP_FW_RESET |
ICVS_HOST_SENSOR_PWR_CTRL |
ICVS_HOST_PRIV_CTRL |
--
2.55.0
reply other threads:[~2026-09-04 3:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260904034344.105034-1-hpa@redhat.com \
--to=hpa@redhat.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=miguel.vadillo@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