From: Armin Wolf <W_Armin@gmx.de>
To: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>,
corentin.chary@gmail.com, luke@ljones.dev, hdegoede@redhat.com,
ilpo.jarvinen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Michael Larabel <Michael@phoronix.com>,
Casey Bowman <casey.g.bowman@intel.com>
Subject: Re: [PATCH] platform/x86: asus-wmi: Support setting AIPT modes
Date: Sun, 20 Oct 2024 21:54:56 +0200 [thread overview]
Message-ID: <eee71aa0-d0db-48a7-ade9-4b444c087de5@gmx.de> (raw)
In-Reply-To: <c5aee6fc77427daca6e009cd22c3637bffec0219.camel@linux.intel.com>
Am 20.10.24 um 21:27 schrieb srinivas pandruvada:
> [...]
>
>>> + adev = acpi_dev_get_first_match_dev("PNP0C14", "ATK", -1);
>> Is there really no way of changing the AIPT mode through the WMI
>> interface?
>> I would prefer using the WMI interface if available, since the
>> firmware might
>> assume that FANL is only called through the WMI interface.
>>
> I wish the same. Didn't find any. Asus is aware of this change which I
> submitted, they didn't suggest that there is alternative.
>
>> Do you have a acpidump from a affected device?
>>
> Will send you.
>
> Thanks,
> Srinivas
Thanks,
the return value of DSTS() on your device contains:
- 8-bit current AIPT mode
- 8-bit nothing
- 8-bit constant 0x07
- 8-bit constant 0x0a
Maybe you can try to find out more about the unknown constants. For the rest, you can use
the helper functions provided by the driver.
Thanks,
Armin Wolf
>> Thanks,
>> Armin Wolf
>>
>>> + if (adev) {
>>> + acpi_handle handle = acpi_device_handle(adev);
>>> +
>>> + acpi_dev_put(adev);
>>> +
>>> + if (!acpi_has_method(handle, "FANL"))
>>> + return 0;
>>> +
>>> + asus->acpi_mgmt_handle = handle;
>>> + asus->asus_aipt_present = true;
>>> + dev_info(dev, "ASUS Intelligent Performance
>>> Technology (AIPT) is present\n");
>>> + /*
>>> + * Set the mode corresponding to default Linux
>>> platform power
>>> + * profile Balanced
>>> + */
>>> + asus_wmi_write_aipt_mode(asus, AIPT_STANDARD);
>>> + }
>>> +
>>> return 0;
>>> }
>>>
>
next prev parent reply other threads:[~2024-10-20 19:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 6:50 Srinivas Pandruvada
2024-10-20 19:05 ` Armin Wolf
2024-10-20 19:27 ` srinivas pandruvada
2024-10-20 19:54 ` Armin Wolf [this message]
2024-10-20 22:10 ` srinivas pandruvada
2024-10-20 19:42 ` Armin Wolf
2024-10-23 14:44 ` Mohamed Ghanmi
2024-10-23 16:31 ` Armin Wolf
2024-10-23 17:59 ` Mohamed Ghanmi
2024-10-23 18:57 ` Armin Wolf
2024-10-23 20:15 ` srinivas pandruvada
2024-10-23 20:32 ` Armin Wolf
2024-10-24 18:15 ` srinivas pandruvada
2024-10-25 13:30 ` Mohamed Ghanmi
2024-10-25 18:33 ` Armin Wolf
2024-10-25 18:40 ` Mohamed Ghanmi
2024-10-23 8:15 ` Luke Jones
2024-10-23 19:34 ` srinivas pandruvada
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=eee71aa0-d0db-48a7-ade9-4b444c087de5@gmx.de \
--to=w_armin@gmx.de \
--cc=Michael@phoronix.com \
--cc=casey.g.bowman@intel.com \
--cc=corentin.chary@gmail.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.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®