Changes in core.c

c17ee635fd3a482b2ad2bf5e269755c2eae5f25e - Merge drm/drm-fixes into drm-misc-fixes

Mon, 23 Feb 2026 09:09:45 +0000

Merge drm/drm-fixes into drm-misc-fixes7.0-rc1 was just released, let's merge it to kick the new release cycle.Signed-off-by: Maxime Ripard List of files: /linux/drivers/platform/wmi/core.c

bf4afc53b77aeaa48b5409da5c8da6bb4eff7f43 - Convert 'alloc_obj' family to use the new default GFP_KERNEL argument

Sun, 22 Feb 2026 00:37:42 +0000

Convert 'alloc_obj' family to use the new default GFP_KERNEL argumentThis was done entirely with mindless brute force, using git grep -l '\ List of files: /linux/drivers/platform/wmi/core.c

8934827db5403eae57d4537114a9ff88b0a8460f - Merge tag 'kmalloc_obj-treewide-v7.0-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux

Sat, 21 Feb 2026 19:02:58 +0000

Merge tag 'kmalloc_obj-treewide-v7.0-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linuxPull kmalloc_obj conversion from Kees Cook: "This does the tree-wide conversion to kmalloc_obj() and friends using coccinelle, with a subsequent small manual cleanup of whitespace alignment that coccinelle does not handle. This uncovered a clang bug in __builtin_counted_by_ref(), so the conversion is preceded by disabling that for current versions of clang. The imminent clang 22.1 release has the fix. I've done allmodconfig build tests for x86_64, arm64, i386, and arm. I did defconfig builds for alpha, m68k, mips, parisc, powerpc, riscv, s390, sparc, sh, arc, csky, xtensa, hexagon, and openrisc"* tag 'kmalloc_obj-treewide-v7.0-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux: kmalloc_obj: Clean up after treewide replacements treewide: Replace kmalloc with kmalloc_obj for non-scalar types compiler_types: Disable __builtin_counted_by_ref for Clang List of files: /linux/drivers/platform/wmi/core.c

69050f8d6d075dc01af7a5f2f550a8067510366f - treewide: Replace kmalloc with kmalloc_obj for non-scalar types

Sat, 21 Feb 2026 07:49:23 +0000

treewide: Replace kmalloc with kmalloc_obj for non-scalar typesThis is the result of running the Coccinelle script fromscripts/coccinelle/api/kmalloc_objs.cocci. The script is designed toavoid scalar types (which need careful case-by-case checking), andinstead replace kmalloc-family calls that allocate struct or unionobject instances:Single allocations: kmalloc(sizeof(TYPE), ...)are replaced with: kmalloc_obj(TYPE, ...)Array allocations: kmalloc_array(COUNT, sizeof(TYPE), ...)are replaced with: kmalloc_objs(TYPE, COUNT, ...)Flex array allocations: kmalloc(struct_size(PTR, FAM, COUNT), ...)are replaced with: kmalloc_flex(*PTR, FAM, COUNT, ...)(where TYPE may also be *VAR)The resulting allocations no longer return "void *", instead returning"TYPE *".Signed-off-by: Kees Cook List of files: /linux/drivers/platform/wmi/core.c

f50822fd8675c68d294e89bd102f7b487ca3acd3 - Merge tag 'platform-drivers-x86-v7.0-1' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86

Fri, 13 Feb 2026 23:39:15 +0000

