From: Armin Wolf <W_Armin@gmx.de>
To: hansg@kernel.org, ilpo.jarvinen@linux.intel.com
Cc: wse@tuxedocomputers.com, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/8] platform/x86: uniwill-laptop: Charging-related improvements
Date: Wed, 13 May 2026 01:21:37 +0200 [thread overview]
Message-ID: <20260512232145.329260-1-W_Armin@gmx.de> (raw)
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.
All patches have been tested on a Tuxedo InfinityBook Pro 15 Gen10 AMD
and work just fine.
Changes since v2:
- add Reviewed-by tags
- rework first patch to use a common helper function
- add last patch from Werner
Changes since v1:
- add Reviewed-by tags
- fix spelling errors
- split third patch into two separate patches
- restructure code for battery initialization
Armin Wolf (7):
platform/x86: uniwill-laptop: Properly initialize charging threshold
platform/x86: uniwill-laptop: Accept charging threshold of 0
platform/x86: uniwill-laptop: Fix behavior of "force" module param
platform/x86: uniwill-laptop: Do not enable the charging limit even
when forced
platform/x86: uniwill-laptop: Rework FN lock/super key suspend
handling
platform/x86: uniwill-laptop: Mark EC_ADDR_OEM_4 as volatile
platform/x86: uniwill-laptop: Add support for battery charge modes
Werner Sembach (1):
platform/x86: uniwill-laptop: Enable battery charge modes on supported
devices
.../admin-guide/laptops/uniwill-laptop.rst | 25 +-
drivers/platform/x86/uniwill/uniwill-acpi.c | 443 ++++++++++++++----
drivers/platform/x86/uniwill/uniwill-wmi.c | 5 +-
3 files changed, 384 insertions(+), 89 deletions(-)
--
2.39.5
next reply other threads:[~2026-05-12 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 23:21 Armin Wolf [this message]
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
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=20260512232145.329260-1-W_Armin@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