From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: dimich.dmb@gmail.com, kuurtb@gmail.com,
Hans de Goede <hansg@kernel.org>, Armin Wolf <W_Armin@gmx.de>
Cc: corbet@lwn.net, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] platform/x86: wmi: Fix WMI event enablement
Date: Thu, 26 Jun 2025 18:19:58 +0300 [thread overview]
Message-ID: <175095119881.2233.10447558196456889460.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250619221440.6737-1-W_Armin@gmx.de>
On Fri, 20 Jun 2025 00:14:39 +0200, Armin Wolf wrote:
> It turns out that the Windows WMI-ACPI driver always enables/disables
> WMI events regardless of whether they are marked as expensive or not.
> This finding is further reinforced when reading the documentation of
> the WMI_FUNCTION_CONTROL_CALLBACK callback used by Windows drivers
> for enabling/disabling WMI devices:
>
> The DpWmiFunctionControl routine enables or disables
> notification of events, and enables or disables data
> collection for data blocks that the driver registered
> as expensive to collect.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-fixes branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/2] platform/x86: wmi: Fix WMI event enablement
commit: cf0b812500e64a7d5e2957abed38c3a97917b34f
[2/2] platform/x86: wmi: Update documentation of WCxx/WExx ACPI methods
commit: 50b6914fc53c718c5426fb6e9cd9484f9ae967c2
--
i.
prev parent reply other threads:[~2025-06-26 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 22:14 Armin Wolf
2025-06-19 22:14 ` [PATCH 2/2] platform/x86: wmi: Update documentation of WCxx/WExx ACPI methods Armin Wolf
2025-06-25 12:28 ` [PATCH 1/2] platform/x86: wmi: Fix WMI event enablement Ilpo Järvinen
2025-06-25 13:09 ` Armin Wolf
2025-06-25 13:13 ` Ilpo Järvinen
2025-06-26 15:19 ` 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=175095119881.2233.10447558196456889460.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=corbet@lwn.net \
--cc=dimich.dmb@gmail.com \
--cc=hansg@kernel.org \
--cc=kuurtb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/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®