mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiajun Leng <adolphpi@outlook.com>
To: platform-driver-x86@vger.kernel.org
Cc: "Antheas Kapenekakis" <lkml@antheas.dev>,
	"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>,
	linux-kernel@vger.kernel.org,
	"Jiajun Leng" <adolphpi@outlook.com>
Subject: [PATCH v2] platform/x86: oxpec: add OneXPlayer X2 Mini (G3E) DMI entry
Date: Sun,  1 Nov 2026 10:18:26 +0800	[thread overview]
Message-ID: <TY7PR01MB1374600CF756D90DF8CFC37BDDB6B2@TY7PR01MB13746.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TY7PR01MB1374656B7810521751CB248D4DB6B2@TY7PR01MB13746.jpnprd01.prod.outlook.com>

The OneXPlayer X2 Mini (G3E) is the Intel variant and reports DMI board
name "ONEXPLAYER X2Mini". Map it to oxp_g1_i, the profile used by the
ONEXPLAYER 3, which has the same Intel EC layout. Fan reading, manual PWM
and charging control work.

Signed-off-by: Jiajun Leng <adolphpi@outlook.com>
---
Changes in v2:
- Remove the X2Mini PRO comparison and the downstream kernel version.
- Merge the quirk mapping and test results into the first paragraph.
- Place the entry above ONEXPLAYER X2Mini PRO to keep alphabetical order.
- Move the AI assistance note out of the commit message.

AI assistance: Claude (Anthropic) was used to draft this changelog and the
diff; the submitter reviewed and tested the change.

 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 c4c4babe8e30..f4b5a35a4d69 100644
--- a/drivers/platform/x86/oxpec.c
+++ b/drivers/platform/x86/oxpec.c
@@ -300,6 +300,13 @@ static const struct dmi_system_id dmi_table[] = {
 		},
 		.driver_data = (void *)oxp_x1,
 	},
+	{
+		.matches = {
+			DMI_MATCH(DMI_BOARD_VENDOR, "ONE-NETBOOK"),
+			DMI_EXACT_MATCH(DMI_BOARD_NAME, "ONEXPLAYER X2Mini"),
+		},
+		.driver_data = (void *)oxp_g1_i,
+	},
 	{
 		.matches = {
 			DMI_MATCH(DMI_BOARD_VENDOR, "ONE-NETBOOK"),
-- 
2.53.0


  parent reply	other threads:[~2026-11-01  2:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-01  1:26 [PATCH] " Jiajun Leng
2026-11-01  1:35 ` Antheas Kapenekakis
2026-11-01  1:37   ` Antheas Kapenekakis
2026-11-01  2:18 ` Jiajun Leng [this message]
2026-11-01  2:24   ` [PATCH v2] " Antheas Kapenekakis

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=TY7PR01MB1374600CF756D90DF8CFC37BDDB6B2@TY7PR01MB13746.jpnprd01.prod.outlook.com \
    --to=adolphpi@outlook.com \
    --cc=derekjohn.clark@gmail.com \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@antheas.dev \
    --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®