All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 220926] HP ENVY 16-h1xxx (Hayden): hp_wmi platform_profile fails to read/write
Date: Fri, 21 Aug 2026 10:44:28 +0000	[thread overview]
Message-ID: <bug-220926-215701-dCHgzFTgEJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220926-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220926

--- Comment #6 from Gibs (gibs23@proton.me) ---
(In reply to Suryansh Singh from comment #5)
> 
> Can you attach the text files made out of these commands?
> 
> sudo modprobe ec_sys
> sudo hexdump -C /sys/kernel/debug/ec/ec0/io > ec_dump.txt
> sudo acpidump > acpidump.txt
> 
> If possible, please also provide two more EC dumps, one while plugged in and
> one while on battery power (can be named as ec_charging.txt and
> ec_battery.txt). This will help me isolate the ENVY's performance flags, if
> there are any relevant to the charging status.
> 
> 
> Also, I noticed this a bit late, but in your first comment you mentioned
> that you could switch profile which changed fan behavior, but hp-wmi read
> fan RPM at 0 and the package power didn't change.
> 
> How were you changing the profile, if you meant you did that on Linux, or
> did you change it in Windows prior to rebooting? Since the driver hit a -22
> probe error when you tested, the standard
> /sys/firmware/acpi/platform_profile node shouldn't even be exposed. Was it
> exposed before you even added your board ID in the driver?
> 
> 
> It might take me a while to figure out everything and multiple tests through
> your device to make a working patch, but I'll try my best to help.


I tried dumping with:
```
sudo hexdump -C /sys/kernel/debug/ec/ec0/io > ec_dump.txt
```
But there's too little data in there, only 256 bytes. I looked in acpi dump and
used the 0xFE0B0800 offset to dump 512 bytes from /dev/mem directly with:
```
sudo dd if=/dev/mem bs=1 skip=$((0xFE0B0800)) count=512 2>/dev/null | hexdump
-C
```
So the attached data is from this command, to me it looks like the same data
from ec dump, but more of it. I actually monitored it with:
```
watch -n 0.1 -d "sudo dd if=/dev/mem bs=1 skip=$((0xFE0B0800)) count=512
2>/dev/null | hexdump -C"
```

This allowed me to see highlighted values that changed in time. So what I could
make out is that one fan speed is at 0x11 offset, and the other fan way over at
0x115 for some reason. These two seem to be the actual fan speed values, maybe
% . There's also set fan speed which seem to be at 0x125 and 0x126. Whenever
fan speed changes these two values change instantly, and then the actual fan
speed values start going towards those set values, and they correlate as sound,
ramping up or down.

At 0x127 there seems to be some kind of...fan speed/cooling index? 00 to 04,
where 04 is when fans spun fastest, and 00 at 0 rpm. So maybe I won't be able
to set certain fan speed rather one of these levels of cooling? 

Regarding battery power / connected charger I noticed 0x10 changes from 00 to
01 the moment I connect the charger to the laptop, and one second later or so
0x0e changes from 00 to 1a. When I disconnect the charger both offsets go to
00.

I noticed a few other values that are constantly changing, couldn't correlate
them to anything else, just an offset seems to be some kind of countdown
counter that keeps repeating.

Ah and 0xb0 and 0xb1 seem to be hotspot/die temps, and there's one more temp
that lags a bit at 0xa7, maybe edge sensor or iGPU?

Regarding the profiles:
```
cat /sys/firmware/acpi/platform_profile_choices
cool quiet balanced performance
```

And:
```
cat /sys/firmware/acpi/platform_profile
cat: /sys/firmware/acpi/platform_profile: Invalid argument
```

But this works:
```
echo "quiet" > /sys/firmware/acpi/platform_profile
```
Or any of the 4 options. To me it seemed like the behavior is changing when I
load it with stress -c 20. Fans come on faster when changing from quiet to
performance, higher power draw at low load, I think but not sure, just a quick
test.

Also managed to sort out power limit, I have to:
```
sudo sh -c 'echo 55000000 >
/sys/class/powercap/intel-rapl-mmio:0/constraint_1_power_limit_uw'
```
And this seems to increase the power limit to 55W.

Hope it is clear, sorry if hard to follow. Will attach asked files.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2026-08-21 10:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-31  2:23 [Bug 220926] New: HP ENVY 16-h1xxx (Hayden): hp_wmi platform_profile fails to read/write bugzilla-daemon
2026-08-16 11:21 ` [Bug 220926] " bugzilla-daemon
2026-08-18 12:49 ` bugzilla-daemon
2026-08-19 19:45 ` bugzilla-daemon
2026-08-20  9:37 ` bugzilla-daemon
2026-08-21  2:01 ` bugzilla-daemon
2026-08-21 10:44 ` bugzilla-daemon [this message]
2026-08-21 10:45 ` bugzilla-daemon
2026-08-21 10:45 ` bugzilla-daemon
2026-08-21 10:50 ` bugzilla-daemon
2026-08-21 10:50 ` bugzilla-daemon
2026-08-21 10:50 ` bugzilla-daemon
2026-08-21 10:51 ` bugzilla-daemon
2026-08-21 10:51 ` bugzilla-daemon
2026-08-21 10:52 ` bugzilla-daemon
2026-08-21 10:55 ` bugzilla-daemon
2026-08-21 11:10 ` 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-220926-215701-dCHgzFTgEJ@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.