From: Hans de Goede <hansg@kernel.org>
To: chipang_kao <prozac2734@gmail.com>,
bryan.odonoghue@linaro.org, ilpo.jarvinen@linux.intel.com,
W_Armin@gmx.de
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] platform: Enable ACPI WMI and ASUS WMI driver for ARM64
Date: Mon, 21 Sep 2026 13:25:56 +0200 [thread overview]
Message-ID: <ee3735b5-6f56-4b88-a582-5bb0aaf3eda8@kernel.org> (raw)
In-Reply-To: <20260921093339.261306-1-chipang_kao@asus.com>
Hi,
On 21-Sep-26 11:33 AM, chipang_kao wrote:
> Hi Bryan, Hans,
>
> Thanks for the review and valuable feedback.
>
>> On Thu, 17 Sep 2026 15:30:00 +0100, Bryan O'Donoghue <bryan.odonoghue@linaro.org> wrote:
>> Thanks, but there's already a series to this effect under discussion:
>> https://lore.kernel.org/all/20260724025959.142826-1-W_Armin@gmx.de/
>>
>> I only now notice the second patch is not covered by Armin's series.
>> But this duplicates Kconfig entries.
>>
>> I suppose the best approach would be to split drivers/platform/x86/Kconfig
>> into two and source the generic one here.
>
> Thanks for pointing out Armin's series and the Kconfig duplication issue.
> I had review Armin's series and make sure not to duplicate work. Regarding
> the driver location/Kconfig split, I agree that avoiding Kconfig duplication
> is necessary, and moving/refactoring the driver directly under platform/wmi
> (as Hans suggested below) seems to be the cleanest path forward.
>
>> On Fri, 18 Sep 2026 09:38:04 +0200, Hans de Goede <hansg@kernel.org> wrote:
>> Yes ACPI / WMI is used on some ARM64 laptops, but AFAIK all of
>> those are currently still booting through Devicetree since
>> the current generation ARM64 laptops is missing various info Linux
>> needs in the ACPI tables. So for a fully functional system
>> Devicetree is necessary.
>> ...
>> Questions:
>> 1. Has this been tested on an actual Asus ARM64 laptop or other
>> ARM64 device?
>> 2. On which laptop/device model ?
>> 3. How was this tested, how was the laptop booted; and does booting
>> it this way lead to loosing any other functionality
>> 4. Were any other kernel patches used during testing?
>
> Regarding Hans's questions:
>
> 1. Yes, this has been tested on an actual ASUS ARM64 laptop.
> 2. This specific model has not been publicly released yet, so I
> cannot disclose the exact model name or marketing designation
> at this stage. However, it is an upcoming ARM64 platform
> featuring ACPI firmware.
> 3. The laptop was booted natively via ACPI firmware (UEFI). To> verify the WMI functionality without modifying the base
> distribution kernel, we built and tested the modules (`wmi.ko`,
> `asus-wmi.ko`, and `asus-nb-wmi.ko`) out-of-tree and loaded
> them using `insmod`. The driver successfully bound to the WMI
> devices exposed by the ACPI tables and functioned as expected.
> 4. No additional kernel patches were required. Note that we have
> dropped patch 1/2 from this series because Armin's patch series
> already removes the X86 dependency from drivers/platform/wmi/Kconfig.
> Since Armin's series is currently under discussion and not yet
> merged, our v2 will focus solely on moving the ASUS drivers to
> drivers/platform/wmi/asus/ while depending on the WMI updates.
Thank you for your answers and this all sounds good to me.
Based on this I've no objections against this series.
Regards,
Hans
next prev parent reply other threads:[~2026-09-21 11:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 2:10 chipang_kao
2026-09-17 2:10 ` [PATCH 1/2] platform/wmi: Remove X86 dependency for ACPI_WMI chipang_kao
2026-09-17 2:10 ` [PATCH 2/2] platform/arm64: Enable ASUS WMI driver support chipang_kao
2026-09-17 9:11 ` Ilpo Järvinen
2026-09-17 9:03 ` [PATCH 0/2] platform: Enable ACPI WMI and ASUS WMI driver for ARM64 Ilpo Järvinen
2026-09-18 7:38 ` Hans de Goede
2026-09-21 9:33 ` chipang_kao
2026-09-21 11:25 ` Hans de Goede [this message]
2026-09-21 14:43 ` [PATCH v2] platform/wmi: Move ASUS platform drivers from x86 to wmi/asus Chipang_Kao
2026-09-21 23:42 ` Denis Benato
2026-09-21 9:48 ` chipang_kao
2026-09-22 3:21 ` [PATCH v3] " chipang_kao
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=ee3735b5-6f56-4b88-a582-5bb0aaf3eda8@kernel.org \
--to=hansg@kernel.org \
--cc=W_Armin@gmx.de \
--cc=bryan.odonoghue@linaro.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=prozac2734@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
all inboxes | Powered by JetHome®