mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Thierry Chatard <tchatard@gmail.com>,
	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, jacopo.mondi@ideasonboard.com,
	nicholas@rothemail.net, v.vitovt@gmail.com, dmanresa@gmail.com
Subject: Re: [PATCH v11 1/9] mfd: intel-lpss: add resource conflict quirk for Dell Latitude 5285
Date: Thu, 1 Oct 2026 21:34:21 +0300	[thread overview]
Message-ID: <ar6nrcQfDYAg2L-M@ashevche-desk.local> (raw)
In-Reply-To: <ar4KtbRTyJR0Bo-b@kekkonen.localdomain>

On Thu, Oct 01, 2026 at 10:24:37AM +0300, Sakari Ailus wrote:
> On Thu, Oct 01, 2026 at 10:05:05AM +0300, Andy Shevchenko wrote:
> > On Wed, Sep 30, 2026 at 02:43:13PM -0700, Thierry Chatard wrote:
> > > The Dell Latitude 5285 2-in-1 has a BIOS bug where the ACPI GEXP device
> > > and the I2C4 controller (INT3446) both claim the same MMIO region via the
> > > shared SB04 variable. This causes intel_lpss_acpi to fail binding to I2C4
> > > with -EBUSY, preventing the front camera (OV5670) sensor from being
> > > registered.
> > > 
> > > Match the affected machine by DMI and the affected device by ACPI ID,
> > > carrying QUIRK_IGNORE_RESOURCE_CONFLICTS in the ACPI match data and
> > > applying it to the per-device info in probe. This follows the quirk
> > > organisation used by the PCI counterpart.
> > 
> > > Assisted-by: Claude Code:claude-opus-4-8
> > 
> > Assisted-by: LLM
> 
> While coding-assistants.rst does indeed suggest to just use "LLM", I think
> more specific information is worth having, too. Specifying this seems
> commonplace elsewhere. I have to admit I haven't followed the related
> discussions.

While 80 characters is recommended, you are strict about that rule,
I believe the same about Assisted-by. It *is* documented.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-10-01 18:34 UTC|newest]

Thread overview: 16+ 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-10-01 18:34       ` Andy Shevchenko [this message]
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
2026-10-01 18:16     ` D. Manresa
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=ar6nrcQfDYAg2L-M@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=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®