From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 218188] hp_wmi_sensors: probe of 8F1F6435-9F42-42C8-BADC-0E9424F20C9A failed with error -61
Date: Sat, 25 Nov 2023 18:34:47 +0000 [thread overview]
Message-ID: <bug-218188-215701-fpPLLRg8Om@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218188-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218188
--- Comment #6 from Armin Wolf (W_Armin@gmx.de) ---
Can you try this one:
From ecbb0f5eeab921baf51270e554d432ec09ae9b5c Mon Sep 17 00:00:00 2001
From: Armin Wolf <W_Armin@gmx.de>
Date: Sat, 25 Nov 2023 16:46:06 +0100
Subject: [PATCH] platform/x86: wmi: Skip blocks with zero instances
Some machines like the HP Omen 17 ck2000nf contain
WMI blocks with zero instances, so any WMI driver
which tries to handle the associated WMI device will
fail.
Skip such WMI blocks to avoid confusing any WMI drivers.
Signed-off-by: Armin Wolf <W_Armin@gmx.de>
---
drivers/platform/x86/wmi.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/platform/x86/wmi.c b/drivers/platform/x86/wmi.c
index 5c27b4aa9690..5dd22258cb3b 100644
--- a/drivers/platform/x86/wmi.c
+++ b/drivers/platform/x86/wmi.c
@@ -1340,6 +1340,11 @@ static int parse_wdg(struct device *wmi_bus_dev, struct
platform_device *pdev)
if (debug_dump_wdg)
wmi_dump_wdg(&gblock[i]);
+ if (!gblock[i].instance_count) {
+ dev_info(wmi_bus_dev, FW_INFO "%pUL has zero
instances\n", &gblock[i].guid);
+ continue;
+ }
+
if (guid_already_parsed_for_legacy(device, &gblock[i].guid))
continue;
--
2.39.2
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-11-25 18:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 12:54 [Bug 218188] New: hp_wmi_sensors: probe of 8F1F6435-9F42-42C8-BADC-0E9424F20C9A failed with error -61 bugzilla-daemon
2023-11-25 13:40 ` [Bug 218188] " bugzilla-daemon
2023-11-25 15:13 ` bugzilla-daemon
2023-11-25 15:52 ` bugzilla-daemon
2023-11-25 17:00 ` bugzilla-daemon
2023-11-25 17:33 ` bugzilla-daemon
2023-11-25 18:23 ` bugzilla-daemon
2023-11-25 18:34 ` bugzilla-daemon [this message]
2023-11-25 19:50 ` bugzilla-daemon
2023-11-25 19:51 ` bugzilla-daemon
2023-11-25 21:45 ` bugzilla-daemon
2023-11-25 22:07 ` bugzilla-daemon
2023-11-25 22:10 ` bugzilla-daemon
2023-11-26 15:38 ` bugzilla-daemon
2023-11-26 16:16 ` bugzilla-daemon
2023-11-26 19:54 ` bugzilla-daemon
2023-11-26 20:08 ` bugzilla-daemon
2023-11-26 22:49 ` bugzilla-daemon
2023-11-27 19:42 ` bugzilla-daemon
2023-11-27 19:44 ` bugzilla-daemon
2023-11-27 19:44 ` bugzilla-daemon
2023-11-27 21:48 ` bugzilla-daemon
2023-11-28 7:17 ` bugzilla-daemon
2023-11-28 7:17 ` bugzilla-daemon
2023-11-29 9:40 ` bugzilla-daemon
2023-11-29 9:40 ` bugzilla-daemon
2023-11-29 15:22 ` bugzilla-daemon
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=bug-218188-215701-fpPLLRg8Om@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.