From: Armin Wolf <W_Armin@gmx.de>
To: corentin.chary@gmail.com, luke@ljones.dev
Cc: hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 4/5] platform/x86: wmi: Update documentation regarding _WED
Date: Mon, 19 Feb 2024 12:59:18 +0100 [thread overview]
Message-ID: <20240219115919.16526-5-W_Armin@gmx.de> (raw)
In-Reply-To: <20240219115919.16526-1-W_Armin@gmx.de>
Update the WMI ACPI interface documentation to include the fact
that _WED should be evaluated every time an ACPI notification
is received.
Signed-off-by: Armin Wolf <W_Armin@gmx.de>
---
Documentation/wmi/acpi-interface.rst | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/wmi/acpi-interface.rst b/Documentation/wmi/acpi-interface.rst
index d31af0ed9c08..06fb7fcf4413 100644
--- a/Documentation/wmi/acpi-interface.rst
+++ b/Documentation/wmi/acpi-interface.rst
@@ -93,4 +93,7 @@ _WED ACPI method
----------------
Used to retrieve additional WMI event data, its single parameter is a integer
-holding the notification ID of the event.
+holding the notification ID of the event. This method should be evaluated every
+time an ACPI notification is received, since some ACPI implementations use a
+queue to store WMI event data items. This queue will overflow after a couple
+of WMI events are received without retrieving the associated WMI event data.
--
2.39.2
next prev parent reply other threads:[~2024-02-19 11:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 11:59 [PATCH v2 0/5] platform/x86: wmi: Fixes for event data handling Armin Wolf
2024-02-19 11:59 ` [PATCH v2 1/5] platform/x86: wmi: Prevent incompatible event driver from probing Armin Wolf
2024-02-19 11:59 ` [PATCH v2 2/5] platform/x86: wmi: Check if event data is not NULL Armin Wolf
2024-02-20 0:59 ` Armin Wolf
2024-02-20 9:19 ` Ilpo Järvinen
2024-02-21 3:21 ` Armin Wolf
2024-02-19 11:59 ` [PATCH v2 3/5] platform/x86: wmi: Always evaluate _WED when receiving an event Armin Wolf
2024-02-19 11:59 ` Armin Wolf [this message]
2024-02-19 11:59 ` [PATCH v2 5/5] Revert "platform/x86: asus-wmi: Support WMI event queue" Armin Wolf
2024-02-19 12:06 ` [PATCH v2 0/5] platform/x86: wmi: Fixes for event data handling Ilpo Järvinen
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=20240219115919.16526-5-W_Armin@gmx.de \
--to=w_armin@gmx.de \
--cc=corentin.chary@gmail.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--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®