From: "Mark Pearson" <mpearson-lenovo@squebb.ca>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Hans de Goede" <hansg@kernel.org>,
"Huang Wei" <huangwei@kylinos.cn>
Cc: "platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
linux-kernel@vger.kernel.org, thisisamirv@gmail.com
Subject: Re: [PATCH v2] platform/x86: thinkpad_acpi: Add X9-14 Gen 1 to non-standard thermal/fan quirk tables
Date: Fri, 18 Sep 2026 18:00:04 -0400 [thread overview]
Message-ID: <3d4bb6df-a3db-41a7-a568-b268efaa1c93@app.fastmail.com> (raw)
In-Reply-To: <178975590278.29716.17309474720733695095.b4-ty@b4>
On Fri, Sep 18, 2026, at 2:25 PM, Ilpo Järvinen wrote:
> On Sat, 19 Sep 2026 00:15:39 +0800, Huang Wei wrote:
>
>> The Lenovo ThinkPad X9-14 Gen 1 uses a non-standard Embedded Controller
>> firmware (ECFW) whose thermal and fan registers are not located at the
>> classic addresses. On this model the thermal registers sit at 0xA8-0xAF /
>> 0xB8-0xBF and the fan registers use the non-standard offsets, instead of
>> the legacy 0x78-0x7F / 0xC0-0xC7 (thermal) and 0x2f / 0x84 (fan).
>>
>> Because the model is not covered by the existing quirk tables, the driver
>> probes the legacy thermal addresses during init, reads back 0x00 from
>> every register, concludes the EC is "misbehaving" and disables all
>> thermal sensor access:
>>
>> [...]
>
> Thank you for your contribution, it has been applied to my local
> review-ilpo-next branch. Note it will show up in the public
> platform-drivers-x86/review-ilpo-next branch only once I've pushed my
> local branch there, which might take a while.
>
> FYI [if applicable to your patch], as per Linus' policy change, also
> fixes are mostly routed through for-next unless the fix is for a
> commit introduced in the most recent cycle or is clearly a regression
> fix.
>
> The list of commits applied:
> [1/1] platform/x86: thinkpad_acpi: Add X9-14 Gen 1 to non-standard
> thermal/fan quirk tables
> commit: bb0f3a5d6b9844b70ad696b9470762028f6d86ec
>
> --
> i.
Just a note that I have a ticket in to the FW team to confirm this (LO-4662). This platform was Linux certified so I was a bit puzzled at it being different, but I think the proposed patch is correct. Just making sure (and to figure out how we missed it...)
I don't mean to hold up the review - just noting that this is being verified and confirmed on the Lenovo side for completeness
Mark
prev parent reply other threads:[~2026-09-18 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 7:30 [PATCH] " Huang Wei
2026-09-18 15:15 ` Ilpo Järvinen
2026-09-18 16:15 ` [PATCH v2] " Huang Wei
2026-09-18 18:25 ` Ilpo Järvinen
2026-09-18 22:00 ` Mark Pearson [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=3d4bb6df-a3db-41a7-a568-b268efaa1c93@app.fastmail.com \
--to=mpearson-lenovo@squebb.ca \
--cc=hansg@kernel.org \
--cc=huangwei@kylinos.cn \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=thisisamirv@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®