mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Armin Wolf <W_Armin@gmx.de>
To: Justin Vargas <justinyvar@gmail.com>,
	jlee@suse.com, hansg@kernel.org, ilpo.jarvinen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: acer-wmi: Add support for Acer Nitro ANV15-51
Date: Thu, 30 Jul 2026 11:17:03 +0200	[thread overview]
Message-ID: <a7c7611d-1721-407d-a4d3-ec096c5e34e2@gmx.de> (raw)
In-Reply-To: <20260729235125.1698-1-justinyvar@gmail.com>

Am 30.07.26 um 01:51 schrieb Justin Vargas:

> The Acer Nitro ANV15-51 uses the Predator V4 WMI interface for thermal
> profile handling and hardware monitoring, but has no quirk entry, so
> these features are only available when the predator_v4 module parameter
> is passed manually.
>
> Add a quirk entry for this model.
>
> Note that this machine does not support the turbo thermal profile: its
> supported profiles bitmap (misc setting 0x0A) reads 0x53, and writing
> PLATFORM_PROFILE_PERFORMANCE is rejected by the firmware. The four
> remaining profiles work as expected.

Hi,

can you create a custom quirk entry and check if controlling the CPU/GPU fans
works? For this you need to fill-in the number of CPU/GPU fans inside struct quirk_entry
and set "pwm" to "1".

I think fo something like "quirk_acer_predator_ph16_72", just without ".tubo = 1".

Thanks,
Armin Wolf

> Assisted-by: Claude:claude-opus-5
> Signed-off-by: Justin Vargas <justinyvar@gmail.com>
> Tested-by: Justin Vargas <justinyvar@gmail.com>
> ---
> v2: Add Assisted-by trailer per
>      Documentation/process/coding-assistants.rst. No change to the code.
>
> Tested on an Acer Nitro ANV15-51, BIOS V1.60 (04/08/2026),
> kernel 7.0.11-1-cachyos:
>
>    $ sudo dmidecode -s system-product-name
>    Nitro ANV15-51
>
>    $ sudo modprobe acer_wmi predator_v4=1
>    $ cat /sys/firmware/acpi/platform_profile_choices
>    low-power quiet balanced balanced-performance performance
>
> Writing low-power, quiet, balanced and balanced-performance all succeed
> and audibly change fan behaviour. Writing performance is rejected by the
> firmware, consistent with the supported profiles bitmap (0x0A) reading
> 0x53, i.e. bit 5 (turbo) clear.
>
> hwmon works: sensors reports acer-isa-0ace with fan1 3024 RPM,
> fan2 2685 RPM, temp1 +48.0 C.
>
> The WMI mechanism was cross-checked on Windows, where NitroSense switches
> profiles via SetGamingMiscSetting with index 0x0B and the same profile
> values used by this driver.
>
> The analysis and patch were produced with AI assistance (see the
> Assisted-by trailer); all testing was performed by me on the physical
> machine, and I take responsibility for the patch as signed off above.
>
>   drivers/platform/x86/acer-wmi.c | 9 +++++++++
>   1 file changed, 9 insertions(+)
>
> diff --git a/drivers/platform/x86/acer-wmi.c b/drivers/platform/x86/acer-wmi.c
> index e0eaaefb13d..a7290f85166 100644
> --- a/drivers/platform/x86/acer-wmi.c
> +++ b/drivers/platform/x86/acer-wmi.c
> @@ -662,6 +662,15 @@ static const struct dmi_system_id acer_quirks[] __initconst = {
>   		},
>   		.driver_data = &quirk_acer_nitro_an515_58,
>   	},
> +	{
> +		.callback = dmi_matched,
> +		.ident = "Acer Nitro ANV15-51",
> +		.matches = {
> +			DMI_MATCH(DMI_SYS_VENDOR, "Acer"),
> +			DMI_MATCH(DMI_PRODUCT_NAME, "Nitro ANV15-51"),
> +		},
> +		.driver_data = &quirk_acer_predator_v4,
> +	},
>   	{
>   		.callback = dmi_matched,
>   		.ident = "Acer Predator PH315-53",

  reply	other threads:[~2026-07-30  9:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 22:29 [PATCH] " Justin Vargas
2026-07-29 23:51 ` [PATCH v2] " Justin Vargas
2026-07-30  9:17   ` Armin Wolf [this message]
2026-07-30 14:05     ` Justin Vargas
2026-07-31  7:15       ` Justin Vargas
2026-08-18  0:51         ` Justin Vargas
2026-08-19  4:17 ` [PATCH v3] " Justin Vargas
2026-09-18 11:19   ` Ilpo Järvinen
2026-09-20  5:39 ` [PATCH v4] " Justin Vargas
2026-10-05 18:24   ` Ilpo Järvinen

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=a7c7611d-1721-407d-a4d3-ec096c5e34e2@gmx.de \
    --to=w_armin@gmx.de \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jlee@suse.com \
    --cc=justinyvar@gmail.com \
    --cc=linux-kernel@vger.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 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®