From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Denis Benato <denis.benato@linux.dev>
Cc: linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Limonciello, Mario" <mario.limonciello@amd.com>,
"Luke D . Jones" <luke@ljones.dev>,
"Alok Tiwari" <alok.a.tiwari@oracle.com>,
"Derek John Clark" <derekjohn.clark@gmail.com>,
"Mateusz Schyboll" <dragonn@op.pl>,
porfet828@gmail.com, "Denis Benato" <benato.denis96@gmail.com>
Subject: Re: [PATCH v17 0/9] platform/x86: Add asus-armoury driver
Date: Wed, 12 Nov 2025 15:43:41 +0100 [thread overview]
Message-ID: <aRSdHcO1WCPmG63W@black.igk.intel.com> (raw)
In-Reply-To: <20251102215319.3126879-1-denis.benato@linux.dev>
On Sun, Nov 02, 2025 at 10:53:10PM +0100, Denis Benato wrote:
> Hi all,
>
> the TL;DR:
> 1. Introduce new module to contain bios attributes, using fw_attributes_class
> 2. Deprecate all possible attributes from asus-wmi that were added ad-hoc
> 3. Remove those in the next LTS cycle
>
> The idea for this originates from a conversation with Mario Limonciello
> https://lore.kernel.org/platform-driver-x86/371d4109-a3bb-4c3b-802f-4ec27a945c99@amd.com/
>
> It is without a doubt much cleaner to use, easier to discover, and the
> API is well defined as opposed to the random clutter of attributes I had
> been placing in the platform sysfs. Given that Derek is also working on a
> similar approach to Lenovo in part based on my initial work I'd like to think
> that the overall approach is good and may become standardised for these types
> of things.
>
> Regarding PPT: it is intended to add support for "custom" platform profile
> soon. If it's a blocker for this patch series being accepted I will drop the
> platform-x86-asus-armoury-add-ppt_-and-nv_-tuning.patch and get that done
> separately to avoid holding the bulk of the series up. Ideally I would like
> to get the safe limits in so users don't fully lose functionality or continue
> to be exposed to potential instability from setting too low, or be mislead
> in to thinking they can set limits higher than actual limit.
>
> The bulk of the PPT patch is data, the actual functional part is relatively
> small and similar to the last version.
>
> Unfortunately I've been rather busy over the months and may not cover
> everything in the v7 changelog but I've tried to be as comprehensive as I can.
This is more files starter with asus in PDx86.
Perhaps it's a time to have drivers/platform/x86/asus/ ?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-11-12 14:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 21:53 [PATCH v17 0/9] platform/x86: Add asus-armoury driver Denis Benato
2025-11-02 21:53 ` [PATCH v17 1/9] platform/x86: asus-wmi: export symbols used for read/write WMI Denis Benato
2025-11-02 21:53 ` [PATCH v17 2/9] platform/x86: asus-armoury: move existing tunings to asus-armoury module Denis Benato
2025-11-02 21:53 ` [PATCH v17 3/9] platform/x86: asus-armoury: add panel_hd_mode attribute Denis Benato
2025-11-02 21:53 ` [PATCH v17 4/9] platform/x86: asus-armoury: add apu-mem control support Denis Benato
2025-11-02 21:53 ` [PATCH v17 5/9] platform/x86: asus-armoury: add core count control Denis Benato
2025-11-02 21:53 ` [PATCH v17 6/9] platform/x86: asus-armoury: add screen auto-brightness toggle Denis Benato
2025-11-02 21:53 ` [PATCH v17 7/9] platform/x86: asus-wmi: deprecate bios features Denis Benato
2025-11-02 21:53 ` [PATCH v17 8/9] platform/x86: asus-wmi: rename ASUS_WMI_DEVID_PPT_FPPT Denis Benato
2025-11-02 21:53 ` [PATCH v17 9/9] platform/x86: asus-armoury: add ppt_* and nv_* tuning knobs Denis Benato
2025-11-10 15:17 ` [PATCH v17 0/9] platform/x86: Add asus-armoury driver Ilpo Järvinen
2025-11-10 18:54 ` Denis Benato
2025-11-11 10:38 ` Ilpo Järvinen
2025-11-11 20:22 ` Denis Benato
2025-11-12 12:42 ` Ilpo Järvinen
2025-11-12 13:44 ` Mario Limonciello
2025-11-12 19:23 ` Denis Benato
2025-11-12 19:24 ` Mario Limonciello
2025-11-12 19:30 ` Denis Benato
2025-11-12 19:33 ` Mario Limonciello
2025-11-12 19:20 ` Denis Benato
2025-11-12 14:43 ` Andy Shevchenko [this message]
2025-11-12 19:26 ` Denis Benato
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=aRSdHcO1WCPmG63W@black.igk.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=alok.a.tiwari@oracle.com \
--cc=benato.denis96@gmail.com \
--cc=denis.benato@linux.dev \
--cc=derekjohn.clark@gmail.com \
--cc=dragonn@op.pl \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=porfet828@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