From: Arun T <arun.t@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Miguel Vadillo <miguel.vadillo@intel.com>
Cc: Len Brown <lenb@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Mehdi Djait <mehdi.djait@intel.com>,
linux-acpi@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 4/4] media: i2c: cvs: Add NVL ACPI ID
Date: Sat, 4 Jul 2026 22:48:55 +0530 [thread overview]
Message-ID: <20260704171855.1462214-5-arun.t@intel.com> (raw)
In-Reply-To: <20260704171855.1462214-1-arun.t@intel.com>
Add INTC10FA to the CVS ACPI match table so the driver can bind to
CVS devices exposed on NVL platforms.
Signed-off-by: Arun T <arun.t@intel.com>
---
drivers/media/i2c/cvs/core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/i2c/cvs/core.c b/drivers/media/i2c/cvs/core.c
index 8270d93f1abe..7486815b16bd 100644
--- a/drivers/media/i2c/cvs/core.c
+++ b/drivers/media/i2c/cvs/core.c
@@ -965,6 +965,7 @@ static const struct acpi_device_id intel_cvs_acpi_match[] = {
{ "INTC10DE" }, /* LNL */
{ "INTC10E0" }, /* ARL */
{ "INTC10E1" }, /* PTL */
+ { "INTC10FA" }, /* NVL */
{ }
};
MODULE_DEVICE_TABLE(acpi, intel_cvs_acpi_match);
--
2.43.0
next prev parent reply other threads:[~2026-07-04 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 17:18 [PATCH v2 0/4] Add NVL CVS/IPU8 camera support Arun T
2026-07-04 17:18 ` [PATCH v2 1/4] ACPI: scan: Honor ACPI _DEP dependency for NVL CVS Arun T
2026-07-06 17:53 ` Rafael J. Wysocki (Intel)
2026-07-04 17:18 ` [PATCH v2 2/4] media: pci: ipu-bridge: Add NVL CVS ACPI ID Arun T
2026-07-04 17:18 ` [PATCH v2 3/4] media: i2c: cvs: Add IPU8 PCI device ID Arun T
2026-07-04 17:18 ` Arun T [this message]
2026-07-04 19:04 ` [PATCH v2 0/4] Add NVL CVS/IPU8 camera support 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=20260704171855.1462214-5-arun.t@intel.com \
--to=arun.t@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=mchehab@kernel.org \
--cc=mehdi.djait@intel.com \
--cc=miguel.vadillo@intel.com \
--cc=rafael@kernel.org \
--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