From: Armin Wolf <W_Armin@gmx.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>, hansg@kernel.org
Cc: wse@tuxedocomputers.com, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/8] platform/x86: uniwill-laptop: Charging-related improvements
Date: Sat, 23 May 2026 00:01:31 +0200 [thread overview]
Message-ID: <ef98a5f8-d62c-465c-9f15-5958cd92c49e@gmx.de> (raw)
In-Reply-To: <177920193411.22546.9855747319755001624.b4-ty@linux.intel.com>
Am 19.05.26 um 16:45 schrieb Ilpo Järvinen:
> On Wed, 13 May 2026 01:21:37 +0200, Armin Wolf wrote:
>
>> This patch series contains various charging-related improvements
>> for the uniwill-laptop driver. The first two patches fix some minor
>> issues inside the charging threshold code, while the third patch
>> fixes an issue inside the module initialization code. The next two
>> patches contain some preparations for the main patch. Said patch
>> introduces support for controlling the charging modes available
>> on many Uniwill-based devices not sold by Intel. The last patch
>> whitelists most Tuxedo devices for using the battery charge modes.
>>
>> [...]
>
> Thank you for your contribution, it has been applied to my local
> review-ilpo-fixes branch. Note it will show up in the public
> platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
> local branch there, which might take a while.
Thank you :)
Is there a special reason why only the first four commits are actually available
on the fixes branch?
Thanks,
Armin Wolf
>
> The list of commits applied:
> [1/8] platform/x86: uniwill-laptop: Properly initialize charging threshold
> commit: c12cc42dadd85dea210d5699d4f21def827382eb
> [2/8] platform/x86: uniwill-laptop: Accept charging threshold of 0
> commit: c16a4823cc60a32b891f7a148bb30c0f51d12cf4
> [3/8] platform/x86: uniwill-laptop: Fix behavior of "force" module param
> commit: fb4b67c44557cb4cbb15900083d4e1af22320339
> [4/8] platform/x86: uniwill-laptop: Do not enable the charging limit even when forced
> commit: 26cbe119f99c86dcb4a0136d2bc73c0c716d80e4
> [5/8] platform/x86: uniwill-laptop: Rework FN lock/super key suspend handling
> (no commit info)
> [6/8] platform/x86: uniwill-laptop: Mark EC_ADDR_OEM_4 as volatile
> (no commit info)
> [7/8] platform/x86: uniwill-laptop: Add support for battery charge modes
> (no commit info)
> [8/8] platform/x86: uniwill-laptop: Enable battery charge modes on supported devices
> (no commit info)
>
> --
> i.
>
>
next prev parent reply other threads:[~2026-05-22 22:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 23:21 Armin Wolf
2026-05-12 23:21 ` [PATCH v3 1/8] platform/x86: uniwill-laptop: Properly initialize charging threshold Armin Wolf
2026-05-12 23:21 ` [PATCH v3 2/8] platform/x86: uniwill-laptop: Accept charging threshold of 0 Armin Wolf
2026-05-12 23:21 ` [PATCH v3 3/8] platform/x86: uniwill-laptop: Fix behavior of "force" module param Armin Wolf
2026-05-12 23:21 ` [PATCH v3 4/8] platform/x86: uniwill-laptop: Do not enable the charging limit even when forced Armin Wolf
2026-05-12 23:21 ` [PATCH v3 5/8] platform/x86: uniwill-laptop: Rework FN lock/super key suspend handling Armin Wolf
2026-05-12 23:21 ` [PATCH v3 6/8] platform/x86: uniwill-laptop: Mark EC_ADDR_OEM_4 as volatile Armin Wolf
2026-05-12 23:21 ` [PATCH v3 7/8] platform/x86: uniwill-laptop: Add support for battery charge modes Armin Wolf
2026-05-12 23:21 ` [PATCH v3 8/8] platform/x86: uniwill-laptop: Enable battery charge modes on supported devices Armin Wolf
2026-05-19 14:45 ` [PATCH v3 0/8] platform/x86: uniwill-laptop: Charging-related improvements Ilpo Järvinen
2026-05-22 22:01 ` Armin Wolf [this message]
2026-05-25 9:55 ` Ilpo Järvinen
2026-05-28 12:10 ` Ilpo Järvinen
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=ef98a5f8-d62c-465c-9f15-5958cd92c49e@gmx.de \
--to=w_armin@gmx.de \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=wse@tuxedocomputers.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®