From: Vasu <vasuhansalia05@gmail.com>
To: platform-driver-x86@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
andriy.shevchenko@linux.intel.com, djrscally@gmail.com,
mika.westerberg@linux.intel.com,
Vasu Hansalia <vasuhansalia05@gmail.com>
Subject: [PATCH 1/2] pinctrl: intel: platform: Add INTC10B5 ACPI ID for Lunar Lake
Date: Sun, 5 Apr 2026 00:32:35 +0530 [thread overview]
Message-ID: <20260404190236.5218-1-vasuhansalia05@gmail.com> (raw)
From: Vasu Hansalia <vasuhansalia05@gmail.com>
Intel Lunar Lake platforms (Core Ultra 200V series) use INTC10B5 as
the ACPI hardware ID for the GPIO controller that manages power to
the integrated MIPI camera sensor.
Without this entry, the pinctrl-intel-platform driver does not bind
to the GPIO controller, causing int3472-discrete to report:
int3472-discrete INT3472:00: cannot find GPIO chip INTC10B5:00, deferring
This prevents the camera sensor from being powered on entirely.
Tested on: Dell Pro 14 Premium PA14250, Intel Core Ultra 7 266V
(Lunar Lake), Ubuntu 24.04, kernel 6.11.0-1016-oem
Signed-off-by: Vasu Hansalia <vasuhansalia05@gmail.com>
---
--- a/drivers/pinctrl/intel/pinctrl-intel-platform.c
+++ b/drivers/pinctrl/intel/pinctrl-intel-platform.c
@@ -204,6 +204,7 @@
static const struct acpi_device_id intel_platform_pinctrl_acpi_match[] = {
{ "INTC105F" },
+ { "INTC10B5" },
{ }
};
MODULE_DEVICE_TABLE(acpi, intel_platform_pinctrl_acpi_match);
next reply other threads:[~2026-04-04 19:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 19:02 Vasu [this message]
2026-04-04 19:02 ` [PATCH 2/2] platform/x86: int3472: Handle GPIO types 0x02 and 0x12 for Lunar Lake Vasu
2026-04-04 19:55 ` Andy Shevchenko
2026-04-05 1:34 ` Vasu
2026-04-05 9:01 ` Andy Shevchenko
2026-04-05 9:15 ` Vasu
2026-04-05 9:27 ` Vasu
2026-04-05 16:10 ` Andy Shevchenko
2026-04-04 19:52 ` [PATCH 1/2] pinctrl: intel: platform: Add INTC10B5 ACPI ID " Andy Shevchenko
2026-04-05 1:34 ` Vasu
2026-04-05 8:59 ` Andy Shevchenko
2026-04-05 9:15 ` Vasu
2026-04-05 16:17 ` Andy Shevchenko
2026-04-05 16:33 ` Vasu
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=20260404190236.5218-1-vasuhansalia05@gmail.com \
--to=vasuhansalia05@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=djrscally@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
/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