From: Mohamed Jouini <amad3v@gmail.com>
To: "Armin Wolf" <W_Armin@gmx.de>, "Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Werner Sembach <wse@tuxedocomputers.com>,
Christoffer Sandberg <cs@tuxedo.de>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, Mohamed Jouini <amad3v@gmail.com>
Subject: [PATCH v3 0/2] platform/x86: uniwill-laptop: Support the PCSpecialist Recoil 16 AMD
Date: Thu, 8 Oct 2026 14:56:22 +0100 [thread overview]
Message-ID: <20261008135624.3520849-1-amad3v@gmail.com> (raw)
The PCSpecialist Recoil 16 AMD is a rebadged TUXEDO Stellaris 16 Gen7 AMD
(board X6FR57TY), which the driver does not match today because of the
different DMI vendor and board name.
Patch 1 adds it with the existing Stellaris 16 Gen7 AMD feature set.
Patch 2 maps the "Sc" key (WMI event 0xD0) to KEY_ROTATE_DISPLAY.
Tested on the Recoil 16 AMD (BIOS N.1.39PCS10) with the v2 driver built
against 7.2.7: the Sc key, the hwmon fan and temperature readings, and
all three charging profiles. v3 only follows the descriptor rename, so
the device gets the same feature set as in v2. Charging from below 70%,
with the charge counted from current_now:
Profile CV (4S) per cell stops at, of a Standard charge
Standard 17.405 V 4.35 V 100%
Long_Life 17.194 V 4.30 V about 93%
Trickle 16.818 V 4.20 V about 90%
In every profile the EC then reports 100% / Full, as Armin said it
would.
Changes in v3:
- Rebased on for-next: the Stellaris 16 Gen7 AMD feature set is now
gmxixxx_xxxx45xx_xxxx55xx_xxxx57xx_descriptor (Ilpo).
- Patch 2 unchanged. On v1, TUXEDO confirmed they know of no device
using event 0xD0, which settles the question attached to Armin's
Reviewed-by:
https://lore.kernel.org/r/66a47248ecfa1704186274f2c245d3f5@tuxedo.de
Changes in v2:
- Patch 1 uses the existing Stellaris 16 Gen7 AMD feature set (charging
profiles) instead of the percentage charge limit (Armin).
- Dropped the platform profile patch for now (Armin).
- Added Armin's Reviewed-by to the Sc key patch.
v2: https://lore.kernel.org/r/20260927014031.3465252-1-amad3v@gmail.com
v1: https://lore.kernel.org/r/20260925211635.1422516-1-amad3v@gmail.com
Mohamed Jouini (2):
platform/x86: uniwill-laptop: Add PCSpecialist Recoil 16 AMD
platform/x86: uniwill-laptop: Map the screen rotation key
drivers/platform/x86/uniwill/uniwill-acpi.c | 11 +++++++++++
drivers/platform/x86/uniwill/uniwill-wmi.h | 3 +++
2 files changed, 14 insertions(+)
base-commit: 98f039265e580291d5e76a11b2072541fbb1c393
--
2.56.0
next reply other threads:[~2026-10-08 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 13:56 Mohamed Jouini [this message]
2026-10-08 13:56 ` [PATCH v3 1/2] platform/x86: uniwill-laptop: Add " Mohamed Jouini
2026-10-08 13:56 ` [PATCH v3 2/2] platform/x86: uniwill-laptop: Map the screen rotation key Mohamed Jouini
2026-10-08 17:38 ` [PATCH v3 0/2] platform/x86: uniwill-laptop: Support the PCSpecialist Recoil 16 AMD 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=20261008135624.3520849-1-amad3v@gmail.com \
--to=amad3v@gmail.com \
--cc=W_Armin@gmx.de \
--cc=cs@tuxedo.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®