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