From: Armin Wolf <W_Armin@gmx.de>
To: hansg@kernel.org, ilpo.jarvinen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, bifangknt@qq.com,
nicokessler@icloud.com, sre@kernel.org, linux-pm@vger.kernel.org,
wse@tuxedocomputers.com
Subject: Re: [PATCH v2 0/9] platform/x86: uniwill-laptop: Complete battery support
Date: Fri, 20 Nov 2026 21:53:52 +0100 [thread overview]
Message-ID: <fad724e8-72f2-4ce2-9a40-26aeb11c5a08@gmx.de> (raw)
In-Reply-To: <20261110165318.631010-1-W_Armin@gmx.de>
Am 10.11.26 um 17:50 schrieb Armin Wolf:
> According to the work item for upstreaming the out-of-tree
> tuxedo-drivers package, the mainline uniwill-laptop driver still does
> not allow userspace to read the cycle count and raw capacity of the
> battery, preventing Tuxedo Computers from switching over to the
> mainline driver (among other things).
>
> This patch series aims to add the missing battery-related bits. The
> first two patches extend the power supply subsystem, while the third
> patch uses the new API to expose the battery cycle count on devices
> where this not already being done by the ACPI firmware itself. The
> fourth patch also exposes the raw battery capacity using a custom
> sysfs attribute below the battery power supply device. The fifth
> patch only does some generic sysfs-related cleanup, while the last
> three patches add support for new devices based on user reports.
>
> All patches have been tested on a TUXEDO InfinityBook Pro 14 Gen10 AMD
> and appear to work without issues.
Hi,
what is the status of this?
Thanks,
Armin Wolf
> Link: https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers/-/work_items/253
>
> Changes since v2:
> - fix error handling inside patch 5
>
> Armin Wolf (9):
> power: supply: core: Add power_supply_has_property_direct()
> power: supply: Enable struct power_supply_ext to be construct
> dynamically
> platform/x86: uniwill-laptop: Report battery cycle count
> platform/x86: uniwill-laptop: Expose battery health and cycle count on
> all devices
> platform/x86: uniwill-laptop: Expose raw battery capacity to userspace
> platform/x86: uniwill-laptop: Mark sysfs attributes as const
> platform/x86: uniwill-laptop: Add support for MECHREVO Yilong15Pro
> platform/x86: uniwill-laptop: Add MECHREVO JIAOLONG Series-X6xR55xK
> platform/x86: uniwill-laptop: Add support for XMG EVO 14 (E25)
>
> .../ABI/testing/sysfs-driver-uniwill-laptop | 11 +
> drivers/platform/x86/uniwill/uniwill-acpi.c | 269 ++++++++++++------
> drivers/power/supply/power_supply_core.c | 26 +-
> include/linux/power_supply.h | 3 +-
> 4 files changed, 220 insertions(+), 89 deletions(-)
>
prev parent reply other threads:[~2026-11-20 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 16:50 Armin Wolf
2026-11-10 16:50 ` [PATCH v2 1/9] power: supply: core: Add power_supply_has_property_direct() Armin Wolf
2026-11-10 16:50 ` [PATCH v2 2/9] power: supply: Enable struct power_supply_ext to be construct dynamically Armin Wolf
2026-11-10 16:50 ` [PATCH v2 3/9] platform/x86: uniwill-laptop: Report battery cycle count Armin Wolf
2026-11-10 16:50 ` [PATCH v2 4/9] platform/x86: uniwill-laptop: Expose battery health and cycle count on all devices Armin Wolf
2026-11-10 16:50 ` [PATCH v2 5/9] platform/x86: uniwill-laptop: Expose raw battery capacity to userspace Armin Wolf
2026-11-10 16:50 ` [PATCH v2 6/9] platform/x86: uniwill-laptop: Mark sysfs attributes as const Armin Wolf
2026-11-10 16:50 ` [PATCH v2 7/9] platform/x86: uniwill-laptop: Add support for MECHREVO Yilong15Pro Armin Wolf
2026-11-10 16:50 ` [PATCH v2 8/9] platform/x86: uniwill-laptop: Add MECHREVO JIAOLONG Series-X6xR55xK Armin Wolf
2026-11-10 16:50 ` [PATCH v2 9/9] platform/x86: uniwill-laptop: Add support for XMG EVO 14 (E25) Armin Wolf
2026-11-20 20:53 ` Armin Wolf [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=fad724e8-72f2-4ce2-9a40-26aeb11c5a08@gmx.de \
--to=w_armin@gmx.de \
--cc=bifangknt@qq.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nicokessler@icloud.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sre@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®