Lines Matching full:drivers

7 The WMI subsystem provides a rich driver API for implementing WMI drivers,
10 to be a successor to the original LWN article [1]_ which deals with WMI drivers
75         .no_singleton = true,         /* required for new WMI drivers */
90 or kexec. Most WMI drivers need no special shutdown handling and can thus omit this callback.
92 Please note that new WMI drivers are required to be able to be instantiated multiple times,
97 Because of this, WMI drivers should use the state container design pattern as described in
104 WMI method drivers
107 WMI drivers can call WMI device methods using wmidev_evaluate_method(), the
116 Take a look at drivers/platform/x86/inspur_platform_profile.c for an example WMI method driver.
118 WMI data block drivers
121 WMI drivers can query WMI device data blocks using wmidev_block_query(), the
127 Take a look at drivers/platform/x86/intel/wmi/sbl-fw-update.c for an example
130 WMI event drivers
133 WMI drivers can receive WMI events via the notify() callback inside the struct wmi_driver.
148 Take a look at drivers/platform/x86/xiaomi-wmi.c for an example WMI event driver.
154 of a single physical device. This can make developing WMI drivers complicated, as those drivers
158 method device upon receiving an WMI event. In such a case, two WMI drivers should be developed,
171 When developing WMI drivers, there are a couple of things which should be avoided:
175 - WMI drivers which cannot be instantiated multiple times.
177 Many older WMI drivers violate one or more points from this list. The reason for
179 so there is a lot of legacy cruft inside older WMI drivers.
181 New WMI drivers are also required to conform to the linux kernel coding style as specified in