From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Chris Taraszka <chris@miget.com>
Cc: TuteMthCD <matias.civadda2342001@gmail.com>,
Hans de Goede <hansg@kernel.org>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>, Armin Wolf <W_Armin@gmx.de>,
Mingyou Chen <qby140326@gmail.com>,
kento@kekto.ru
Subject: Re: [PATCH] platform/x86: bitland-mifs-wmi: Add Xiaomi Book Pro 14 platform profile values
Date: Mon, 19 Oct 2026 09:26:33 +0300 (EEST) [thread overview]
Message-ID: <f9da7ec4-2a89-fdd0-b60e-7f7b97b97e05@linux.intel.com> (raw)
In-Reply-To: <CAAcRvKOADz1T_MCv4VB1QxT6uMxmU5Ax7B3HGRYbZ8Ph7+8-rg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]
On Sat, 17 Oct 2026, Chris Taraszka wrote:
> On Mon, 12 Oct 2026, Ilpo Järvinen wrote:
> > I've not seen v2 so far, has there been some progress with this?
> >
> > (Not having the generalization seems a blocker adding many models.)
>
> Hi Ilpo,
>
> Sorry for the silence. Mingyou's v12 5/6 ("platform/x86:
> bitland-mifs-wmi: Add quirks table") now has the {value, profile}
> pair table I described, plus the no_set flag for GET-only values and
> accept_zero_function for SET replies without a function id. That
> covers what my v2 generic patch would have done, so I won't post a
> second one.
Okay, thanks. I'll go with that series then.
> I'll test v12 on the Xiaomi Book Pro 14 and base the
> model entry on top of it.
>
> Mingyou, one issue in v12 5/6, in bitland_mifs_wmi_call():
>
> memcpy(output->data, payload_data, sizeof(*output->data));
>
> data is u8[28], so this copies a single byte. laptop_hwmon_read()
> reads res.data[0..7] for the fan speeds, which would then come from
> uninitialized stack. sizeof(output->data) is what you want.
>
> Kento, you're right that the match has to be on board_name TM2424.
> Since we have the same machine, let's send a single TM2424 entry. If
> you rebase your v2 onto Mingyou's table, I'm fine with it being yours
> and I'll test it here on BIOS XMAPT4B0P0909 with accept_zero_function
> set.
>
> Matias, sorry for the delay. I think your TM2107 v3 can go on top of
> Mingyou's 5/6 directly.
--
i.
prev parent reply other threads:[~2026-10-19 6:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 15:39 Chris Taraszka
2026-09-28 15:49 ` Ilpo Järvinen
2026-09-28 16:41 ` Chris Taraszka
2026-09-28 23:26 ` Matias Civadda
2026-09-29 9:14 ` Ilpo Järvinen
2026-10-12 12:29 ` Ilpo Järvinen
2026-10-17 16:50 ` Chris Taraszka
2026-10-17 17:12 ` Chris Taraszka
2026-10-19 6:26 ` Ilpo Järvinen [this message]
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=f9da7ec4-2a89-fdd0-b60e-7f7b97b97e05@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=chris@miget.com \
--cc=hansg@kernel.org \
--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 \
/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®