Merge tag 'platform-drivers-x86-v7.0-1' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86Pull x86 platform driver updates from Ilpo Järvinen: "Highlights: - amd/pmf: - Avoid overwriting BIOS input values when events occur rapidly - Fix PMF driver issues related to S4 (in part on crypto/ccp side) - Add NPU metrics API (for accel side consumers) - Allow disabling Smart PC function through a module parameter - asus-wmi & HID/asus: - Unification of backlight control (replaces quirks) - Support multiple interfaces for controlling keyboard/RGB brightness - Simplify init sequence - hp-wmi: - Add manual fan control for Victus S models - Add fan mode keep-alive - Fix platform profile values for Omen 16-wf1xxx - Add EC offset to get the thermal profile - intel/pmc: Show substate residencies also for non-primary PMCs - intel/ISST: - Store and restore data for all domains - Write interface improvements - lenovo-wmi: - Support multiple Capability Data - Add HWMON reporting and tuning support - mellanox/mlx-platform: Add HI173 & HI174 support - surface/aggregator_registry: Add Surface Pro 11 (QCOM) - thinkpad_acpi: Add support for HW damage detection capability - uniwill: Implement cTGP setting - wmi: - Introduce marshalling support - Convert a few drivers to use the new buffer-based WMI API - tools/power/x86/intel-speed-select: Allow read operations for non-root - Miscellaneous cleanups / refactoring / improvements"* tag 'platform-drivers-x86-v7.0-1' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86: (68 commits) platform/x86: lenovo-wmi-{capdata,other}: Fix HWMON channel visibility platform/x86: hp-wmi: Add EC offsets to read Victus S thermal profile platform: mellanox: mlx-platform: Add support DGX flavor of next-generation 800GB/s ethernet switch. platform: mellanox: mlx-platform: Add support for new Nvidia DGX system based on class VMOD0010 HID: asus: add support for the asus-wmi brightness handler platform/x86: asus-wmi: add keyboard brightness event handler platform/x86: asus-wmi: remove unused keyboard backlight quirk HID: asus: listen to the asus-wmi brightness device instead of creating one platform/x86: asus-wmi: Add support for multiple kbd led handlers HID: asus: early return for ROG devices HID: asus: move vendor initialization to probe HID: asus: fortify keyboard handshake HID: asus: use same report_id in response HID: asus: initialize additional endpoints only for certain devices HID: asus: simplify RGB init sequence platform/wmi: string-kunit: Add missing oversized string test case platform/x86/amd/pmf: Added a module parameter to disable the Smart PC function platform/x86/uniwill: Implement cTGP setting platform/x86: uniwill-laptop: Introduce device descriptor system platform/x86/amd: Use scope-based cleanup for wbrf_record() ... List of files: /linux/drivers/platform/wmi/core.c

015b70a6ae697f5dac3562e4ab45ee275d98860b - platform/wmi: Introduce marshalling support

Fri, 16 Jan 2026 20:41:08 +0000

platform/wmi: Introduce marshalling supportThe Windows WMI-ACPI driver likely uses wmilib [1] to interact withthe WMI service in userspace. Said library uses plain byte buffersfor exchanging data, so the WMI-ACPI driver has to convert betweenthose byte buffers and ACPI objects returned by the ACPI firmware.The format of the byte buffer is publicly documented [2], and aftersome reverse eingineering of the WMI-ACPI driver using a set of customACPI tables, the following conversion rules have been discovered:- ACPI integers are always converted into a uint32- ACPI strings are converted into special WMI strings- ACPI buffers are copied as-is- ACPI packages are unpackedExtend the ACPI-WMI driver to also perform this kind of marshallingfor WMI data blocks, methods and events. Doing so gives us a numberof benefits:- WMI drivers are not restricted to a fixed set of supported ACPI data types anymore, see dell-wmi-aio (integer vs buffer) and hp-wmi-sensors (string vs buffer)- correct marshalling of WMI strings when data blocks are marked as requiring ACPI strings instead of ACPI buffers- development of WMI drivers without having to understand ACPIThis eventually should result in better compatibility with someACPI firmware implementations and in simpler WMI drivers. There arehowever some differences between the original Windows driver andthe ACPI-WMI driver when it comes to ACPI object conversions:- the Windows driver copies internal _ACPI_METHOD_ARGUMENT_V1 data structures into the output buffer when encountering nested ACPI packages. This is very likely an error inside the driver itself, so we do not support nested ACPI packages.- when converting WMI strings (UTF-16LE) into ACPI strings (ASCII), the Windows driver replaces non-ascii characters (ä -> a, & -> ?) instead of returning an error. This behavior is not documented anywhere and might lead to severe errors in some cases (like setting BIOS passwords over WMI), so we simply return an error.As the current bus-based WMI API is based on ACPI buffers, a newAPI is necessary. The legacy GUID-based WMI API is not extended tosupport marshalling, as WMI drivers using said API are expected tomove to the bus-based WMI API in the future.[1] https://learn.microsoft.com/de-de/windows-hardware/drivers/ddi/wmilib/[2] https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/ driver-defined-wmi-data-itemsSigned-off-by: Armin Wolf Link: https://patch.msgid.link/20260116204116.4030-2-W_Armin@gmx.deReviewed-by: Ilpo Järvinen Signed-off-by: Ilpo Järvinen List of files: /linux/drivers/platform/wmi/core.c

ec496f77b4c11036cc835d6f045fb5e5ef1e6530 - Merge branch 'for-6.20/sony' into for-linus

Mon, 09 Feb 2026 16:33:26 +0000

