From: Armin Wolf <W_Armin@gmx.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Hans de Goede <hansg@kernel.org>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux@weissschuh.net, "Rafael J. Wysocki" <rafael@kernel.org>,
lenb@kernel.org, linux-acpi@vger.kernel.org,
alexander.deucher@amd.com, christian.koenig@amd.com,
airlied@gmail.com, simona@ffwll.ch,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
patrik.r.jakobsson@gmail.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de,
jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
rodrigo.vivi@intel.com, tursulin@ursulin.net,
intel-gfx@lists.freedesktop.org, matthew.brost@intel.com,
thomas.hellstrom@linux.intel.com, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v3 0/3] platform/wmi: Add aarch64 support
Date: Wed, 2 Sep 2026 18:58:46 +0200 [thread overview]
Message-ID: <8c70d6af-8dd7-4ffa-81a9-1cb2c5e54101@gmx.de> (raw)
In-Reply-To: <c8445c2e-6799-7856-610c-0742248e1c07@linux.intel.com>
Am 02.09.26 um 11:27 schrieb Ilpo Järvinen:
> On Tue, 1 Sep 2026, Armin Wolf wrote:
>
>> Am 07.08.26 um 23:03 schrieb Armin Wolf:
>>
>>> Am 24.07.26 um 04:59 schrieb Armin Wolf:
>>>
>>>> The aarch64-laptops project found out that some Windows-on-Arm
>>>> notebooks contain WMI-ACPI mapping devices (PNP0C14) that work
>>>> exactly like on x86. Those devices however are currently not
>>>> supported by the WMI driver core due to only supporting x86.
>>>>
>>>> The first patch removes this restriction and allows the WMI
>>>> driver core to run on all architectures that support ACPI.
>>>> The second patch updates the acpi-video driver to take advantage
>>>> of the improved support for architectures other than x86, and
>>>> the last patch enables the generic WMI BMOF driver to support
>>>> aarch64 as well.
>>>>
>>>> All patches have been tested on a ACPI-based aarch64 VM and
>>>> work just fine.
>>> Any thoughts about this series from the GPU driver people?
>>>
>>> Thanks,
>>> Armin Wolf
>> Can i assume that the silence means "looks fine to me"?
> Hi,
>
> Those subjects may be too generic for the GPU people to realize we're
> waiting for their Acks.
>
> I suggest you send non-ML email (private) with a more descriptive subject
> to the relevant maintainers asking for them to take look at this series
> (I'd have done that myself later this week but you can do it as well).
> Such an email is more likely to be caught in their radar.
Good point, i will try this.
Thanks,
Armin Wolf
>>>> Armin Wolf (3):
>>>> platform/wmi: Remove dependency on CONFIG_X86
>>>> ACPI: video: Remove CONFIG_X86 handling from nvidia_wmi_ec_supported()
>>>> platform/x86: wmi-bmof: Move to generic WMI code
prev parent reply other threads:[~2026-09-02 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 2:59 [PATCH v3 0/3] platform/wmi: Add aarch64 support Armin Wolf
2026-07-24 2:59 ` [PATCH v3 1/3] platform/wmi: Remove dependency on CONFIG_X86 Armin Wolf
2026-07-24 2:59 ` [PATCH v3 2/3] ACPI: video: Remove CONFIG_X86 handling from nvidia_wmi_ec_supported() Armin Wolf
2026-09-01 21:30 ` Deucher, Alexander
2026-09-02 17:00 ` Armin Wolf
2026-07-24 2:59 ` [PATCH v3 3/3] platform/x86: wmi-bmof: Move to generic WMI code Armin Wolf
2026-08-07 21:03 ` [PATCH v3 0/3] platform/wmi: Add aarch64 support Armin Wolf
2026-09-01 20:17 ` Armin Wolf
2026-09-02 9:27 ` Ilpo Järvinen
2026-09-02 16:58 ` Armin Wolf [this message]
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=8c70d6af-8dd7-4ffa-81a9-1cb2c5e54101@gmx.de \
--to=w_armin@gmx.de \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=patrik.r.jakobsson@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).