From: Armin Wolf <W_Armin@gmx.de>
To: hansg@kernel.org, ilpo.jarvinen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, i@rsplwe.com,
rahulbheda131313@gmail.com, kento@kekto.ru, qby140326@gmail.com,
martiya.ar@gmail.com, vlku.milos.fun@gmail.com,
mm3885525@gmail.com, wleizc7319@gmail.com
Subject: [PATCH 0/2] Fix for platform profile issues on USB-C-only models
Date: Sat, 5 Sep 2026 00:45:14 +0200 [thread overview]
Message-ID: <20260904224516.8893-1-W_Armin@gmx.de> (raw)
After looking thru the ACPI tables of various people having issues
with the bitland-mifs-wmi driver, i came to the following conclusions:
1. There seem to be multiple flavors of the Mifs interface,
distinguishable by small changes inside their WMI MOF definitions
2. The buffer format used to communicate with the ACPI-WMI firmware
operates differently than previously thought.
This patch series addresses the second point I am aware that there
exist multiple outstanding patch series that partially overlap with
this one. All of those patch series still rely on the incorrect buffer
format currently being used by the driver, so i suggest that this
patch series be used as a new base for future patches.
All patches have been tested by a user on his Redmi Book Pro 16 2024.
Armin Wolf (2):
platform/x86: bitland-mifs-wmi: Detect failed function calls
platform/x86: bitland-mifs-wmi: Treat WMI_FN_SYSTEM_AC_TYPE as
optional
.../wmi/devices/bitland-mifs-wmi.rst | 64 +++++---
drivers/platform/x86/bitland-mifs-wmi.c | 146 +++++++++---------
2 files changed, 117 insertions(+), 93 deletions(-)
--
2.39.5
next reply other threads:[~2026-09-04 22:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 22:45 Armin Wolf [this message]
2026-09-04 22:45 ` [PATCH 1/2] platform/x86: bitland-mifs-wmi: Detect failed function calls Armin Wolf
2026-09-04 22:45 ` [PATCH 2/2] platform/x86: bitland-mifs-wmi: Treat WMI_FN_SYSTEM_AC_TYPE as optional Armin Wolf
2026-09-15 11:32 ` [PATCH 0/2] Fix for platform profile issues on USB-C-only models Ilpo Järvinen
2026-09-15 21:26 ` Armin Wolf
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=20260904224516.8893-1-W_Armin@gmx.de \
--to=w_armin@gmx.de \
--cc=hansg@kernel.org \
--cc=i@rsplwe.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kento@kekto.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=martiya.ar@gmail.com \
--cc=mm3885525@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=qby140326@gmail.com \
--cc=rahulbheda131313@gmail.com \
--cc=vlku.milos.fun@gmail.com \
--cc=wleizc7319@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®