From: James Seo <james@equiv.tech>
To: Lukasz Stelmach <l.stelmach@samsung.com>
Cc: Guenter Roeck <linux@roeck-us.net>, Armin Wolf <W_Armin@gmx.de>,
linux-hwmon@vger.kernel.org
Subject: Re: [BUG] hp-wmi-sensors: probe of 8F1F6435-9F42-42C8-BADC-0E9424F20C9A failed with error -22
Date: Tue, 31 Oct 2023 07:16:50 -0700 [thread overview]
Message-ID: <ZUEMUt8t+mWjMYA2@equiv.tech> (raw)
In-Reply-To: <ZUEIcOBpVzxC/+c1@equiv.tech>
On Tue, Oct 31, 2023 at 07:00:17AM -0700, James Seo wrote:
> After using iasl to decompile the DSDT you sent to ACPI Source Language (ASL),
> everything looks fine with HPBIOS_BIOSNumericSensor. Not that I'm particularly
> familiar with ASL, but search for "Name (SEN1, Package (0x06)" and read on to
> the "Method (_INI, 0, NotSerialized)" and the "Method (WQAE, 1, Serialized)"
> lines below. It certainly looks like that's how the BIOS on that system is
> generating HPBIOS_PlatformEvents instances at runtime.
Correction: I meant "HPBIOS_BIOSNumericSensor instances" in the last line here.
Sorry about that.
next prev parent reply other threads:[~2023-10-31 14:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231113115327eucas1p11f84e775ce78deaa01557f3868c2f9dd@eucas1p1.samsung.com>
2023-10-27 15:07 ` [BUG] hp-wmi-sensors: probe of 8F1F6435-9F42-42C8-BADC-0E9424F20C9A failed with error -22 Lukasz Stelmach
2023-10-27 17:07 ` Guenter Roeck
2023-10-27 18:50 ` Armin Wolf
2023-10-28 18:37 ` James Seo
2023-10-31 12:05 ` Lukasz Stelmach
2023-10-31 14:00 ` James Seo
2023-10-31 14:16 ` James Seo [this message]
2023-10-31 14:47 ` Guenter Roeck
2023-10-31 19:07 ` Lukasz Stelmach
2023-10-31 19:28 ` Guenter Roeck
2023-10-31 21:07 ` Lukasz Stelmach
2023-10-31 22:34 ` Armin Wolf
2023-11-01 4:34 ` James Seo
2023-11-02 1:11 ` Armin Wolf
2023-11-02 5:11 ` James Seo
2023-11-01 5:52 ` James Seo
2023-11-02 8:15 ` Lukasz Stelmach
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=ZUEMUt8t+mWjMYA2@equiv.tech \
--to=james@equiv.tech \
--cc=W_Armin@gmx.de \
--cc=l.stelmach@samsung.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
/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.