From: Armin Wolf <W_Armin@gmx.de>
To: Kurt Borja <kuurtb@gmail.com>,
jlee@suse.com, basak.sb2006@gmail.com, rayanmargham4@gmail.com
Cc: hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 1/3] platform/x86: acer-wmi: Fix setting of fan behavior
Date: Sat, 15 Feb 2025 20:35:54 +0100 [thread overview]
Message-ID: <d53c7f66-8efb-4df5-a372-5598aa1f3e01@gmx.de> (raw)
In-Reply-To: <D7T8UQ8PJ7BH.3DGKE2REW8025@gmail.com>
Am 15.02.25 um 19:51 schrieb Kurt Borja:
> On Sat Feb 15, 2025 at 12:45 PM -05, Armin Wolf wrote:
>> After studying the linuwu_sense driver
>> (https://github.com/0x7375646F/Linuwu-Sense) i was able to understand
>> the meaning of the SetGamingFanBehavior() WMI method:
>>
>> - the first 16-bit are a bitmap of all fans affected by a fan behavior
>> change request.
>>
>> - the next 8 bits contain four fan mode fields (2-bit), each being
>> associated with a bit inside the fan bitmap.
>>
>> There are three fan modes: auto, turbo and custom.
>>
>> Use this newfound knowledge to fix the turbo fan handling by setting
>> the correct bits before calling SetGamingFanBehavior(). Also check
>> the result of the WMI method call and return an error should the ACPI
>> firmware signal failure.
>>
>> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
>> ---
>> drivers/platform/x86/acer-wmi.c | 75 +++++++++++++++++++++++----------
>> 1 file changed, 52 insertions(+), 23 deletions(-)
>>
>> diff --git a/drivers/platform/x86/acer-wmi.c b/drivers/platform/x86/acer-wmi.c
>> index 69336bd778ee..f20a882e3650 100644
>> --- a/drivers/platform/x86/acer-wmi.c
>> +++ b/drivers/platform/x86/acer-wmi.c
>> @@ -68,10 +68,19 @@ MODULE_LICENSE("GPL");
>> #define ACER_WMID_SET_GAMING_LED_METHODID 2
>> #define ACER_WMID_GET_GAMING_LED_METHODID 4
>> #define ACER_WMID_GET_GAMING_SYS_INFO_METHODID 5
>> -#define ACER_WMID_SET_GAMING_FAN_BEHAVIOR 14
>> +#define ACER_WMID_SET_GAMING_FAN_BEHAVIOR_METHODID 14
>> #define ACER_WMID_SET_GAMING_MISC_SETTING_METHODID 22
>> #define ACER_WMID_GET_GAMING_MISC_SETTING_METHODID 23
>>
>> +#define ACER_GAMING_FAN_BEHAVIOR_ID_MASK GENMASK_ULL(15, 0)
>> +#define ACER_GAMING_FAN_BEHAVIOR_SET_MODE_MASK GENMASK_ULL(23, 16)
>> +
>> +#define ACER_GAMING_FAN_BEHAVIOR_CPU BIT(0)
>> +#define ACER_GAMING_FAN_BEHAVIOR_GPU BIT(3)
>> +
>> +#define ACER_GAMING_FAN_BEHAVIOR_CPU_MODE_MASK GENMASK(1, 0)
>> +#define ACER_GAMING_FAN_BEHAVIOR_GPU_MODE_MASK GENMASK(7, 6)
>> +
>> #define ACER_GAMING_MISC_SETTING_STATUS_MASK GENMASK_ULL(7, 0)
>> #define ACER_GAMING_MISC_SETTING_INDEX_MASK GENMASK_ULL(7, 0)
>> #define ACER_GAMING_MISC_SETTING_VALUE_MASK GENMASK_ULL(15, 8)
>> @@ -121,6 +130,12 @@ enum acer_wmi_predator_v4_sensor_id {
>> ACER_WMID_SENSOR_GPU_TEMPERATURE = 0x0A,
>> };
>>
>> +enum acer_wmi_gaming_fan_mode {
>> + ACER_WMID_FAN_MODE_AUTO = 0x01,
>> + ACER_WMID_FAN_MODE_TURBO = 0x02,
>> + ACER_WMID_FAN_MODE_CUSTOM = 0x03,
>> +};
>> +
>> enum acer_wmi_predator_v4_oc {
>> ACER_WMID_OC_NORMAL = 0x0000,
>> ACER_WMID_OC_TURBO = 0x0002,
>> @@ -1565,9 +1580,6 @@ static acpi_status WMID_gaming_set_u64(u64 value, u32 cap)
>> case ACER_CAP_TURBO_LED:
>> method_id = ACER_WMID_SET_GAMING_LED_METHODID;
>> break;
>> - case ACER_CAP_TURBO_FAN:
>> - method_id = ACER_WMID_SET_GAMING_FAN_BEHAVIOR;
>> - break;
>> default:
>> return AE_BAD_PARAMETER;
>> }
>> @@ -1618,25 +1630,42 @@ static int WMID_gaming_get_sys_info(u32 command, u64 *out)
>> return 0;
>> }
>>
>> +static int WMID_gaming_set_fan_behavior(u16 fan_bitmap, u8 mode_bitmap)
>> +{
>> + acpi_status status;
>> + u64 input = 0;
>> + u64 result;
>> +
>> + input |= FIELD_PREP(ACER_GAMING_FAN_BEHAVIOR_ID_MASK, fan_bitmap);
>> + input |= FIELD_PREP(ACER_GAMING_FAN_BEHAVIOR_SET_MODE_MASK, mode_bitmap);
>> +
>> + status = WMI_gaming_execute_u64(ACER_WMID_SET_GAMING_FAN_BEHAVIOR_METHODID, input,
>> + &result);
>> + if (ACPI_FAILURE(status))
>> + return -EIO;
>> +
>> + /* TODO: Proper error handling */
>> + pr_notice("Fan behavior return status: %llu\n", result);
> I guess this is missing some ACER_GAMING_FAN_BEHAVIOR_STATUS_MASK
> handling right? This shouldn't mess with testing tho.
Yes, i need to wait for the hardware testers to give feedback before i can implement this.
>> +
>> + return 0;
>> +}
>> +
>> static void WMID_gaming_set_fan_mode(u8 fan_mode)
>> {
>> - /* fan_mode = 1 is used for auto, fan_mode = 2 used for turbo*/
>> - u64 gpu_fan_config1 = 0, gpu_fan_config2 = 0;
>> - int i;
>> -
>> - if (quirks->cpu_fans > 0)
>> - gpu_fan_config2 |= 1;
>> - for (i = 0; i < (quirks->cpu_fans + quirks->gpu_fans); ++i)
>> - gpu_fan_config2 |= 1 << (i + 1);
> I agree on with your explaination in the previous thread, so after the
> TODO is addressed:
>
> Reviewed-by: Kurt Borja <kuurtb@gmail.com>
>
> I do wonder tho, isn't there a WMI operation to get the bitmap of
> available fans? Like in the case of available thermal profiles and
> sensors.
I do not know. There are a couple of other fan-related WMI methods available but they seem
to do something else.
For now i use the hwmon interface for detecting the presence of the CPU and GPU fan. I suspect
that the second GPU fan can also be detected using the hwmon interface.
Thanks,
Armin Wolf
next prev parent reply other threads:[~2025-02-15 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 17:45 [RFC PATCH v2 0/3] platform/x86: acer-wmi: Add fan control support Armin Wolf
2025-02-15 17:45 ` [RFC PATCH v2 1/3] platform/x86: acer-wmi: Fix setting of fan behavior Armin Wolf
2025-02-15 18:51 ` Kurt Borja
2025-02-15 19:35 ` Armin Wolf [this message]
2025-02-15 17:45 ` [RFC PATCH v2 2/3] platform/x86: acer-wmi: Add fan control support Armin Wolf
2025-02-15 17:45 ` [RFC PATCH v2 3/3] platform/x86: acer-wmi: Enable fan control for PH16-72 and PT14-51 Armin Wolf
2025-03-05 0:23 ` [RFC PATCH v2 0/3] platform/x86: acer-wmi: Add fan control support Armin Wolf
2025-03-09 12:51 ` Rayan Margham
2025-03-11 21:53 ` Armin Wolf
2025-03-13 18:21 ` Rayan Margham
2025-03-17 0:18 ` Armin Wolf
2025-08-15 6:17 ` Fa-Iz Faadhillah Ibrahim
2025-08-22 12:02 ` Armin Wolf
[not found] ` <1bb3edd6-405f-4615-831f-301dba525bc3@gmail.com>
2025-08-31 19:33 ` Armin Wolf
2025-09-02 4:39 ` Fa-Iz Faadhillah Ibrahim
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=d53c7f66-8efb-4df5-a372-5598aa1f3e01@gmx.de \
--to=w_armin@gmx.de \
--cc=basak.sb2006@gmail.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jlee@suse.com \
--cc=kuurtb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rayanmargham4@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®