Linux-GPIO Archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Vasu <vasuhansalia05@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	djrscally@gmail.com, mika.westerberg@linux.intel.com
Subject: Re: [PATCH 1/2] pinctrl: intel: platform: Add INTC10B5 ACPI ID for Lunar Lake
Date: Sun, 5 Apr 2026 19:17:48 +0300	[thread overview]
Message-ID: <adKLLO1oKOy1tjdo@ashevche-desk.local> (raw)
In-Reply-To: <20260405091518.5322-1-vasuhansalia05@gmail.com>

On Sun, Apr 05, 2026 at 02:45:17PM +0530, Vasu wrote:
> 
> Yes, multiple PA14250 variants are already on the market and shipping.
> The Core Ultra 5 variants ship with Ubuntu 24.04 and are Ubuntu-certified.
> The Dell Pro 13 Plus (PB13250) with Core Ultra 7 266V is also
> Ubuntu-certified. My device, the PA14250 with Core Ultra 7 266V, ships
> with Windows 11.
> 
> All of these Lunar Lake Dell laptops share the same ACPI BIOS issue with
> INTC10B5 not having _CID set properly.

Okay, you misinterpreted the SoC's GPIO with external component. The problem is
you forgot (or distro, in that case file a bug in their respective bugzilla) to
have the proper LJCA driver(s) be enabled.

Another possibility that they are using old kernel.

You can spent 5 minutes by checking yourself:

$ git grep -n -w INTC10B5
drivers/gpio/gpio-usbio.c:31:   { "INTC10B5" }, /* LNL */
drivers/usb/misc/usb-ljca.c:182:        { "INTC10B5" }, /* LNL LJCA GPIO */

Overall, your series is not needed at all.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-04-05 16:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-04 19:02 [PATCH 1/2] pinctrl: intel: platform: Add INTC10B5 ACPI ID for Lunar Lake Vasu
2026-04-04 19:02 ` [PATCH 2/2] platform/x86: int3472: Handle GPIO types 0x02 and 0x12 " 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 [this message]
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=adKLLO1oKOy1tjdo@ashevche-desk.local \
    --to=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 \
    --cc=vasuhansalia05@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).