[Bug 220926] HP ENVY 16-h1xxx (Hayden): hp_wmi platform_profile fails to read/write

[bugzilla-daemon@kernel.org]

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

--- Comment #5 from Suryansh Singh (technosfan14@gmail.com) ---
(In reply to Gibs from comment #3)
> (In reply to Suryansh Singh from comment #2)
> > (In reply to Gibs from comment #1)
> > > I have the same problem on same platform on kernel 7.1.8.
> > > Changing profiles does change fan behavior, but RPM reads 0 with hp-wmi.
> > > 
> > > Package power also seems to max at 40W no matter the profile. On Windows
> I
> > > have peaks of 115W and then drops at 55W after a short while.
> > > 
> > > I also tried mapping my board ID to Omen or Victus configs but doesn't
> work,
> > > the ENVY seems to be different.
> > 
> > Hi,
> > 
> > Could you please provide your board ID, or clarify if it is the same as
> > Andres?
> > 
> > 
> > Are you sure you've tried out all Omen or Victus configs? The latest branch
> > for the platforms/x86 subsystem (pdx86/for-next) has an expanded driver
> > scope compared to the current upstream version of the kernel you're
> running,
> > so consider using the code on that branch for mapping your board ID to
> > specific driver data in hp_wmi_feature_boards[]
> > 
> > 
> > In case none of the existing parameters apply to your ENVY laptop, the EC
> > behavior and specific quirks required to get it working will have to be
> > reverse engineered and patched into the code, rather than the regular patch
> > of mapping the board ID under predefined parameters.
> > You may contact me at my mail if that happens to be true, I'll be glad to
> > help in the whole process if it gets that complex.
> 
> Hello, thank you for offering to help!
> 
> It is the same board:
> cat /sys/class/dmi/id/board_name
> 8BE5
> 
> I had a look on the motherboard and I found a ENE KB9542GF chip, this seems
> to be the EC. It may be present on a few Dell laptops, may have found it on
> an Alienware. There's also a different package for this chip, still marked
> KB9542 but different suffix and QFP package, which is also present on some
> other laptops, like ENVY x360 by the results of some searches.
> 
> I will have a look at the latest branch as you suggested, will report back
> after testing.

(In reply to Gibs from comment #4)
> (In reply to Suryansh Singh from comment #2)
> > (In reply to Gibs from comment #1)
> > > I have the same problem on same platform on kernel 7.1.8.
> > > Changing profiles does change fan behavior, but RPM reads 0 with hp-wmi.
> > > 
> > > Package power also seems to max at 40W no matter the profile. On Windows
> I
> > > have peaks of 115W and then drops at 55W after a short while.
> > > 
> > > I also tried mapping my board ID to Omen or Victus configs but doesn't
> work,
> > > the ENVY seems to be different.
> > 
> > Hi,
> > 
> > Could you please provide your board ID, or clarify if it is the same as
> > Andres?
> > 
> > 
> > Are you sure you've tried out all Omen or Victus configs? The latest branch
> > for the platforms/x86 subsystem (pdx86/for-next) has an expanded driver
> > scope compared to the current upstream version of the kernel you're
> running,
> > so consider using the code on that branch for mapping your board ID to
> > specific driver data in hp_wmi_feature_boards[]
> > 
> > 
> > In case none of the existing parameters apply to your ENVY laptop, the EC
> > behavior and specific quirks required to get it working will have to be
> > reverse engineered and patched into the code, rather than the regular patch
> > of mapping the board ID under predefined parameters.
> > You may contact me at my mail if that happens to be true, I'll be glad to
> > help in the whole process if it gets that complex.
> 
> I tried the version from the next branch but still no results. With
> &omen_v1_no_ec_thermal_params I get a kernel panic, and with the others the
> driver fails to load with hp-wmi hp-wmi: probe with driver hp-wmi failed
> with error -22.

I see, the kernel panic is slightly unusual, but other than that I believe your
board does not match with any of the provided driver data yet, causing a
mismatch between the actual parameters and the ones in the code, and hence the
error.


> For one of them I got an extra:
> hp_wmi: Unknown EC layout for board 8BE5. Thermal profile readback will be
> disabled. Please report this to platform-driver-x86@vger.kernel.org


I'm assuming this one happened when you mapped it to Victus S thermal params,
they still use HP_EC_OFFSET_UNKNOWN, and that is what leads to that warning
message (explicitly defined in hp-wmi.c).


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.

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

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