From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Thierry Chatard <tchatard@gmail.com>
Cc: linux-kernel@vger.kernel.org, hansg@kernel.org, lee@kernel.org,
platform-driver-x86@vger.kernel.org,
ilpo.jarvinen@linux.intel.com, djrscally@gmail.com,
dan.scally@ideasonboard.com, linux-media@vger.kernel.org,
mchehab@kernel.org, sakari.ailus@linux.intel.com,
jacopo.mondi@ideasonboard.com, nicholas@rothemail.net,
v.vitovt@gmail.com, dmanresa@gmail.com,
Hans de Goede <johannes.goede@oss.qualcomm.com>
Subject: Re: [PATCH v11 2/9] mfd: intel-lpss: add Dell Latitude 7275 to the resource conflict quirk
Date: Thu, 1 Oct 2026 10:06:08 +0300 [thread overview]
Message-ID: <ar4GYJvy_w-ZMJb4@ashevche-desk.local> (raw)
In-Reply-To: <20260930214321.600863-3-tchatard@gmail.com>
On Wed, Sep 30, 2026 at 02:43:14PM -0700, Thierry Chatard wrote:
> The Dell Latitude 7275 2-in-1 has the same BIOS bug as the Latitude 5285:
> the ACPI GEXP device declares an OperationRegion (BAR0) on the GNVS
> variable SB04 and the I2C4 controller (INT3446) builds its _CRS from that
> same variable, so intel_lpss_acpi fails to bind the controller with
> -EBUSY and the front camera sensor (OV5670, INT3479) is never registered
> unless acpi_enforce_resources=lax is passed.
>
> Add the machine to the DMI table so QUIRK_IGNORE_RESOURCE_CONFLICTS is
> applied to INT3446 on it as well.
> Assisted-by: Claude Code:claude-fable-5-1
Assisted-by: LLM
With the above being corrected,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-10-01 7:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 21:43 [PATCH v11 0/9] Enable cameras on Dell Latitude 5285 2-in-1 Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 1/9] mfd: intel-lpss: add resource conflict quirk for Dell Latitude 5285 Thierry Chatard
2026-10-01 5:32 ` Sakari Ailus
2026-10-01 7:05 ` Andy Shevchenko
2026-10-01 7:24 ` Sakari Ailus
2026-09-30 21:43 ` [PATCH v11 2/9] mfd: intel-lpss: add Dell Latitude 7275 to the resource conflict quirk Thierry Chatard
2026-10-01 7:06 ` Andy Shevchenko [this message]
2026-09-30 21:43 ` [PATCH v11 3/9] platform/x86: int3472: tps68470: use unsigned int for GPIO lookup loop counters Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 4/9] platform/x86: int3472: tps68470: move Windows MFD setup below the device-type switch Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 5/9] platform/x86: int3472: tps68470: add static clock consumer support Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 6/9] platform/x86: int3472: tps68470: use a common always-on VIO regulator init_data Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 7/9] platform/x86: int3472: tps68470: add board data for Dell Latitude 5285 Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 8/9] media: ipu-bridge: add sensor configuration for OV8858 (INT3477) Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 9/9] media: ov8858: add ACPI device ID INT3477 Thierry Chatard
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=ar4GYJvy_w-ZMJb4@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=dan.scally@ideasonboard.com \
--cc=djrscally@gmail.com \
--cc=dmanresa@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=johannes.goede@oss.qualcomm.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicholas@rothemail.net \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tchatard@gmail.com \
--cc=v.vitovt@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
all inboxes | Powered by JetHome®