Commit da6b5aae authored by Linus Torvalds's avatar Linus Torvalds
Browse files

Merge tag 'platform-drivers-x86-v7.1-1' of... 

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

Pull x86 platform driver updates from Ilpo Järvinen:
 "asus-wmi:
   - Retain battery charge threshold during boot which avoids
     unsolicited change to 100%. Return -ENODATA when the limit
     is not yet known
   - Improve screenpad power/brightness handling consistency
   - Fix screenpad brightness range

  barco-p50-gpio:
   - Normalize gpio_get return values

  bitland-mifs-wmi:
   - Add driver for Bitland laptops (supports platform profile,
     hwmon, kbd backlight, gpu mode, hotkeys, and fan boost)

  dell_rbu:
   - Fix using uninitialized value in sysfs write function

  dell-wmi-sysman:
   - Respect destination length when constructing enum strings

  hp-wmi:
   - Propagate fan setting apply failures and log an error
   - Fix sysfs write vs work handler cancel_delayed_work_sync() deadlock
   - Correct keepalive schedule_delayed_work() to mod_delayed_work()
   - Fix u8 underflows in GPU delta calculation
   - Use mutex to protect fan pwm/mode
   - Ignore kbd backlight and FnLock key events that are handled by FW
   - Fix fan table parsing (use correct field)
   - Add support for Omen 14-fb0xxx, 16-n0xxx, 16-wf1xxx, and
     Omen MAX 16-ak0xxxx

  input: trackpoint & thinkpad_acpi:
   - Enable doubletap by default and add sysfs enable/disable

  int3472:
   - Add support for GPIO type 0x02 (IR flood LED)

  intel-speed-select: (updated to v1.26)
   - Avoid using current base frequency as maximum
   - Fix CPU extended family ID decoding
   - Fix exit code
   - Improve error reporting

  intel/vsec:
   - Refactor to support ACPI-enumerated PMT endpoints.

  pcengines-apuv2:
   - Attach software node to the gpiochip

  uniwill:
   - Refactor hwmon to smaller parts to accomodate HW diversity
   - Support USB-C power/performance priority switch through sysfs
   - Add another XMG Fusion 15 (L19) DMI vendor
   - Enable fine-grained features to device lineup mapping

  wmi:
   - Perform output size check within WMI core to allow simpler WMI
     drivers

  misc:
   - acpi_driver -> platform driver conversions (a large number of
     changes from Rafael J. Wysocki)
   - cleanups / refactoring / improvements"

* tag 'platform-drivers-x86-v7.1-1' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86: (106 commits)
  platform/x86: hp-wmi: Add support for Omen 16-wf1xxx (8C77)
  platform/x86: hp-wmi: Add support for Omen 16-n0xxx (8A44)
  platform/x86: hp-wmi: Add support for OMEN MAX 16-ak0xxx (8D87)
  platform/x86: hp-wmi: fix fan table parsing
  platform/x86: hp-wmi: add Omen 14-fb0xxx (board 8C58) support
  platform/wmi: Replace .no_notify_data with .min_event_size
  platform/wmi: Extend wmidev_query_block() to reject undersized data
  platform/wmi: Extend wmidev_invoke_method() to reject undersized data
  platform/wmi: Prepare to reject undersized unmarshalling results
  platform/wmi: Convert drivers to use wmidev_invoke_procedure()
  platform/wmi: Add wmidev_invoke_procedure()
  platform/x86: int3472: Add support for GPIO type 0x02 (IR flood LED)
  platform/x86: int3472: Parameterize LED con_id in registration
  platform/x86: int3472: Rename pled to led in LED registration code
  platform/x86: int3472: Use local variable for LED struct access
  platform/x86: thinkpad_acpi: remove obsolete TODO comment
  platform/x86: dell-wmi-sysman: bound enumeration string aggregation
  platform/x86: hp-wmi: Ignore backlight and FnLock events
  platform/x86: uniwill-laptop: Fix signedness bug
  platform/x86: dell_rbu: avoid uninit value usage in packet_size_write()
  ...
parents b69e4785 344bf523

Documentation/ABI/testing/sysfs-driver-uniwill-laptop

+27 −0
Original line number Diff line number Diff line
@@ -51,3 +51,30 @@ Description: 


		Reading this file returns the current status of the breathing animation

		functionality.



What:		/sys/bus/platform/devices/INOU0000:XX/ctgp_offset

Date:		January 2026

KernelVersion:	7.0

Contact:	Werner Sembach <wse@tuxedocomputers.com>

