From: Denis Benato <denis.benato@linux.dev>
To: chipang_kao <prozac2734@gmail.com>,
W_Armin@gmx.de, hansg@kernel.org, ilpo.jarvinen@linux.intel.com
Cc: corentin.chary@gmail.com, luke@ljones.dev, scardracs@disroot.org,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] platform/wmi: Move ASUS platform drivers from x86 to wmi/asus
Date: Wed, 23 Sep 2026 14:22:49 +0200 [thread overview]
Message-ID: <da2c36f3-cc44-445f-a2ed-b2019ccdeb36@linux.dev> (raw)
In-Reply-To: <20260923082923.154732-1-chipang_kao@asus.com>
On 9/23/26 10:29, chipang_kao wrote:
> Hi Armin, Hans, and all,
>
> Thank you for the feedback, Armin!
>
> I completely agree that separating WMI core infrastructure from WMI client
> drivers makes logical sense. The reason v3 relocated the drivers to
> drivers/platform/wmi/asus/ was based on Hans's earlier suggestion to use the
> WMI subsystem hierarchy. However, Armin's point about keeping client drivers in
> a brand-specific directory like drivers/platform/asus/ also provides a very
> clean, cross-architecture solution for all ASUS platform drivers.
>
> Regarding the background: yes, the RTX Spark is indeed our target platform.
> ASUS plans to provide user-space applications on Ubuntu to control platform
> features via the WMI interface. During our bring-up on ARM64, we found that no
> ASUS WMI modules were currently available for this architecture due to the
> existing x86 Kconfig restriction. This patch series aims to enable
> cross-architecture WMI support to address this gap.
So my intuition about RTX Spark having those was spot on...
Very good to know. Once those drivers are compiled for arm64
we should be able to reuse the whole asusctl software to get
the driver control every hardware that is there.
> I am happy to go with either path (wmi/asus/ vs. platform/asus/). Hans, Armin,
> what would be the preferred target directory before I prepare [PATCH v4]?
>
> Best regards,
> Chipang Kao
Thanks for taking care of this move: it was planned but with no
product in my hands I decided to postpone this.
Best regards,
Denis
next prev parent reply other threads:[~2026-09-23 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202609221954.123456@gmx.de>
2026-09-23 8:29 ` chipang_kao
2026-09-23 8:42 ` Hans de Goede
2026-09-23 12:18 ` Denis Benato
2026-09-23 12:22 ` Denis Benato [this message]
2026-09-18 7:38 [PATCH 0/2] platform: Enable ACPI WMI and ASUS WMI driver for ARM64 Hans de Goede
2026-09-22 3:21 ` [PATCH v3] platform/wmi: Move ASUS platform drivers from x86 to wmi/asus chipang_kao
2026-09-22 19:54 ` Armin Wolf
2026-09-24 1:58 ` kernel test robot
2026-09-24 2:32 ` kernel test robot
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=da2c36f3-cc44-445f-a2ed-b2019ccdeb36@linux.dev \
--to=denis.benato@linux.dev \
--cc=W_Armin@gmx.de \
--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 \
--cc=prozac2734@gmail.com \
--cc=scardracs@disroot.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®