From: "D. Manresa" <dmanresa@gmail.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: "Daniel Scally" <dan.scally@ideasonboard.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Thierry Chatard" <tchatard@gmail.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: int3472: Add TPS68470 board data for Dell Latitude 7275
Date: Tue, 8 Sep 2026 18:13:22 +0200 [thread overview]
Message-ID: <20260908161322.334690-1-dmanresa@gmail.com> (raw)
In-Reply-To: <apptlIQexoFg42DF@kekkonen.localdomain>
Hi Sakari,
On Fri, 4 Sep 2026, Sakari Ailus wrote:
> What's below would better fit after the '---' line.
Will do in v2.
> Is this the same issue than for Latutude 5285 here
> <URL:https://lore.kernel.org/linux-media/20260831160754.9857-1-tchatard@gmail.com/>?
Yes, exactly the same. On the 7275 the GEXP device declares
OperationRegion (BAR0, SystemMemory, SB04, 0x0208)
and the I2C4 controller (INT3446) builds its _CRS from the same SB04
variable, so intel_lpss_acpi fails with -EBUSY unless
acpi_enforce_resources=lax is given. Thierry's patch 1/8 fixes it here
too once a "Latitude 7275" entry is added to intel_lpss_quirk_dmi[]. I'll
send that as a small patch on top of his series; Thierry, if you would
rather fold it into v11, I'm happy to provide a Tested-by.
The other 5285 quirk, the static clock consumer list for the broken
INT3479 _DEP, is not needed on the 7275: tps68470-clk already lists
i2c-INT3479:00 as a consumer in clk_summary.
Thanks,
D.
next prev parent reply other threads:[~2026-09-08 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 6:20 [PATCH] platform/x86: int3472: Add TPS68470 board data for Dell Latitude 7275 D. Manresa
2026-09-04 7:04 ` Sakari Ailus
2026-09-08 16:13 ` D. Manresa [this message]
2026-09-08 16:14 ` [PATCH v2] " D. Manresa
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=20260908161322.334690-1-dmanresa@gmail.com \
--to=dmanresa@gmail.com \
--cc=dan.scally@ideasonboard.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tchatard@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