From: Krishna Chomal <krishna.chomal108@gmail.com>
To: Lorenzo Collevecchio <lorenzocollevecchio17@gmail.com>
Cc: platform-driver-x86@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-hwmon@vger.kernel.org, W_Armin@gmx.de
Subject: Re: hp-wmi: WHCM AE_AML_OPERAND_TYPE and fan init -22 on HP OmniBook 5 16-ag1xxx (board 8DF4)
Date: Fri, 16 Oct 2026 22:56:14 +0530 [thread overview]
Message-ID: <atJc2J2hYrdI_Eun@archlinux> (raw)
In-Reply-To: <CAPvUaSpq2d5hkxTaqAL6rBoeHct68Y37C4nSpV+goGZ-QwrCsw@mail.gmail.com>
On Fri, Oct 16, 2026 at 09:06:03AM +0200, Lorenzo Collevecchio wrote:
>Subject: Re: hp-wmi: WHCM AE_AML_OPERAND_TYPE and fan init -22 on HP
>OmniBook 5 16-ag1xxx (board 8DF4)
>
>Hi Krishna,
>
>Thanks a lot for digging into the ACPI code, the explanation makes
>everything fit: the missing GMCF call for HPWMI_GM, Local2 being left
>as an Integer, and the -22 coming from that.
>
>I also tried your suggestion about the platform profile. With
>HPWMI_READ/WRITE the errors should not appear:
>
> Before: dmesg | grep -c WHCM -> 3 (the three boot-time errors)
> cat /sys/firmware/acpi/platform_profile -> quiet
> After: dmesg | grep -c WHCM -> 3 (no new errors)
>
>On the fan: thanks for confirming that acpi_fan reads the EC value
>correctly. Together with hearing the fan on Mint and on CachyOS at
>idle, that makes me fairly comfortable that the 0 RPM readings are the
>fan really being off.
>
>Your plan to query the fan count and hide pwm1_enable and
>fan{1,2}_input when it fails sounds good to me. I am happy to test it
>on 8DF4 whenever you have a patch, and I can rebase it onto a stable
>kernel tree on my side if that is easier for you.
>
>I also tried 7.2.10-1-cachyos: dmesg and the hp-wmi hwmon folder are
>identical to 7.2.9 (three WHCM errors, then the -22 message, and
>pwm1_enable still present).
>
>Thanks again for the time you spent on this.
Thanks, I will share the final proposed patch on your Bugzilla report
(222138), and leave this thread for others to pick up the WQBC/WQBE
errors.
>Best regards,
>Lorenzo
>
[...]
prev parent reply other threads:[~2026-10-16 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 16:03 hp-wmi: WHCM AE_AML_OPERAND_TYPE and fan init -22 on HP OmniBook 5 16-ag1xxx (board 8DF4) Lorenzo Collevecchio
2026-10-11 22:45 ` Armin Wolf
2026-10-12 4:03 ` Krishna Chomal
2026-10-12 8:08 ` Lorenzo Collevecchio
2026-10-12 15:24 ` Krishna Chomal
2026-10-12 16:04 ` Lorenzo Collevecchio
2026-10-12 17:49 ` Krishna Chomal
2026-10-12 19:34 ` Lorenzo Collevecchio
2026-10-13 9:32 ` Lorenzo Collevecchio
2026-10-15 19:58 ` Krishna Chomal
2026-10-16 7:06 ` Lorenzo Collevecchio
2026-10-16 17:26 ` Krishna Chomal [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=atJc2J2hYrdI_Eun@archlinux \
--to=krishna.chomal108@gmail.com \
--cc=W_Armin@gmx.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=lorenzocollevecchio17@gmail.com \
--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.