summaryrefslogtreecommitdiff
path: root/lib/memweight.c
diff options
context:
space:
mode:
authorJorge Lopez <jorge.lopez2@hp.com>2022-03-10 15:08:52 -0600
committerHans de Goede <hdegoede@redhat.com>2022-03-14 16:25:27 +0100
commitbe9d73e64957bbd31ee9a0d11adc0f720974c558 (patch)
tree3056690c00eb00f01f9a8b3d67feccac9bc42c79 /lib/memweight.c
parent520ee4ea1cc60251a6e3c911cf0336278aa52634 (diff)
downloadlinux-rt-be9d73e64957bbd31ee9a0d11adc0f720974c558.tar.gz
platform/x86: hp-wmi: Fix 0x05 error code reported by several WMI calls
Several WMI queries leverage hp_wmi_read_int function to read their data. hp_wmi_read_int function was corrected in a previous patch. Now, this function invokes hp_wmi_perform_query with input parameter of size zero and the output buffer of size 4. WMI commands calling hp_wmi_perform_query with input buffer size value of zero are listed below. HPWMI_DISPLAY_QUERY HPWMI_HDDTEMP_QUERY HPWMI_ALS_QUERY HPWMI_HARDWARE_QUERY HPWMI_WIRELESS_QUERY HPWMI_BIOS_QUERY HPWMI_FEATURE_QUERY HPWMI_HOTKEY_QUERY HPWMI_FEATURE2_QUERY HPWMI_WIRELESS2_QUERY HPWMI_POSTCODEERROR_QUERY HPWMI_THERMAL_PROFILE_QUERY HPWMI_FAN_SPEED_MAX_GET_QUERY Invoking those WMI commands with an input buffer size greater than zero will cause error 0x05 to be returned. All WMI commands executed by the driver were reviewed and changes were made to ensure the expected input and output buffer size match the WMI specification. Changes were validated on a HP ZBook Workstation notebook, HP EliteBook x360, and HP EliteBook 850 G8. Additional validation was included in the test process to ensure no other commands were incorrectly handled. Signed-off-by: Jorge Lopez <jorge.lopez2@hp.com> Link: https://lore.kernel.org/r/20220310210853.28367-4-jorge.lopez2@hp.com Reviewed-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Diffstat (limited to 'lib/memweight.c')
0 files changed, 0 insertions, 0 deletions