Merge branch 'for-6.20/sony' into for-linus- Support for Rock band 4 PS4 and PS5 guitars (Rosalie Wanders) List of files: /linux/drivers/platform/wmi/core.c

cc4adab164b772a34b3340d644b7c4728498581e - Merge tag 'v6.19-rc1' into msm-next

Tue, 20 Jan 2026 22:06:55 +0000

Merge tag 'v6.19-rc1' into msm-nextMerge Linux 6.19-rc1 in order to catch up with other changes (e.g. UBWCconfig database defining UBWC_6).Signed-off-by: Dmitry Baryshkov List of files: /linux/drivers/platform/wmi/core.c

5add3c3c280a35f7e258e9cef7607db5a2e56fdc - Merge drm/drm-next into drm-xe-next

Fri, 19 Dec 2025 10:51:22 +0000

Merge drm/drm-next into drm-xe-nextBackmerging to bring in 6.19-rc1. An important upstream bugfix andto help unblock PTL CI.Signed-off-by: Thomas Hellström List of files: /linux/drivers/platform/wmi/core.c

b8304863a3990d0f18c38e5b94191830a63ee1af - Merge drm/drm-next into drm-intel-next

Mon, 15 Dec 2025 13:24:02 +0000

Merge drm/drm-next into drm-intel-nextSync-up some display code needed for Async flips refactor.Signed-off-by: Rodrigo Vivi List of files: /linux/drivers/platform/wmi/core.c

7f790dd21a931c61167f7bdc327aecf2cebad327 - Merge drm/drm-next into drm-misc-next

Mon, 15 Dec 2025 08:27:39 +0000

Merge drm/drm-next into drm-misc-nextLet's kickstart the v6.20 (7.0?) release cycle.Signed-off-by: Maxime Ripard List of files: /linux/drivers/platform/wmi/core.c

ec439c38013550420aecc15988ae6acb670838c1 - Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf after 6.19-rc1

Wed, 17 Dec 2025 05:29:38 +0000

Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf after 6.19-rc1Cross-merge BPF and other fixes after downstream PR.Signed-off-by: Alexei Starovoitov List of files: /linux/drivers/platform/wmi/core.c

24f171c7e145f43b9f187578e89b0982ce87e54c - Merge tag 'asoc-fix-v6.19-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus

Sun, 21 Dec 2025 10:11:11 +0000

Merge tag 'asoc-fix-v6.19-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linusASoC: Fixes for v6.19We've been quite busy with fixes since the merge window, though not inany particularly exciting ways - the standout thing is the fix for _SXcontrols which were broken by a change to how we do clamping, otherwiseit's all fairly run of the mill fixes and quirks. List of files: /linux/drivers/platform/wmi/core.c

84318277d6334c6981ab326d4acc87c6a6ddc9b8 - Merge remote-tracking branch 'drm/drm-fixes' into drm-misc-fixes

Mon, 15 Dec 2025 11:53:27 +0000

Merge remote-tracking branch 'drm/drm-fixes' into drm-misc-fixesPull in rc1 to include all changes since the merge window closed,and grab all fixes and changes from drm/drm-next.Signed-off-by: Maarten Lankhorst List of files: /linux/drivers/platform/wmi/core.c

e2c1b56f3dfa014128e775e898774c0356e3ff05 - platform/x86: wmi: Move WMI core code into a separate directory

Tue, 11 Nov 2025 13:11:25 +0000

platform/x86: wmi: Move WMI core code into a separate directoryMove the WMI core code into a separate directory to prepare forfuture additions to the WMI driver. Also update the descriptionof the Kconfig entry to better fit with the other subsystemKconfig entries.Signed-off-by: Armin Wolf Link: https://patch.msgid.link/20251111131125.3379-5-W_Armin@gmx.deReviewed-by: Ilpo Järvinen Signed-off-by: Ilpo Järvinen List of files: /linux/drivers/platform/wmi/core.c

c209195a2a4ad920ff481b56628ca942d62e01b1 - platform/x86: wmi: Use correct type when populating ACPI objects

Tue, 11 Nov 2025 13:11:23 +0000

platform/x86: wmi: Use correct type when populating ACPI objectsWhen evaluating a WMxx/WSxx ACPI control method, the data buffereither needs to be passed as an ACPI buffer or as an ACPI string.Use the correct type (buffer/string) when populating the associatedACPI object.Signed-off-by: Armin Wolf Link: https://patch.msgid.link/20251111131125.3379-3-W_Armin@gmx.deReviewed-by: Ilpo Järvinen Signed-off-by: Ilpo Järvinen List of files: /linux/drivers/platform/wmi/core.c