Description:

		Allows userspace applications to set the configurable TGP offset on top of the base

		TGP. Base TGP and max TGP and therefore the max cTGP offset are device specific.

		Note that setting the maximum cTGP leaves no window open for Dynamic Boost as

		Dynamic Boost also can not go over max TGP. Setting the cTGP to maximum is

		effectively disabling Dynamic Boost and telling the device to always prioritize the

		GPU over the CPU.



		Reading this file returns the current configurable TGP offset.



What:		/sys/bus/platform/devices/INOU0000:XX/usb_c_power_priority

Date:		February 2026

KernelVersion:	7.1

Contact:	Werner Sembach <wse@tuxedocomputers.com>

Description:

		Allows userspace applications to choose the USB-C power distribution profile between

		one that offers a bigger share of the power to the battery and one that offers more

		of it to the CPU. Writing "charging"/"performance" into this file selects the

		respective profile.



		Reading this file returns the profile names with the currently active one in

		brackets.

Documentation/admin-guide/laptops/thinkpad-acpi.rst

+21 −0
Original line number Diff line number Diff line
@@ -1522,6 +1522,27 @@ Currently 2 antenna types are supported as mentioned below: 
The property is read-only. If the platform doesn't have support the sysfs

class is not created.



doubletap_enable

----------------



sysfs: doubletap_enable



Controls whether TrackPoint doubletap events are filtered out. Doubletap is a

feature where quickly tapping the TrackPoint twice triggers a special function key event.



The available commands are::



                cat /sys/devices/platform/thinkpad_acpi/doubletap_enable

                echo 1 | sudo tee /sys/devices/platform/thinkpad_acpi/doubletap_enable

                echo 0 | sudo tee /sys/devices/platform/thinkpad_acpi/doubletap_enable



Values:



	* 1 - doubletap events are processed (default)

	* 0 - doubletap events are filtered out (ignored)



	This setting can also be toggled via the Fn+doubletap hotkey.



Auxmac

------

Documentation/admin-guide/laptops/uniwill-laptop.rst

+12 −0
Original line number Diff line number Diff line
@@ -50,6 +50,10 @@ between 1 and 100 percent are supported. 
Additionally the driver signals the presence of battery charging issues through the standard

``health`` power supply sysfs attribute.



It also lets you set whether a USB-C power source should prioritise charging the battery or

delivering immediate power to the cpu. See Documentation/ABI/testing/sysfs-driver-uniwill-laptop for

details.



Lightbar

--------
@@ -58,3 +62,11 @@ LED class device. The default name of this LED class device is ``uniwill:multico 


See Documentation/ABI/testing/sysfs-driver-uniwill-laptop for details on how to control the various

animation modes of the lightbar.



Configurable TGP

----------------



The ``uniwill-laptop`` driver allows to set the configurable TGP for devices with NVIDIA GPUs that

allow it.



See Documentation/ABI/testing/sysfs-driver-uniwill-laptop for details.

Documentation/wmi/devices/bitland-mifs-wmi.rst

0 → 100644
+207 −0
Original line number Diff line number Diff line 
.. SPDX-License-Identifier: GPL-2.0-or-later



========================================

Bitland MIFS driver (bitland-mifs-wmi)

========================================



Introduction

============





EC WMI interface description

============================



The EC WMI interface description can be decoded from the embedded binary MOF (bmof)

data using the `bmfdec <https://github.com/pali/bmfdec>`_ utility:



::



  class WMIEvent : __ExtrinsicEvent {

  };



  [WMI, Dynamic, Provider("WmiProv"), Locale("MS\\0x40A"), Description("Root WMI HID_EVENT20"), guid("{46c93e13-ee9b-4262-8488-563bca757fef}")]

  class HID_EVENT20 : WmiEvent {

    [key, read] string InstanceName;

    [read] boolean Active;

    [WmiDataId(1), read, write, Description("Package Data")] uint8 EventDetail[8];

  };



  [WMI, Dynamic, Provider("WmiProv"), Locale("MS\\0x40A"), Description("Root WMI HID_EVENT21"), guid("{fa78e245-2c0f-4ca1-91cf-15f34e474850}")]

  class HID_EVENT21 : WmiEvent {

    [key, read] string InstanceName;

    [read] boolean Active;

    [WmiDataId(1), read, write, Description("Package Data")] uint8 EventDetail[8];

  };



  [WMI, Dynamic, Provider("WmiProv"), Locale("MS\\0x40A"), Description("Root WMI HID_EVENT22"), guid("{1dceaf0a-4d63-44bb-bd0c-0d6281bfddc5}")]

  class HID_EVENT22 : WmiEvent {

    [key, read] string InstanceName;

    [read] boolean Active;

    [WmiDataId(1), read, write, Description("Package Data")] uint8 EventDetail[8];

  };



  [WMI, Dynamic, Provider("WmiProv"), Locale("MS\\0x40A"), Description("Root WMI HID_EVENT23"), guid("{3f9e3c26-b077-4f86-91f5-37ff64d8c7ed}")]

  class HID_EVENT23 : WmiEvent {

    [key, read] string InstanceName;

    [read] boolean Active;

    [WmiDataId(1), read, write, Description("Package Data")] uint8 EventDetail[8];

  };



  [WMI, Dynamic, provider("WmiProv"), Locale("MS\\0x409"), Description("Class used to operate firmware interface"), guid("{b60bfb48-3e5b-49e4-a0e9-8cffe1b3434b}")]

  class MICommonInterface {

    [key, read] string InstanceName;

    [read] boolean Active;



    [WmiMethodId(1), Implemented, read, write, Description("Method used to support system functions.")] void MiInterface([in, Description("WMI Interface")] uint8 InData[32], [out] uint8 OutData[30], [out] uint16 Reserved);

  };



