| /kernel/linux/linux-6.6/Documentation/wmi/ |
| D | acpi-interface.rst | 16 of ``PNP0C14``. These devices will contain a set of ACPI buffers and methods
17 used for mapping and execution of WMI methods and/or queries. If there exist
40 - 0x2: Data block contains WMI methods.
49 WQxx ACPI methods
52 If a data block does not contain WMI methods, then its content can be retrieved
58 WSxx ACPI methods
61 Similar to the ``WQxx`` ACPI methods, except that it is optional and takes an
65 WMxx ACPI methods
68 Used for executing WMI methods associated with a data block. The last two
70 containing the WMI methods. Their first parameter is a integer describing the
[all …]
|
| /kernel/linux/linux-5.10/sound/aoa/fabrics/ |
| D | layout.c | 644 if (gpio->methods && gpio->methods->get_##n) \
646 gpio->methods->get_##n(gpio); \
653 if (gpio->methods && gpio->methods->set_##n) \
654 gpio->methods->set_##n(gpio, \
736 v = ldev->gpio.methods->get_detect(&ldev->gpio, in detected_get()
740 v = ldev->gpio.methods->get_detect(&ldev->gpio, in detected_get()
860 v = ldev->gpio.methods->get_detect(&ldev->gpio, AOA_NOTIFY_HEADPHONE); in layout_notify()
864 ldev->gpio.methods->set_speakers(&ldev->gpio, !v); in layout_notify()
865 ldev->gpio.methods->set_headphone(&ldev->gpio, v); in layout_notify()
866 ldev->gpio.methods->set_lineout(&ldev->gpio, 0); in layout_notify()
[all …]
|
| /kernel/linux/linux-6.6/sound/aoa/fabrics/ |
| D | layout.c | 644 if (gpio->methods && gpio->methods->get_##n) \
646 gpio->methods->get_##n(gpio); \
653 if (gpio->methods && gpio->methods->set_##n) \
654 gpio->methods->set_##n(gpio, \
736 v = ldev->gpio.methods->get_detect(&ldev->gpio, in detected_get()
740 v = ldev->gpio.methods->get_detect(&ldev->gpio, in detected_get()
860 v = ldev->gpio.methods->get_detect(&ldev->gpio, AOA_NOTIFY_HEADPHONE); in layout_notify()
864 ldev->gpio.methods->set_speakers(&ldev->gpio, !v); in layout_notify()
865 ldev->gpio.methods->set_headphone(&ldev->gpio, v); in layout_notify()
866 ldev->gpio.methods->set_lineout(&ldev->gpio, 0); in layout_notify()
[all …]
|
| /kernel/linux/linux-5.10/include/rdma/ |
| D | uverbs_named_ioctl.h | 56 .methods = &UVERBS_OBJECT_METHODS(_object_id) \
60 * Declare global methods. These still have a unique object_id because we
61 * identify all uapi methods with a (object,method) tuple. However, they have
70 .methods = &UVERBS_OBJECT_METHODS(_object_id) \
73 /* Used by drivers to declare a complete parsing tree for new methods
81 .methods = &UVERBS_OBJECT_METHODS(_object_id) \
|
| /kernel/linux/linux-6.6/include/rdma/ |
| D | uverbs_named_ioctl.h | 56 .methods = &UVERBS_OBJECT_METHODS(_object_id) \
60 * Declare global methods. These still have a unique object_id because we
61 * identify all uapi methods with a (object,method) tuple. However, they have
70 .methods = &UVERBS_OBJECT_METHODS(_object_id) \
73 /* Used by drivers to declare a complete parsing tree for new methods
81 .methods = &UVERBS_OBJECT_METHODS(_object_id) \
|
| /kernel/linux/linux-6.6/drivers/acpi/acpica/ |
| D | evgpeinit.c | 22 * the entire namespace to execute the _PRW methods and detect all GPEs
26 * actually unnecessary. The host OS must in fact execute all _PRW methods
197 * DESCRIPTION: Check for new GPE methods (_Lxx/_Exx) made available as a
199 * methods have been installed, register the new methods.
211 * Find any _Lxx/_Exx GPE methods that have just been loaded. in acpi_ev_update_gpes()
213 * Any GPEs that correspond to new _Lxx/_Exx methods are immediately in acpi_ev_update_gpes()
248 "While decoding _Lxx/_Exx methods")); in acpi_ev_update_gpes()
286 * If walk_info->execute_by_owner_id is TRUE, we only execute examine GPE methods
376 * and GPE1 methods both appear under \_GPE. in acpi_ev_match_gpe_method()
399 "For GPE 0x%.2X, found both _L%2.2X and _E%2.2X methods", in acpi_ev_match_gpe_method()
|
| D | nsxfname.c | 208 * control methods (Such as in the case of a device.)
211 * _CLS, _ADR, _sx_w, and _sx_d methods.
216 * discovery namespace traversal. Therefore, no complex methods can be
218 * not add any additional methods that could cause problems in this area.
219 * Because of this reason support for the following methods has been removed:
279 * Run the Device _HID, _UID, _CLS, and _CID methods. in acpi_get_object_info()
281 * Note: none of these methods are required, so they may or may in acpi_get_object_info()
283 * to indicate which methods were found and run successfully. in acpi_get_object_info()
339 * Run the _ADR and, sx_w, and _sx_d methods. in acpi_get_object_info()
341 * Notes: none of these methods are required, so they may or may in acpi_get_object_info()
[all …]
|
| D | nsinit.c | 83 "%u Control Methods found\n%u Op Regions found\n", in acpi_ns_initialize_objects()
125 "and executing _INI/_STA methods:\n")); in acpi_ns_initialize_devices()
127 /* Tree analysis: find all subtrees that contain _INI methods */ in acpi_ns_initialize_devices()
184 * Run all _REG methods in acpi_ns_initialize_devices()
186 * Note: Any objects accessed by the _REG methods will be automatically in acpi_ns_initialize_devices()
198 "[Init] Executing _REG OpRegion methods\n")); in acpi_ns_initialize_devices()
230 " Executed %u _INI methods requiring %u _STA executions " in acpi_ns_initialize_devices()
310 * 1) Methods
468 /* We are only looking for methods named _INI */ in acpi_ns_find_ini_methods()
475 * The only _INI methods that we care about are those that are in acpi_ns_find_ini_methods()
[all …]
|
| /kernel/linux/linux-5.10/drivers/acpi/acpica/ |
| D | evgpeinit.c | 22 * the entire namespace to execute the _PRW methods and detect all GPEs
26 * actually unnecessary. The host OS must in fact execute all _PRW methods
197 * DESCRIPTION: Check for new GPE methods (_Lxx/_Exx) made available as a
199 * methods have been installed, register the new methods.
211 * Find any _Lxx/_Exx GPE methods that have just been loaded. in acpi_ev_update_gpes()
213 * Any GPEs that correspond to new _Lxx/_Exx methods are immediately in acpi_ev_update_gpes()
248 "While decoding _Lxx/_Exx methods")); in acpi_ev_update_gpes()
286 * If walk_info->execute_by_owner_id is TRUE, we only execute examine GPE methods
376 * and GPE1 methods both appear under \_GPE. in acpi_ev_match_gpe_method()
399 "For GPE 0x%.2X, found both _L%2.2X and _E%2.2X methods", in acpi_ev_match_gpe_method()
|
| D | nsxfname.c | 208 * control methods (Such as in the case of a device.)
211 * _CLS, _ADR, _sx_w, and _sx_d methods.
216 * discovery namespace traversal. Therefore, no complex methods can be
218 * not add any additional methods that could cause problems in this area.
219 * Because of this reason support for the following methods has been removed:
279 * Run the Device _HID, _UID, _CLS, and _CID methods. in acpi_get_object_info()
281 * Note: none of these methods are required, so they may or may in acpi_get_object_info()
283 * to indicate which methods were found and run successfully. in acpi_get_object_info()
339 * Run the _ADR and, sx_w, and _sx_d methods. in acpi_get_object_info()
341 * Notes: none of these methods are required, so they may or may in acpi_get_object_info()
[all …]
|
| D | nsinit.c | 83 "%u Control Methods found\n%u Op Regions found\n", in acpi_ns_initialize_objects()
125 "and executing _INI/_STA methods:\n")); in acpi_ns_initialize_devices()
127 /* Tree analysis: find all subtrees that contain _INI methods */ in acpi_ns_initialize_devices()
184 * Run all _REG methods in acpi_ns_initialize_devices()
186 * Note: Any objects accessed by the _REG methods will be automatically in acpi_ns_initialize_devices()
198 "[Init] Executing _REG OpRegion methods\n")); in acpi_ns_initialize_devices()
230 " Executed %u _INI methods requiring %u _STA executions " in acpi_ns_initialize_devices()
310 * 1) Methods
468 /* We are only looking for methods named _INI */ in acpi_ns_find_ini_methods()
475 * The only _INI methods that we care about are those that are in acpi_ns_find_ini_methods()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/laptops/ |
| D | sony-laptop.rst | 102 More recent Vaio models expose a consistent set of ACPI methods to
121 In your kernel logs you will find the list of all ACPI methods
129 (3) SN06 and SN07 are used to call into the real methods based on
136 * For old models you can see the GCDP/GCDP methods used to pwer on/off
140 **I HAVE NO IDEA WHAT THOSE METHODS DO.**
142 The sony-laptop driver creates, for some of those methods (the most
145 You can create other entries corresponding to your own laptop methods by
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/laptops/ |
| D | sony-laptop.rst | 102 More recent Vaio models expose a consistent set of ACPI methods to
121 In your kernel logs you will find the list of all ACPI methods
129 (3) SN06 and SN07 are used to call into the real methods based on
136 * For old models you can see the GCDP/GCDP methods used to pwer on/off
140 **I HAVE NO IDEA WHAT THOSE METHODS DO.**
142 The sony-laptop driver creates, for some of those methods (the most
145 You can create other entries corresponding to your own laptop methods by
|
| /kernel/linux/linux-5.10/drivers/i2c/busses/ |
| D | i2c-scmi.c | 35 struct smbus_methods_t *methods; member
164 method = smbus_cmi->methods->mt_sbr; in acpi_smbus_cmi_access()
168 method = smbus_cmi->methods->mt_sbw; in acpi_smbus_cmi_access()
308 if (!strcmp(name, smbus_cmi->methods->mt_info)) { in acpi_smbus_cmi_add_cap()
310 smbus_cmi->methods->mt_info, in acpi_smbus_cmi_add_cap()
314 smbus_cmi->methods->mt_info, status); in acpi_smbus_cmi_add_cap()
337 } else if (!strcmp(name, smbus_cmi->methods->mt_sbr)) in acpi_smbus_cmi_add_cap()
339 else if (!strcmp(name, smbus_cmi->methods->mt_sbw)) in acpi_smbus_cmi_add_cap()
383 smbus_cmi->methods = in acpi_smbus_cmi_add()
|
| /kernel/linux/linux-6.6/drivers/i2c/busses/ |
| D | i2c-scmi.c | 28 const struct smbus_methods_t *methods; member
157 method = smbus_cmi->methods->mt_sbr; in acpi_smbus_cmi_access()
161 method = smbus_cmi->methods->mt_sbw; in acpi_smbus_cmi_access()
301 if (!strcmp(name, smbus_cmi->methods->mt_info)) { in acpi_smbus_cmi_add_cap()
303 smbus_cmi->methods->mt_info, in acpi_smbus_cmi_add_cap()
307 smbus_cmi->methods->mt_info, status); in acpi_smbus_cmi_add_cap()
330 } else if (!strcmp(name, smbus_cmi->methods->mt_sbr)) in acpi_smbus_cmi_add_cap()
332 else if (!strcmp(name, smbus_cmi->methods->mt_sbw)) in acpi_smbus_cmi_add_cap()
367 smbus_cmi->methods = device_get_match_data(dev); in smbus_cmi_probe()
|
| /kernel/linux/linux-5.10/Documentation/driver-api/pm/ |
| D | devices.rst | 42 by implementing various role-specific suspend and resume methods to
69 various role-specific suspend and resume methods, so that the hardware
103 methods included in it will be explained in what follows. For now, it should be
104 sufficient to remember that the last three methods are specific to runtime power
111 sleep power management methods in a limited way. Therefore it is not described
116 Subsystem-Level Methods
119 The core methods to suspend and resume devices reside in
126 bus types) don't provide all power management methods.
128 Bus drivers implement these methods as appropriate for the hardware and the
279 All phases use PM domain, bus, type, class or driver callbacks (that is, methods
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/pm/ |
| D | devices.rst | 42 by implementing various role-specific suspend and resume methods to
69 various role-specific suspend and resume methods, so that the hardware
103 methods included in it will be explained in what follows. For now, it should be
104 sufficient to remember that the last three methods are specific to runtime power
111 sleep power management methods in a limited way. Therefore it is not described
116 Subsystem-Level Methods
119 The core methods to suspend and resume devices reside in
126 bus types) don't provide all power management methods.
128 Bus drivers implement these methods as appropriate for the hardware and the
279 All phases use PM domain, bus, type, class or driver callbacks (that is, methods
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | io.rst | 9 The V4L2 API defines several different methods to read from or write to
18 Other methods must be negotiated. To select the streaming I/O method
39 The following sections describe the various I/O methods in more detail.
|
| /kernel/linux/linux-6.6/Documentation/infiniband/ |
| D | core_locking.rst | 14 all of the methods in struct ib_device may sleep. The exceptions
15 are any methods from the list:
51 All of the methods in struct ib_device exported by a low-level
116 A consumer is permitted to sleep in its add and remove methods.
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | nvram.h | 21 * of these methods. If the NVRAM hardware can be accessed only one byte
24 * .write methods can be used to implement that efficiently.
28 * methods when available and fall back on the .read_byte and .write_byte
29 * methods otherwise.
|
| /kernel/linux/linux-5.10/Documentation/infiniband/ |
| D | core_locking.rst | 14 all of the methods in struct ib_device may sleep. The exceptions
15 are any methods from the list:
51 All of the methods in struct ib_device exported by a low-level
116 A consumer is permitted to sleep in its add and remove methods.
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | nvram.h | 21 * of these methods. If the NVRAM hardware can be accessed only one byte
24 * .write methods can be used to implement that efficiently.
28 * methods when available and fall back on the .read_byte and .write_byte
29 * methods otherwise.
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | io.rst | 9 The V4L2 API defines several different methods to read from or write to
18 Other methods must be negotiated. To select the streaming I/O method
40 The following sections describe the various I/O methods in more detail.
|
| /kernel/linux/linux-5.10/sound/aoa/core/ |
| D | gpio-feature.c | 181 static struct gpio_methods methods; variable
192 if (methods.set_master) in ftr_gpio_all_amps_off()
206 if (methods.set_master) in ftr_gpio_all_amps_restore()
249 methods.set_master = ftr_gpio_set_master; in ftr_gpio_init()
250 methods.get_master = ftr_gpio_get_master; in ftr_gpio_init()
408 static struct gpio_methods methods = { variable
424 struct gpio_methods *ftr_gpio_methods = &methods;
|
| /kernel/linux/linux-6.6/sound/aoa/core/ |
| D | gpio-feature.c | 181 static struct gpio_methods methods; variable
192 if (methods.set_master) in ftr_gpio_all_amps_off()
206 if (methods.set_master) in ftr_gpio_all_amps_restore()
249 methods.set_master = ftr_gpio_set_master; in ftr_gpio_init()
250 methods.get_master = ftr_gpio_get_master; in ftr_gpio_init()
408 static struct gpio_methods methods = { variable
424 struct gpio_methods *ftr_gpio_methods = &methods;
|