88e326b3316a8c6d86c528d31a8da31444716d73 - Merge branch 'fixes' into for-next

Wed, 02 Jul 2025 10:21:23 +0000

Merge branch 'fixes' into for-nextMerge fixes back into for-next to be able to take dell_rbu change thatis build on top of fixes material, and to bring lenovo related changesin sync after the move under lenovo/ subdir in the for-next branch anddiverging changes in the fixes branch. List of files: /linux/drivers/platform/wmi/core.c

cf0b812500e64a7d5e2957abed38c3a97917b34f - platform/x86: wmi: Fix WMI event enablement

Thu, 19 Jun 2025 22:14:39 +0000

platform/x86: wmi: Fix WMI event enablementIt turns out that the Windows WMI-ACPI driver always enables/disablesWMI events regardless of whether they are marked as expensive or not.This finding is further reinforced when reading the documentation ofthe WMI_FUNCTION_CONTROL_CALLBACK callback used by Windows driversfor enabling/disabling WMI devices: The DpWmiFunctionControl routine enables or disables notification of events, and enables or disables data collection for data blocks that the driver registered as expensive to collect.Follow this behavior to fix the WMI event used for reporting hotkeyevents on the Dell Latitude 5400 and likely many more devices.Reported-by: Dmytro Bagrii Closes: https://bugzilla.kernel.org/show_bug.cgi?id=220246Tested-by: Dmytro Bagrii Fixes: 656f0961d126 ("platform/x86: wmi: Rework WCxx/WExx ACPI method handling")Signed-off-by: Armin Wolf Link: https://lore.kernel.org/r/20250619221440.6737-1-W_Armin@gmx.deReviewed-by: Ilpo Järvinen Signed-off-by: Ilpo Järvinen List of files: /linux/drivers/platform/wmi/core.c

73f0f2b52c5ea67b3140b23f58d8079d158839c8 - platform/x86: wmi: Fix WMI device naming issue

Tue, 10 Jun 2025 05:55:26 +0000

platform/x86: wmi: Fix WMI device naming issueWhen multiple WMI devices with the same GUID are presentinside a given system, the WMI driver core might fail toregister all of them.Consider the following scenario: WMI devices ([-]): 05901221-D566-11D1-B2F0-00A0C9062910 (on PNP0C14:00) 05901221-D566-11D1-B2F0-00A0C9062910-1 (on PNP0C14:01)If the WMI core driver somehow unbinds from PNP0C14:00, the followingwill happen upon rebinding:1. The WMI driver core counts all registered WMI devices with a GUID of 05901221-D566-11D1-B2F0-00A0C9062910 (count: 1).2. The new WMI device will be named "05901221-D566-11D1-B2F0-00A0C9062910-1" because another device with the same GUID is already registered (on PNP0C14:01).3. The new WMI device cannot be registered due to a name conflict.Use a IDA when building the WMI device name to avoid such namecollisions by ensuring that a given WMI device ID is not reused.Userspace applications using udev for WMI device detection are notimpacted by this change. Additionally userspace applications that dofully support the existing naming scheme are also not impacted. Onlyuserspace applications using hardcoded sysfs paths will break.Introduce a kconfig option for restoring the old naming scheme togive developers time to fix any compatibility issues.Tested on a Asus Prime B650-Plus.Signed-off-by: Armin Wolf Link: https://lore.kernel.org/r/20250610055526.23688-2-W_Armin@gmx.deReviewed-by: Ilpo Järvinen Signed-off-by: Ilpo Järvinen List of files: /linux/drivers/platform/wmi/core.c

08c9f4029007325e0bbd4fdda05650b03e43f071 - platform/x86: wmi: Call WCxx methods when setting data blocks

Sun, 16 Feb 2025 19:32:50 +0000

platform/x86: wmi: Call WCxx methods when setting data blocksAfter performing some tests with a custom SSDT table available athttps://github.com/Wer-Wolf/acpi-wmi-ssdt i found out that Windowsalso enables data block collection even when the data block isbeing set.Emulate this behaviour to avoid confusing the ACPI firmware.The bus-based API already implements this behaviour, so only thelegacy GUID-based API needs to be changed.Signed-off-by: Armin Wolf Link: https://lore.kernel.org/r/20250216193251.866125-8-W_Armin@gmx.deReviewed-by: Ilpo Järvinen Signed-off-by: Ilpo Järvinen List of files: /linux/drivers/platform/wmi/core.c