From: Antheas Kapenekakis <lkml@antheas.dev>
To: platform-driver-x86@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"Derek John Clark" <derekjohn.clark@gmail.com>,
"Joaquín Ignacio Aramendía" <samsagax@gmail.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
Eileen <eileen@one-netbook.com>,
"Antheas Kapenekakis" <lkml@antheas.dev>
Subject: [PATCH v1 2/2] platform/x86: oxpec: Add OneXPlayer 3 quirk
Date: Sun, 20 Sep 2026 21:04:38 +0200 [thread overview]
Message-ID: <20260920190438.3444923-2-lkml@antheas.dev> (raw)
In-Reply-To: <20260920190438.3444923-1-lkml@antheas.dev>
The OneXPlayer 3 is a new Intel device by OneXPlayer. It uses the same
registers as the G1 Intel edition. So, add a quirk for it. Battery
bypass, capacity limits, fan curves, fan tachometer, and turbo button
override were confirmed to work.
Signed-off-by: Antheas Kapenekakis <lkml@antheas.dev>
---
drivers/platform/x86/oxpec.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/platform/x86/oxpec.c b/drivers/platform/x86/oxpec.c
index 38c272995437..c4c4babe8e30 100644
--- a/drivers/platform/x86/oxpec.c
+++ b/drivers/platform/x86/oxpec.c
@@ -223,6 +223,13 @@ static const struct dmi_system_id dmi_table[] = {
},
.driver_data = (void *)oxp_g1_i,
},
+ {
+ .matches = {
+ DMI_MATCH(DMI_BOARD_VENDOR, "ONE-NETBOOK"),
+ DMI_EXACT_MATCH(DMI_BOARD_NAME, "ONEXPLAYER 3"),
+ },
+ .driver_data = (void *)oxp_g1_i,
+ },
{
.matches = {
DMI_MATCH(DMI_BOARD_VENDOR, "ONE-NETBOOK"),
--
2.55.0
next prev parent reply other threads:[~2026-09-20 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 19:04 [PATCH v1 1/2] platform/x86: oxpec: Fix Apex charge limit control Antheas Kapenekakis
2026-09-20 19:04 ` Antheas Kapenekakis [this message]
2026-09-20 22:29 ` [PATCH v1 2/2] platform/x86: oxpec: Add OneXPlayer 3 quirk Derek J. Clark
2026-09-20 22:28 ` [PATCH v1 1/2] platform/x86: oxpec: Fix Apex charge limit control Derek J. Clark
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=20260920190438.3444923-2-lkml@antheas.dev \
--to=lkml@antheas.dev \
--cc=derekjohn.clark@gmail.com \
--cc=eileen@one-netbook.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=samsagax@gmail.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®