mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Donjuanplatinum <donplat@barrensea.org>
To: Armin Wolf <W_Armin@gmx.de>
Cc: "Hans de Goede" <hansg@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, donplat@barrensea.org
Subject: Re: [PATCH v3] uniwill: Add support for MECHREVO WUJIE Series 15 X Pro
Date: Mon, 12 Oct 2026 22:45:54 +0800	[thread overview]
Message-ID: <8733ub7za5.fsf_-_@DESKTOP-4UP1K6L.lan> (raw)
In-Reply-To: <8f67b6b6-ce55-46cc-a0ac-e54f4bdafb3e@gmx.de> (Armin Wolf's message of "Mon, 12 Oct 2026 01:10:00 +0200")

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]

Armin Wolf <W_Armin@gmx.de> writes:

>
> Hi,
>
> please remove this pointless block of text.

OK, I've remove it.

>
> Can you check if UNIWILL_FEATURE_BATTERY_CHARGE_MODES also works on your device?
> Please note that the embedded controller will still report to charge the battery
> to 100%, so this is not a reliable indicator. Do you know if the Windows OEM app
> provides such a setting on this device?
>
> Thanks,
> Armin Wolf
>

I also checked the battery charge modes in the Windows OEM application. The OEM application provides this setting.

Additionally, I used the interfaces exposed by the OEM's
ACPIDriverDll.dll to test the three charge modes and confirmed that
their behavior matches the current implementation in the Uniwill driver.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-uniwill-Add-support-for-MECHREVO-WUJIE-Series-15-X-P.patch --]
[-- Type: text/x-patch, Size: 2028 bytes --]

From 518d89d58e3ea84af4bced696150ca1e02a4575c Mon Sep 17 00:00:00 2001
From: Donjuanplatinum <donplat@barrensea.org>
Date: Tue, 29 Sep 2026 01:29:09 +0800
Subject: [PATCH v3] platform/x86: uniwill-laptop: Add support for
MECHREVO WUJIE Series 15 X Pro

Add support for the MECHREVO WUJIE Series 15 X Pro (WUJIE
Series-X5SP4NAG).

Signed-off-by: Yifei Yao <donplat@barrensea.org>
---
 drivers/platform/x86/uniwill/uniwill-acpi.c | 22 +++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/drivers/platform/x86/uniwill/uniwill-acpi.c b/drivers/platform/x86/uniwill/uniwill-acpi.c
index 7a2eeaec4c96..bf46f03fb5f5 100644
--- a/drivers/platform/x86/uniwill/uniwill-acpi.c
+++ b/drivers/platform/x86/uniwill/uniwill-acpi.c
@@ -2712,6 +2712,20 @@ static struct uniwill_device_descriptor lapkc71f_descriptor __initdata = {
 	.lightbar_max_brightness = 200,
 };
 
+static struct uniwill_device_descriptor series_x5sp4nag_descriptor __initdata = {
+	.features = UNIWILL_FEATURE_FN_LOCK |
+		    UNIWILL_FEATURE_SUPER_KEY |
+		    UNIWILL_FEATURE_CPU_TEMP |
+		    UNIWILL_FEATURE_PRIMARY_FAN |
+		    UNIWILL_FEATURE_SECONDARY_FAN |
+	            UNIWILL_FEATURE_BATTERY_CHARGE_MODES |
+		    UNIWILL_FEATURE_KEYBOARD_BACKLIGHT |
+		    UNIWILL_FEATURE_AC_AUTO_BOOT |
+		    UNIWILL_FEATURE_USB_POWERSHARE,
+	.kbd_led_single_color = false,
+	.kbd_led_max_brightness = 4,
+};
+
 /*
  * The featuresets below reflect somewhat chronological changes:
  * 1 -> 2: UNIWILL_FEATURE_NVIDIA_CTGP_CONTROL is added to the EC firmware.
@@ -2996,6 +3010,14 @@ static const struct dmi_system_id uniwill_dmi_table[] __initconst = {
 		},
 		.driver_data = &tux_featureset_4_descriptor,
 	},
+	{
+		.ident = "MECHREVO WUJIE Series 15 X Pro",
+		.matches = {
+			DMI_MATCH(DMI_SYS_VENDOR, "MECHREVO"),
+			DMI_EXACT_MATCH(DMI_BOARD_NAME, "WUJIE Series-X5SP4NAG"),
+		},
+		.driver_data = &series_x5sp4nag_descriptor,
+	},
 	{
 		.ident = "TUXEDO InfinityBook Pro 14/15 Gen9 Intel/Commodore Omnia-Book 15 Gen9",
 		.matches = {
-- 
2.55.0


      reply	other threads:[~2026-10-12 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-11  8:14 [PATCH v2] " Donjuanplatinum
2026-10-11 23:10 ` Armin Wolf
2026-10-12 14:45   ` Donjuanplatinum [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=8733ub7za5.fsf_-_@DESKTOP-4UP1K6L.lan \
    --to=donplat@barrensea.org \
    --cc=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 \
    /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®