tjh.dev
+5
-6
Documentation/driver-api/wmi.rst
+5
-6
Documentation/driver-api/wmi.rst
···
7
7
The WMI driver core supports a more modern bus-based interface for interacting
8
8
with WMI devices, and an older GUID-based interface. The latter interface is
9
9
considered to be deprecated, so new WMI drivers should generally avoid it since
10
-
it has some issues with multiple WMI devices and events sharing the same GUIDs
11
-
and/or notification IDs. The modern bus-based interface instead maps each
12
-
WMI device to a :c:type:`struct wmi_device <wmi_device>`, so it supports
13
-
WMI devices sharing GUIDs and/or notification IDs. Drivers can then register
14
-
a :c:type:`struct wmi_driver <wmi_driver>`, which will be bound to compatible
15
-
WMI devices by the driver core.
10
+
it has some issues with multiple WMI devices sharing the same GUID.
11
+
The modern bus-based interface instead maps each WMI device to a
12
+
:c:type:`struct wmi_device <wmi_device>`, so it supports WMI devices sharing the
13
+
same GUID. Drivers can then register a :c:type:`struct wmi_driver <wmi_driver>`
14
+
which will be bound to compatible WMI devices by the driver core.
16
15
17
16
.. kernel-doc:: include/linux/wmi.h
18
17
:internal: