1*618ba6abSArmin WolfWhat: /sys/bus/wmi/devices/.../driver_override 2*618ba6abSArmin WolfDate: February 2024 3*618ba6abSArmin WolfContact: Armin Wolf <[email protected]> 4*618ba6abSArmin WolfDescription: 5*618ba6abSArmin Wolf This file allows the driver for a device to be specified which 6*618ba6abSArmin Wolf will override standard ID table matching. 7*618ba6abSArmin Wolf When specified, only a driver with a name matching the value 8*618ba6abSArmin Wolf written to driver_override will have an opportunity to bind 9*618ba6abSArmin Wolf to the device. 10*618ba6abSArmin Wolf The override is specified by writing a string to the 11*618ba6abSArmin Wolf driver_override file (echo wmi-event-dummy > driver_override). 12*618ba6abSArmin Wolf The override may be cleared with an empty string (echo > \ 13*618ba6abSArmin Wolf driver_override) which returns the device to standard matching 14*618ba6abSArmin Wolf rules binding. 15*618ba6abSArmin Wolf Writing to driver_override does not automatically unbind the 16*618ba6abSArmin Wolf device from its current driver or make any attempt to automatically 17*618ba6abSArmin Wolf load the specified driver. If no driver with a matching name is 18*618ba6abSArmin Wolf currently loaded in the kernel, the device will not bind to any 19*618ba6abSArmin Wolf driver. 20*618ba6abSArmin Wolf This also allows devices to opt-out of driver binding using a 21*618ba6abSArmin Wolf driver_override name such as "none". Only a single driver may be 22*618ba6abSArmin Wolf specified in the override, there is no support for parsing delimiters. 23*618ba6abSArmin Wolf 24*618ba6abSArmin WolfWhat: /sys/bus/wmi/devices/.../modalias 25*618ba6abSArmin WolfDate: November 20:15 26*618ba6abSArmin WolfContact: Andy Lutomirski <[email protected]> 27*618ba6abSArmin WolfDescription: 28*618ba6abSArmin Wolf This file contains the MODALIAS value emitted by uevent for a 29*618ba6abSArmin Wolf given WMI device. 30*618ba6abSArmin Wolf 31*618ba6abSArmin Wolf Format: wmi:XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX. 32*618ba6abSArmin Wolf 33*618ba6abSArmin WolfWhat: /sys/bus/wmi/devices/.../guid 34*618ba6abSArmin WolfDate: November 2015 35*618ba6abSArmin WolfContact: Andy Lutomirski <[email protected]> 36*618ba6abSArmin WolfDescription: 37*618ba6abSArmin Wolf This file contains the GUID used to match WMI devices to 38*618ba6abSArmin Wolf compatible WMI drivers. This GUID is not necessarily unique 39*618ba6abSArmin Wolf inside a given machine, it is solely used to identify the 40*618ba6abSArmin Wolf interface exposed by a given WMI device. 41*618ba6abSArmin Wolf 42*618ba6abSArmin WolfWhat: /sys/bus/wmi/devices/.../object_id 43*618ba6abSArmin WolfDate: November 2015 44*618ba6abSArmin WolfContact: Andy Lutomirski <[email protected]> 45*618ba6abSArmin WolfDescription: 46*618ba6abSArmin Wolf This file contains the WMI object ID used internally to construct 47*618ba6abSArmin Wolf the ACPI method names used by non-event WMI devices. It contains 48*618ba6abSArmin Wolf two ASCII letters. 49*618ba6abSArmin Wolf 50*618ba6abSArmin WolfWhat: /sys/bus/wmi/devices/.../notify_id 51*618ba6abSArmin WolfDate: November 2015 52*618ba6abSArmin WolfContact: Andy Lutomirski <[email protected]> 53*618ba6abSArmin WolfDescription: 54*618ba6abSArmin Wolf This file contains the WMI notify ID used internally to map ACPI 55*618ba6abSArmin Wolf events to WMI event devices. It contains two ASCII letters. 56*618ba6abSArmin Wolf 57*618ba6abSArmin WolfWhat: /sys/bus/wmi/devices/.../instance_count 58*618ba6abSArmin WolfDate: November 2015 59*618ba6abSArmin WolfContact: Andy Lutomirski <[email protected]> 60*618ba6abSArmin WolfDescription: 61*618ba6abSArmin Wolf This file contains the number of WMI object instances being 62*618ba6abSArmin Wolf present on a given WMI device. It contains a non-negative 63*618ba6abSArmin Wolf number. 64*618ba6abSArmin Wolf 65*618ba6abSArmin WolfWhat: /sys/bus/wmi/devices/.../expensive 66*618ba6abSArmin WolfDate: November 2015 67*618ba6abSArmin WolfContact: Andy Lutomirski <[email protected]> 68*618ba6abSArmin WolfDescription: 69*618ba6abSArmin Wolf This file contains a boolean flag signaling if interacting with 70*618ba6abSArmin Wolf the given WMI device will consume significant CPU resources. 71*618ba6abSArmin Wolf The WMI driver core will take care of enabling/disabling such 72*618ba6abSArmin Wolf WMI devices. 73*618ba6abSArmin Wolf 74*618ba6abSArmin WolfWhat: /sys/bus/wmi/devices/.../setable 75*618ba6abSArmin WolfDate: May 2017 76*618ba6abSArmin WolfContact: Darren Hart (VMware) <[email protected]> 77*618ba6abSArmin WolfDescription: 78*618ba6abSArmin Wolf This file contains a boolean flags signaling the data block 79*618ba6abSArmin Wolf aassociated with the given WMI device is writable. If the 80*618ba6abSArmin Wolf given WMI device is not associated with a data block, then 81*618ba6abSArmin Wolf this file will not exist. 82