Reverse-Engineering the EC WMI interface

========================================



The OEM software can be download from `this link <https://iknow.lenovo.com.cn/detail/429447>`_



Nothing is obfuscated, In this case, `ILSpy <https://github.com/icsharpcode/ILSpy>`_ could be helpful.



WMI Methods (MICommonInterface)

========================================



The ``MICommonInterface`` class (GUID: ``{b60bfb48-3e5b-49e4-a0e9-8cffe1b3434b}``)

is the primary control interface. It uses a 32-byte buffer for both input

(``InData``) and output (``OutData``).



Method Structure

----------------



The data packet follows a standardized format:



+----------+------------------------------------------------------------------+

| Byte     | Description                                                      |

+==========+==================================================================+

| 1        | Method Type: Get (0xFA / 250) or Set (0xFB / 251)                |

+----------+------------------------------------------------------------------+

| 3        | Command ID (Method Name)                                         |

+----------+------------------------------------------------------------------+

| 4 - 31   | Arguments (for Set) or Return Data (for Get)                     |

+----------+------------------------------------------------------------------+





Command IDs

-----------



The following Command IDs are used in the third byte of the buffer:



+----------+-----------------------+------------------------------------------+

| ID       | Name                  | Values / Description                     |

+==========+=======================+==========================================+

| 8        | SystemPerMode         | 0: Balance, 1: Performance, 2: Quiet,    |

|          |                       | 3: Full-speed                            |

+----------+-----------------------+------------------------------------------+

| 9        | GPUMode               | 0: Hybrid, 1: Discrete, 2: UMA           |

+----------+-----------------------+------------------------------------------+

| 10       | KeyboardType          | 0: White, 1: Single RGB, 2: Zone RGB     |

+----------+-----------------------+------------------------------------------+

| 11       | FnLock                | 0: Off, 1: On                            |

+----------+-----------------------+------------------------------------------+

| 12       | TPLock                | 0: Unlock, 1: Lock (Touchpad)            |

+----------+-----------------------+------------------------------------------+

| 13       | CPUGPUSYSFanSpeed     | Returns 12 bytes of fan data:            |

|          |                       | Bytes 4-5: CPU Fan RPM (Little Endian)   |

|          |                       | Bytes 6-7: GPU Fan RPM (Little Endian)   |

|          |                       | Bytes 10-11: SYS Fan RPM (Little Endian) |

+----------+-----------------------+------------------------------------------+

| 16       | RGBKeyboardMode       | 0: Off, 1: Auto Cyclic, 2: Fixed,        |

|          |                       | 3: Custom                                |

+----------+-----------------------+------------------------------------------+

| 17       | RGBKeyboardColor      | Bytes 4, 5, 6: Red, Green, Blue values   |

+----------+-----------------------+------------------------------------------+

| 18       | RGBKeyboardBrightness | 0-10: Brightness Levels, 128: Auto       |

+----------+-----------------------+------------------------------------------+

| 19       | SystemAcType          | 1: Type-C, 2: Circular Hole (DC)         |

+----------+-----------------------+------------------------------------------+

| 20       | MaxFanSpeedSwitch     | Byte 4: Fan Type (0: CPU/GPU, 1: SYS)    |

|          |                       | Byte 5: State (0: Off, 1: On)            |

+----------+-----------------------+------------------------------------------+

| 21       | MaxFanSpeed           | Sets manual fan speed duty cycle         |

+----------+-----------------------+------------------------------------------+

| 22       | CPUThermometer        | Returns CPU Temperature                  |

+----------+-----------------------+------------------------------------------+



WMI Events (HID_EVENT20)

========================



The driver listens for events from the ``HID_EVENT20`` class

(GUID: ``{46c93e13-ee9b-4262-8488-563bca757fef}``). These events are triggered

