From: Chris Taraszka <chris@miget.com>
To: "Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, Mingyou Chen <qby140326@gmail.com>,
Ilya Gladyshev <ilya.gladyshev@linux.dev>,
Armin Wolf <W_Armin@gmx.de>, KentoNion <kento@kekto.ru>,
Matias Civadda <matias.civadda2342001@gmail.com>,
Yun Wang <7z0423arsenova@proton.me>,
Oleg Rybalov <rybalov.oleg.dev@gmail.com>,
Chris Taraszka <chris@miget.com>
Subject: [PATCH v5 0/4] platform/x86: bitland-mifs-wmi: Xiaomi Book Pro 14 support
Date: Wed, 11 Nov 2026 18:04:02 +0100 [thread overview]
Message-ID: <20261111170406.1634428-1-chris@miget.com> (raw)
Four patches on top of Mingyou Chen's v16 "Merge redmi-wmi into
bitland-mifs-wmi" [1] for the Xiaomi Book Pro 14 (TM2424).
The firmware passes SystemPerMode to Intel DTT, and the DTT tables in
its data vault name each mode and set its PL1 per power source.
Low-power, balanced and performance map to 0x02, 0x09 and 0x04. On
battery the firmware's performance mode is 0x03, so patch 2 lets a
profile use a separate value on battery, re-applied when the power
source changes, and patch 3 adds the quirk. Patch 1 keeps a failed
profile read from aborting system suspend, and patch 4 makes Fn+K
cycle the platform profile.
Changes since v4 [2]:
- Rebase onto v16
- Fn+K: cycle on 0x28 for every model, drop the quirk flag (Mingyou)
- Add Mingyou's Reviewed-by to the quirk patch
Changes since v3 [3]:
- Move the quirk after the battery support, so 0x03 is its battery
entry from the start (Mingyou)
- Move the suspend fix to the front, as it stands on its own
- Fn+K still only handles 0x28. Event 0x16 reports a mode change on
TM2135 [4] and TM2424 alike, so it stays a notification
Changes since v2 [5]:
- New mode map from the firmware's DTT tables (Kento)
- New battery support patch
- Fold in the Fn+K patch
[1] https://lore.kernel.org/all/20261111141226.9482-1-qby140326@gmail.com/
[2] https://lore.kernel.org/all/20261106114300.936782-1-chris@miget.com/
[3] https://lore.kernel.org/all/20261101161814.1325847-1-chris@miget.com/
[4] https://lore.kernel.org/all/BelDdF5woNEBX6dZ3_zJDEbVkifs1pdxEjtQ1yC-aKyZahijFJCllxm0l_SqZ5Hsj61D8wfJNa7uDSuNKmyyxo2S0tZp9QS5yaafeZUxvxE=@proton.me/
[5] https://lore.kernel.org/all/20261025195456.43414-1-chris@miget.com/
Chris Taraszka (4):
platform/x86: bitland-mifs-wmi: Don't fail suspend or resume on
profile errors
platform/x86: bitland-mifs-wmi: Support a separate profile value on
battery
platform/x86: bitland-mifs-wmi: Add Xiaomi Book Pro 14 quirk
platform/x86: bitland-mifs-wmi: Cycle the platform profile on Fn+K
drivers/platform/x86/bitland-mifs-wmi.c | 175 +++++++++++++++++++++---
1 file changed, 155 insertions(+), 20 deletions(-)
base-commit: 5680519168f65666d2c03cc6ed8fe2b7052aee12
prerequisite-patch-id: 99b10cd2b70d630ab65d8a8bb02c1d4bf89b1a63
prerequisite-patch-id: 27db041f827872b8be142c310a14c79962154bd5
prerequisite-patch-id: 74fc3298fa3dceb2224dfc3d2ae4cc6d4be61c01
prerequisite-patch-id: 290a15f4692b36391eade807db324a974a4c1f9e
prerequisite-patch-id: 48f575fda0c7b1d4c66179af98a7f8825666ac87
prerequisite-patch-id: 2fe8c043993034f1a2cde98b1b2e299987d5ac7f
--
2.56.0
next reply other threads:[~2026-11-11 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 17:04 Chris Taraszka [this message]
2026-11-11 17:04 ` [PATCH v5 1/4] platform/x86: bitland-mifs-wmi: Don't fail suspend or resume on profile errors Chris Taraszka
2026-11-11 17:04 ` [PATCH v5 2/4] platform/x86: bitland-mifs-wmi: Support a separate profile value on battery Chris Taraszka
2026-11-11 17:04 ` [PATCH v5 3/4] platform/x86: bitland-mifs-wmi: Add Xiaomi Book Pro 14 quirk Chris Taraszka
2026-11-11 17:04 ` [PATCH v5 4/4] platform/x86: bitland-mifs-wmi: Cycle the platform profile on Fn+K Chris Taraszka
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=20261111170406.1634428-1-chris@miget.com \
--to=chris@miget.com \
--cc=7z0423arsenova@proton.me \
--cc=W_Armin@gmx.de \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=ilya.gladyshev@linux.dev \
--cc=kento@kekto.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=matias.civadda2342001@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=qby140326@gmail.com \
--cc=rybalov.oleg.dev@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®