From: johannes.goede@oss.qualcomm.com
To: "Ali Ahmet Memiş" <aliamemis@disroot.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Len Brown <lenb@kernel.org>, Armin Wolf <W_Armin@gmx.de>,
Charis Stratakis <c.stratakis@proton.me>,
linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org,
regressions@lists.linux.dev,
Mark Pearson <mpearson-lenovo@squebb.ca>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ACPI: battery: Re-read battery information in the complete callback
Date: Wed, 14 Oct 2026 12:01:55 +0200 [thread overview]
Message-ID: <ab5c5ae1-1bfd-4fe4-adef-fb64b5b3dfbb@oss.qualcomm.com> (raw)
In-Reply-To: <20261013210609.8117-1-aliamemis@disroot.org>
Hi,
On 13-Oct-26 23:05, Ali Ahmet Memiş wrote:
> On Tue, Oct 13, 2026 at 07:20:55PM +0200, Rafael J. Wysocki (Intel) wrote:
>> Also, we don't actually know how many "bad" cases there are and so far
>> we have identified a few.
>
> I wrote a script that extracts the ACPI tables from all 208 BIOS
> packages in Lenovo's ThinkPad catalog (370 models) and flags methods
> that switch the EC page selector (HIID) without BATM while other methods
> use it under BATM, and checked the flagged ones by hand. Two BIOSes do
> it both with \GTST from _TMP: P1 Gen2 / X1 Extreme Gen2 and P53 / P73.
> Apart from those, NVPS on T450 / T450s does it from the NVIDIA GPS
> _DSM, which only the out-of-tree NVIDIA driver evaluates. This doesn't
> cover races like the UCSI one in bko221065.
>
> FWIW, the exclusive variant is done. With it the emulated \GTST breaks
> neither _BIX after resume nor _BST at run time (0 of 5 and 0 of 1074),
> and with only the _TMP side converted both still break (5 of 5 and 421
> of 424).
As I just agreed in my reply to Rafael, it looks like we want to go
with the exclusive variant for now.
Can you post a patch series for the code you've for this now ?
Note I guess you're using LLM to help you with this, that is fine,
but can you please manually shorten the commit messages of the patches
a bit if they were written by LLM? OR instruct it to write "short and
concise" commit messages?
LLM's tend to write overly verbose commit messages. Note a good commit
message is important, but lets try to keep them compact.
And the same for the cover-letter.
Regards,
Hans
next prev parent reply other threads:[~2026-10-14 10:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <37N_jFulf7n-Z55NfKfE71C_wVPxYvZ0xD_iRUg2fXu7TypDiF5PStQ6siSfVBih6fThg5WoPes8U5ZQpfVm_teMFcUGXFxz2DdMbfSWuws=@proton.me>
2026-10-12 22:46 ` Ali Ahmet Memiş
2026-10-12 22:58 ` Ali Ahmet Memiş
2026-10-13 1:40 ` Charis Stratakis
2026-10-13 5:34 ` Ali Ahmet Memiş
2026-10-13 9:33 ` johannes.goede
2026-10-13 11:58 ` Rafael J. Wysocki (Intel)
2026-10-13 12:30 ` Ali Ahmet Memiş
2026-10-13 13:12 ` Rafael J. Wysocki (Intel)
2026-10-13 13:36 ` johannes.goede
2026-10-13 17:20 ` Rafael J. Wysocki (Intel)
2026-10-13 21:05 ` Ali Ahmet Memiş
2026-10-14 10:01 ` johannes.goede [this message]
2026-10-14 13:32 ` Ali Ahmet Memiş
2026-10-14 14:00 ` johannes.goede
2026-10-14 9:58 ` johannes.goede
2026-10-14 15:06 ` Rafael J. Wysocki (Intel)
2026-10-14 19:34 ` johannes.goede
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=ab5c5ae1-1bfd-4fe4-adef-fb64b5b3dfbb@oss.qualcomm.com \
--to=johannes.goede@oss.qualcomm.com \
--cc=W_Armin@gmx.de \
--cc=aliamemis@disroot.org \
--cc=c.stratakis@proton.me \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@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
all inboxes | Powered by JetHome®