X86 platform drivers
 help / color / mirror / Atom feed
From: Vasu <vasuhansalia05@gmail.com>
To: andriy.shevchenko@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org,
	mika.westerberg@linux.intel.com,
	Vasu Hansalia <vasuhansalia05@gmail.com>
Subject: Re: [PATCH 1/2] pinctrl: intel: platform: Add INTC10B5 ACPI ID for Lunar Lake
Date: Sun,  5 Apr 2026 07:37:42 +0530	[thread overview]
Message-ID: <20260405020742.34869-1-vasuhansalia05@gmail.com> (raw)
In-Reply-To: <adFsG9mTkoE3kIF4@ashevche-desk.local>

From: Vasu Hansalia <vasuhansalia05@gmail.com>

Hi Andy,

Thank you for confirming this is a BIOS bug.

I have filed the issue in the following places:

1. Ubuntu Launchpad bug tracker:
   https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2131016

2. Intel ipu7-drivers issue tracker:
   https://github.com/intel/ipu7-drivers/issues/26

Unfortunately I could not find an official Dell bug tracker or public
repository where BIOS/firmware bugs can be reported. Dell does not appear
to have a public GitHub repository for BIOS bugs unlike other vendors.

Since Intel has a direct relationship with Dell OEM, would it be possible
for you or someone at Intel to escalate this BIOS _CID issue to Dell's
firmware team? This affects all Lunar Lake Dell laptops (PA14250, XPS 13
9350) running Linux.

The affected users are currently unable to use the camera in any native
Linux application. A BIOS fix from Dell would resolve this permanently
without requiring a kernel workaround.

Thank you for your help.

Regards,
Vasu Hansalia

      parent reply	other threads:[~2026-04-05  2:08 UTC|newest]

Thread overview: 15+ 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
2026-04-05 16:33           ` Vasu
2026-04-05  2:07   ` Vasu [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=20260405020742.34869-1-vasuhansalia05@gmail.com \
    --to=vasuhansalia05@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --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