mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Armin Wolf <W_Armin@gmx.de>
To: Mario Limonciello <superm1@kernel.org>,
	viro@zeniv.linux.org.uk, brauner@kernel.org, hansg@kernel.org,
	ilpo.jarvinen@linux.intel.com
Cc: jack@suse.cz, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 0/4] platform/x86: wmi: Prepare for future changes
Date: Wed, 5 Nov 2025 23:16:27 +0100	[thread overview]
Message-ID: <17515e4d-6e3b-4eb9-99eb-840933315d55@gmx.de> (raw)
In-Reply-To: <e40a0d9c-7f38-44ab-a954-b09c9687ea88@kernel.org>

Am 04.11.25 um 21:52 schrieb Mario Limonciello:

> On 11/4/25 2:45 PM, Armin Wolf wrote:
>> After over a year of reverse engineering, i am finally ready to
>> introduce support for WMI-ACPI marshalling inside the WMI driver core.
> marshaling> Since the resulting patch series is quite large, i am 
> planning to
>> submit the necessary patches as three separate patch series.
>>
>> This is supposed to be the first of the three patch series. Its main
>> purpose is to prepare the WMI driver core for the upcoming changes.
>> The first patch fixes an issue inside the nls utf16 to utf8 conversion
>> code, while the next two patches fix some minor issues inside the WMI
>> driver core itself. The last patch finally moves the code of the WMI
>> driver core into a separate repository to allow for future additions
>> without cluttering the main directory.
>
> One question I have here on the patch to move things.
>
> Since Windows on ARM (WoA) laptops are a thing - is this still 
> actually x86 specific?  I am wondering if this should be moving to a 
> different subsystem altogether like ACPI; especially now with this 
> impending other large patch series you have on your way.

I know of a few WoA laptops that contain ACPI-WMI devices, meaning this driver is indeed not x86-specific.
However i need to make some changes to the WMI driver core (and actually tests it on a AArch64 VM) first
before moving it out of drivers/platform/x86.

Once i am actually ready for this i would prefer to move the whole stuff to drivers/platform, as drivers/acpi
IMHO is better suited for core ACPI drivers.

Thanks,
Armin Wolf

>>
>> Armin Wolf (4):
>>    fs/nls: Fix utf16 to utf8 conversion
>>    platform/x86: wmi: Use correct type when populating ACPI objects
>>    platform/x86: wmi: Remove extern keyword from prototypes
>>    platform/x86: wmi: Move WMI core code into a separate directory
>>
>>   Documentation/driver-api/wmi.rst           |  2 +-
>>   MAINTAINERS                                |  2 +-
>>   drivers/platform/x86/Kconfig               | 30 +------------------
>>   drivers/platform/x86/Makefile              |  2 +-
>>   drivers/platform/x86/wmi/Kconfig           | 34 ++++++++++++++++++++++
>>   drivers/platform/x86/wmi/Makefile          |  8 +++++
>>   drivers/platform/x86/{wmi.c => wmi/core.c} | 34 +++++++++++++---------
>>   fs/nls/nls_base.c                          | 16 +++++++---
>>   include/linux/wmi.h                        | 15 ++++------
>>   9 files changed, 84 insertions(+), 59 deletions(-)
>>   create mode 100644 drivers/platform/x86/wmi/Kconfig
>>   create mode 100644 drivers/platform/x86/wmi/Makefile
>>   rename drivers/platform/x86/{wmi.c => wmi/core.c} (98%)
>>
>
> Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>

  reply	other threads:[~2025-11-05 22:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 20:45 Armin Wolf
2025-11-04 20:45 ` [PATCH 1/4] fs/nls: Fix utf16 to utf8 conversion Armin Wolf
2025-11-04 20:45 ` [PATCH 2/4] platform/x86: wmi: Use correct type when populating ACPI objects Armin Wolf
2025-11-04 20:45 ` [PATCH 3/4] platform/x86: wmi: Remove extern keyword from prototypes Armin Wolf
2025-11-04 20:45 ` [PATCH 4/4] platform/x86: wmi: Move WMI core code into a separate directory Armin Wolf
2025-11-05  9:41   ` Ilpo Järvinen
2025-11-05 22:10     ` Armin Wolf
2025-11-10 10:54       ` Ilpo Järvinen
2025-11-04 20:52 ` [PATCH 0/4] platform/x86: wmi: Prepare for future changes Mario Limonciello
2025-11-05 22:16   ` Armin Wolf [this message]
2025-11-10 11:00     ` Ilpo Järvinen
2025-11-10 11:03       ` Armin Wolf

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=17515e4d-6e3b-4eb9-99eb-840933315d55@gmx.de \
    --to=w_armin@gmx.de \
    --cc=brauner@kernel.org \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=superm1@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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®