nepharius/onexplayer-superxcontrol
1
0
Fork 0
forked from Public-Mirror/onexplayer-superxcontrol
Code Pull requests Activity

Add Super X upstream mail templates

Browse source
This commit is contained in:
ps1x 2026-03-30 00:48:16 +03:00
parent b4423401b7
commit 7446f562fd
2 changed files with 58 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
contrib/upstream-linux/commit-message-superx.txt Normal file
View file

@ -0,0 +1,27 @@
platform/x86: oxpec: add support for OneXPlayer Super X
OneXPlayer Super X identifies itself via DMI as:
board vendor: ONE-NETBOOK
board name: ONEXPLAYER SUPER X
product name: ONEXPLAYER SUPER X
Current mainline oxpec does not contain a matching DMI entry for this
system, so the in-tree driver is not auto-loaded.
On the tested Super X device, the working EC layout matches the
following handling:
- fan RPM is read from OXP_SENSOR_FAN_REG (0x76)
- pwm1_enable uses OXP_SENSOR_PWM_ENABLE_REG (0x4A)
- pwm1 uses OXP_SENSOR_PWM_REG (0x4B) with direct 0-255 writes
- turbo toggle uses OXP_TURBO_SWITCH_REG (0xF1)
- charge-limit / charge-behaviour uses the same battery extension path
as the X1 family
Add a dedicated oxp_superx board id, a DMI match for OneXPlayer Super X,
and route the fan, PWM, turbo-toggle, and battery-extension paths
through the validated Super X handling.
Tested-on: OneXPlayer Super X
Signed-off-by: ps1x <ps1x@users.noreply.github.com>

31
contrib/upstream-linux/cover-letter-superx.txt Normal file
View file

@ -0,0 +1,31 @@
Subject: [PATCH] platform/x86: oxpec: add support for OneXPlayer Super X
Hi,
this patch adds DMI-based support for OneXPlayer Super X to
drivers/platform/x86/oxpec.c.
Why this is needed:
- the tested Super X system exposes DMI strings as `ONE-NETBOOK` /
`ONEXPLAYER SUPER X`
- current mainline `oxpec` does not match those strings
- as a result, the in-tree driver is not auto-loaded on this machine
What was validated locally on hardware:
- the patched driver matches and loads on OneXPlayer Super X
- the hwmon node appears
- fan RPM becomes readable
- manual PWM control works
- turbo toggle register matches the `OXP_TURBO_SWITCH_REG` path
The tested Super X fan/PWM behaviour does not match the current `oxp_x1`
fan path, so this patch adds a dedicated `oxp_superx` board id instead
of aliasing the system directly to `oxp_x1`.
Battery charge-limit / charge-behaviour on this machine uses the same
0xA3 / 0xA4 EC path that is already used by the X1 family, so the patch
keeps that extension enabled for Super X.
Thanks.