From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: chipang_kao <prozac2734@gmail.com>
Cc: Hans de Goede <hansg@kernel.org>,
bryan.odonoghue@linaro.org, W_Armin@gmx.de,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
chipang_kao <chipang_kao@asus.com>
Subject: Re: [PATCH 2/2] platform/arm64: Enable ASUS WMI driver support
Date: Thu, 17 Sep 2026 12:11:33 +0300 (EEST) [thread overview]
Message-ID: <cea8b0e8-518e-ace7-3fb1-688b29b497d5@linux.intel.com> (raw)
In-Reply-To: <20260917021055.8029-3-chipang_kao@asus.com>
On Thu, 17 Sep 2026, chipang_kao wrote:
> Wire up the Makefile to build drivers/platform/x86/asus-wmi.c
> and asus-nb-wmi.c without duplicating driver source code.
>
> Signed-off-by: chipang_kao <chipang_kao@asus.com>
> ---
> drivers/platform/arm64/Kconfig | 46 +++++++++++++++++++++++++++++++++
> drivers/platform/arm64/Makefile | 2 ++
> 2 files changed, 48 insertions(+)
>
> diff --git a/drivers/platform/arm64/Kconfig b/drivers/platform/arm64/Kconfig
> index e32e01b2a9bd..59aa389d9aab 100644
> --- a/drivers/platform/arm64/Kconfig
> +++ b/drivers/platform/arm64/Kconfig
> @@ -103,4 +103,50 @@ config EC_QCOM_HAMOA
>
> This driver currently supports Hamoa/Purwa/Glymur reference devices.
>
> +config ASUS_WMI
> + tristate "ASUS WMI Driver"
> + depends on ACPI_WMI
> + depends on ACPI_BATTERY
> + depends on INPUT
> + depends on HWMON
> + depends on BACKLIGHT_CLASS_DEVICE
> + depends on RFKILL || RFKILL = n
> + depends on HOTPLUG_PCI
> + depends on ACPI_VIDEO || ACPI_VIDEO = n
> + depends on SERIO_I8042 || SERIO_I8042 = n
> + select INPUT_SPARSEKMAP
> + select LEDS_CLASS
> + select NEW_LEDS
> + select ACPI_PLATFORM_PROFILE
> + help
> + Say Y here if you have a WMI aware Asus laptop (like Eee PCs or new
> + Asus Notebooks).
> +
> + To compile this driver as a module, choose M here: the module will
> + be called asus-wmi.
> +
> +config ASUS_WMI_DEPRECATED_ATTRS
> + bool "BIOS option support in WMI platform (DEPRECATED)"
> + depends on ASUS_WMI
> + default y
> + help
> + Say Y to expose the configurable BIOS options through the asus-wmi
> + driver.
> +
> + This can be used with or without the asus-armoury driver which
> + has the same attributes, but more, and better features.
> +
> +config ASUS_NB_WMI
> + tristate "Asus Notebook WMI Driver"
> + depends on ASUS_WMI
> + help
> + This is a driver for newer Asus notebooks. It adds extra features
> + like wireless radio and bluetooth control, leds, hotkeys, backlight...
> +
> + For more information, see
> + <file:Documentation/ABI/testing/sysfs-platform-asus-wmi>
> +
> + If you have an ACPI-WMI compatible Asus Notebook, say Y or M
> + here.
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.
> +
> endif # ARM64_PLATFORM_DEVICES
> diff --git a/drivers/platform/arm64/Makefile b/drivers/platform/arm64/Makefile
> index 7681be4a46e9..d608b2aa8c12 100644
> --- a/drivers/platform/arm64/Makefile
> +++ b/drivers/platform/arm64/Makefile
> @@ -10,3 +10,5 @@ obj-$(CONFIG_EC_HUAWEI_GAOKUN) += huawei-gaokun-ec.o
> obj-$(CONFIG_EC_LENOVO_YOGA_C630) += lenovo-yoga-c630.o
> obj-$(CONFIG_EC_LENOVO_THINKPAD_T14S) += lenovo-thinkpad-t14s.o
> obj-$(CONFIG_EC_QCOM_HAMOA) += qcom-hamoa-ec.o
> +obj-$(CONFIG_ASUS_WMI) += ../x86/asus-wmi.o
> +obj-$(CONFIG_ASUS_NB_WMI) += ../x86/asus-nb-wmi.o
>
--
i.
next prev parent reply other threads:[~2026-09-17 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 2:10 [PATCH 0/2] platform: Enable ACPI WMI and ASUS WMI driver for ARM64 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 [this message]
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
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=cea8b0e8-518e-ace7-3fb1-688b29b497d5@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=bryan.odonoghue@linaro.org \
--cc=chipang_kao@asus.com \
--cc=hansg@kernel.org \
--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®