by hotkeys or system state changes (e.g., plugging in AC power).



Event Structure

---------------



The event data is provided in an 8-byte array (``EventDetail``):



+----------+------------------------------------------------------------------+

| Byte     | Description                                                      |

+==========+==================================================================+

| 0        | Event Type (Always 0x01 for HotKey/Notification)                 |

+----------+------------------------------------------------------------------+

| 1        | Event ID (Corresponds to the Command IDs above)                  |

+----------+------------------------------------------------------------------+

| 2        | Value (The new state or value of the feature)                    |

+----------+------------------------------------------------------------------+



Common Event IDs:

-----------------



Note: reserved event ids are not listed there



+----------+------------------------------------------------------------------+

| Event Id | Description                                                      |

+==========+==================================================================+

| 4        | AirPlane mode change                                             |

+----------+------------------------------------------------------------------+

| 5        | Keyboard brightness change                                       |

+----------+------------------------------------------------------------------+

| 6        | Touchpad state (enabled/disabled) change                         |

+----------+------------------------------------------------------------------+

| 7        | FnLock state (enabled/disabled) change                           |

+----------+------------------------------------------------------------------+

| 8        | Keyboard mode change                                             |

+----------+------------------------------------------------------------------+

| 9        | CapsLock state change                                            |

+----------+------------------------------------------------------------------+

| 13       | NumLock state change                                             |

+----------+------------------------------------------------------------------+

| 14       | ScrollLock state change                                          |

+----------+------------------------------------------------------------------+

| 15       | Performance plan change                                          |

+----------+------------------------------------------------------------------+

| 25       | Display refresh rate change                                      |

+----------+------------------------------------------------------------------+

| 33       | Super key lock state (enabled/disabled) change                   |

+----------+------------------------------------------------------------------+

| 35       | Open control center key                                          |

+----------+------------------------------------------------------------------+



Implementation Details

======================



Performance Modes

-----------------

Changing the performance mode via Command ID 0x08 (SystemPerMode) affects the

power limits (PL1/PL2) and fan curves managed by the Embedded Controller (EC).

Note that the "Full-speed" and "Performance" mode (1, 3) is typically only

available when the system is connected to a DC power source (not USB-C/PD).



In the driver implementation, switch to performance/full-speed mode without

DC power connected will throw the EOPNOTSUPP error.



Graphics Switching

------------------

The ``GPUMode`` (0x09) allows switching between Hybrid (Muxless) and Discrete

(Muxed) graphics. Changing this value usually requires a system reboot to

take effect in the BIOS/Firmware.



Fan Control

-----------

The system supports both automatic EC control and manual overrides. Command ID

0x14 (``MaxFanSpeedSwitch``) is used to toggle manual control, while ID 0x15

sets the actual PWM duty cycle.

Documentation/wmi/driver-development-guide.rst

+7 −4
Original line number Diff line number Diff line
@@ -71,7 +71,7 @@ to matching WMI devices using a struct wmi_device_id table: 
        .remove = foo_remove,         /* optional, devres is preferred */

        .shutdown = foo_shutdown,     /* optional, called during shutdown */

        .notify_new = foo_notify,     /* optional, for event handling */

        .no_notify_data = true,       /* optional, enables events containing no additional data */

        .min_event_size = X,          /* optional, simplifies event payload size verification */

        .no_singleton = true,         /* required for new WMI drivers */

  };

  module_wmi_driver(foo_driver);
@@ -106,7 +106,8 @@ WMI method drivers 


WMI drivers can call WMI device methods using wmidev_invoke_method(). For each WMI method

invocation the WMI driver needs to provide the instance number and the method ID, as well as

a buffer with the method arguments and optionally a buffer for the results.

a buffer with the method arguments and optionally a buffer for the results. When calling WMI

methods that do not return any values, wmidev_invoke_procedure() should be used instead.



The layout of said buffers is device-specific and described by the Binary MOF data associated

with a given WMI device. Said Binary MOF data also describes the method ID of a given WMI method
@@ -141,8 +142,10 @@ right before and after calling its remove() or shutdown() callback. 
However WMI driver developers should be aware that multiple WMI events can be received concurrently,

so any locking (if necessary) needs to be provided by the WMI driver itself.



In order to be able to receive WMI events containing no additional event data,

the ``no_notify_data`` flag inside struct wmi_driver should be set to ``true``.

The WMI driver can furthermore instruct the WMI driver core to automatically reject WMI events

that contain a undersized event payload by populating the ``min_event_size`` field inside

struct wmi_driver. Setting this field to 0 will thus enable the WMI driver to receive WMI events

without any event payload.



Take a look at drivers/platform/x86/xiaomi-wmi.c for an example WMI event driver.