From: Denis Benato <denis.benato@linux.dev>
To: platform-driver-x86@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Hans de Goede" <hansg@kernel.org>,
"Corentin Chary" <corentin.chary@gmail.com>,
"Luke Jones" <luke@ljones.dev>, busybox11 <busybox11th@gmail.com>,
"Denis Benato" <benato.denis96@gmail.com>,
"Denis Benato" <denis.benato@linux.dev>
Subject: [PATCH v3 0/4] platform/x86: asus-armoury: reorganize visibility and extend dgpu_disable
Date: Fri, 25 Sep 2026 14:42:24 +0000 [thread overview]
Message-ID: <20260925144229.3693-1-denis.benato@linux.dev> (raw)
Hi all,
This patchset reorganizes the visibility of attribute groups in the Asus
Armoury driver and extends the dGPU disable functionality with a fallback
DEVID for the ProArt H7606 series.
This good idea comes from Ilpo and this patchset is the result of our
productive exchange (link below).
The original author of the patch has stated that he/she wants to remain
anonymous, and asked me to respect that, therefore I will only reuse
the DEVID information from that patch and the commit text as everything
else has become irrelevant anyway after the reorganization of the driver.
Link: https://lore.kernel.org/all/20260810-asus_armoury_dgpu_new_devid-v1-1-0a5c845414e4@gmail.com/
Changelog:
Link v1: https://lore.kernel.org/all/20260916154210.181441-1-denis.benato@linux.dev/
Link v2: https://lore.kernel.org/all/20260923004706.41256-1-denis.benato@linux.dev/
- v2
- platform/x86: asus-armoury: let attribute groups decide their own visibility
- simplify the .c source of the driver making extensive use of .is_visible
- v3:
- platform/x86: asus-armoury: let attribute groups decide their own visibility
- move the moving of a function in its own patch
- platform/x86: asus-armoury: use sysfs_create_groups()
- replace individual sysfs_create_file() calls with sysfs_create_groups()
Cc: busybox11 <busybox11th@gmail.com>
Denis Benato (4):
platform/x86: asus-armoury: move has_valid_limit() above the attribute
declarations
platform/x86: asus-armoury: let attribute groups decide their own
visibility
platform/x86: asus-armoury: add dGPU disable fallback DEVID for ProArt
H7606 series
platform/x86: asus-armoury: use sysfs_create_groups() and
sysfs_remove_groups()
drivers/platform/x86/asus-armoury.c | 284 ++++++++-------------
drivers/platform/x86/asus-armoury.h | 124 +++++++--
include/linux/platform_data/x86/asus-wmi.h | 3 +
3 files changed, 215 insertions(+), 196 deletions(-)
--
2.47.3
next reply other threads:[~2026-09-25 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 14:42 Denis Benato [this message]
2026-09-25 14:42 ` [PATCH v3 1/4] platform/x86: asus-armoury: move has_valid_limit() above the attribute declarations Denis Benato
2026-09-25 14:42 ` [PATCH v3 2/4] platform/x86: asus-armoury: let attribute groups decide their own visibility Denis Benato
2026-09-25 14:42 ` [PATCH v3 3/4] platform/x86: asus-armoury: add dGPU disable fallback DEVID for ProArt H7606 series Denis Benato
2026-09-25 14:42 ` [PATCH v3 4/4] platform/x86: asus-armoury: use sysfs_create_groups() and sysfs_remove_groups() 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=20260925144229.3693-1-denis.benato@linux.dev \
--to=denis.benato@linux.dev \
--cc=benato.denis96@gmail.com \
--cc=busybox11th@gmail.com \
--cc=corentin.chary@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--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®