From: "dydydd" <admin@qb.edu.kg>
To: "Armin Wolf" <W_Armin@gmx.de>
Cc: "Hans de Goede" <hansg@kernel.org>,
"Ilpo Jarvinen" <ilpo.jarvinen@linux.intel.com>,
<platform-driver-x86@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 1/2] platform/x86: uniwill: Add MECHREVO Jiaolong 16K (GM6BG0Q)
Date: Fri, 23 Oct 2026 11:48:21 +0800 [thread overview]
Message-ID: <20261023034822.141263-1-admin@qb.edu.kg> (raw)
Add a DMI entry for the MECHREVO Jiaolong 16K, which is built by Uniwill
on the GM6BG0Q board (BIOS project ID "IDQ", EC version 1.24).
The feature set was determined by testing every sysfs attribute exposed
by the driver on the actual machine:
- fn_lock, super_key_enable and touchpad_toggle_enable are writable and
take effect
- the battery exposes charge_types (Trickle/Standard/Long_Life) instead
of charge_control_end_threshold, so BATTERY_CHARGE_MODES is used
- cpu_temp, gpu_temp, fan1_input and fan2_input report plausible values
- the keyboard backlight is RGB with four brightness levels
- ac_auto_boot and usb_powershare_high are writable
- usb_c_power_priority switches between charging and performance
- ctgp_offset is writable
This machine has no lightbar, so UNIWILL_FEATURE_LIGHTBAR is left out.
Tested on: MECHREVO Jiaolong16K Series GM6BG0Q, BIOS N.1.19MRO15,
EC 1.24, AMD Rembrandt, NVIDIA RTX 4060 Mobile.
Signed-off-by: dydydd <admin@qb.edu.kg>
---
drivers/platform/x86/uniwill/uniwill-acpi.c | 26 +++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/drivers/platform/x86/uniwill/uniwill-acpi.c b/drivers/platform/x86/uniwill/uniwill-acpi.c
index 7a2eeaec..94ed83ed 100644
--- a/drivers/platform/x86/uniwill/uniwill-acpi.c
+++ b/drivers/platform/x86/uniwill/uniwill-acpi.c
@@ -2677,6 +2677,24 @@ static struct uniwill_device_descriptor machenike_l16p_descriptor __initdata = {
.kbd_led_max_brightness = 4,
};
+static struct uniwill_device_descriptor mechrevo_gm6bg0q_descriptor __initdata = {
+ .features = UNIWILL_FEATURE_FN_LOCK |
+ UNIWILL_FEATURE_SUPER_KEY |
+ UNIWILL_FEATURE_TOUCHPAD_TOGGLE |
+ UNIWILL_FEATURE_BATTERY_CHARGE_MODES |
+ UNIWILL_FEATURE_CPU_TEMP |
+ UNIWILL_FEATURE_GPU_TEMP |
+ UNIWILL_FEATURE_PRIMARY_FAN |
+ UNIWILL_FEATURE_SECONDARY_FAN |
+ UNIWILL_FEATURE_NVIDIA_CTGP_CONTROL |
+ UNIWILL_FEATURE_USB_C_POWER_PRIORITY |
+ UNIWILL_FEATURE_KEYBOARD_BACKLIGHT |
+ UNIWILL_FEATURE_AC_AUTO_BOOT |
+ UNIWILL_FEATURE_USB_POWERSHARE,
+ .kbd_led_single_color = false,
+ .kbd_led_max_brightness = 4,
+};
+
static struct uniwill_device_descriptor lapqc71a_lapqc71b_descriptor __initdata = {
.features = UNIWILL_FEATURE_SUPER_KEY |
UNIWILL_FEATURE_LIGHTBAR |
@@ -2877,6 +2895,14 @@ static const struct dmi_system_id uniwill_dmi_table[] __initconst = {
},
.driver_data = &machenike_l16p_descriptor,
},
+ {
+ .ident = "MECHREVO Jiaolong 16K GM6BG0Q",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "MECHREVO"),
+ DMI_EXACT_MATCH(DMI_BOARD_NAME, "GM6BG0Q"),
+ },
+ .driver_data = &mechrevo_gm6bg0q_descriptor,
+ },
{
.ident = "XMG FUSION 15 (L19)",
.matches = {
--
2.56.0
next reply other threads:[~2026-10-23 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 3:48 dydydd [this message]
2026-10-23 3:48 ` [PATCH 2/2] platform/x86: uniwill: Add platform profile support dydydd
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=20261023034822.141263-1-admin@qb.edu.kg \
--to=admin@qb.edu.kg \
--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®