| /Linux-v6.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 …]
|
| /Linux-v6.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 …]
|
| /Linux-v6.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) \
|
| /Linux-v6.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 …]
|
| D | evregion.c | 39 * DESCRIPTION: Execute _REG methods for all Operation Regions that have
56 /* Run the _REG methods for op_regions in each default address space */ in acpi_ev_initialize_op_regions()
61 * default, the _REG methods will have already been run (when the in acpi_ev_initialize_op_regions()
186 * potentially execute control methods (for example, the _REG method in acpi_ev_address_space_dispatch()
680 * DESCRIPTION: Run all _REG methods for the input Space ID;
711 " Running _REG methods for SpaceId %s\n", in acpi_ev_execute_reg_methods()
715 * Run all _REG methods for all Operation Regions for this space ID. This in acpi_ev_execute_reg_methods()
717 * regions and _REG methods. (i.e. handlers must be installed for all in acpi_ev_execute_reg_methods()
718 * regions of this Space ID before we can run any _REG methods) in acpi_ev_execute_reg_methods()
725 * Special case for EC and GPIO: handle "orphan" _REG methods with in acpi_ev_execute_reg_methods()
[all …]
|
| D | evxfregn.c | 30 * Run_reg - Run _REG methods for this address space?
37 * been called. This is because any _REG methods associated with the Space ID
38 * are executed here, and these methods can only be safely executed after
85 /* Run all _REG methods for this address space */ in acpi_install_address_space_handler_internal()
297 /* Run all _REG methods for this address space */ in ACPI_EXPORT_SYMBOL()
|
| /Linux-v6.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
|
| /Linux-v6.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()
|
| /Linux-v6.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 …]
|
| /Linux-v6.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.
|
| /Linux-v6.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.
|
| /Linux-v6.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.
|
| D | rwlock.h | 9 * rwlock related methods
48 * Define the various rw_lock methods. Note we define these
50 * methods are defined as nops in the case they are not required.
|
| /Linux-v6.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;
|
| /Linux-v6.6/Documentation/networking/ |
| D | sfp-phylink.rst | 137 6. Add/replace ksettings get/set methods with:
193 :c:func:`of_phy_connect` becomes three methods: :c:func:`mac_link_up`,
211 methods such as 1000base-X and SGMII.
229 For further information on these methods, please see the inline
275 :c:func:`mac_link_down` methods.
279 :c:type:`struct phylink_mac_ops <phylink_mac_ops>` methods are called
|
| /Linux-v6.6/Documentation/power/ |
| D | basic-pm-debugging.rst | 60 global control methods [1]_
64 global control methods [1]_ and the disabling of nonboot CPUs
68 control methods\ [1]_, the disabling of nonboot CPUs and suspending
73 the platform global control methods are only available on ACPI systems
90 invoke the global control methods (eg. ACPI global control methods) used to
93 methods used to cancel hibernation etc.
|
| /Linux-v6.6/Documentation/sound/soc/ |
| D | jack.rst | 34 machine driver and updated by jack detection methods.
49 Jack detection methods
59 provided by the snd_soc_jack_add_gpio() function. Other methods are
|
| /Linux-v6.6/drivers/video/fbdev/riva/ |
| D | riva_hw.h | 357 struct { /* start aliased methods in array 0400- */
360 } Lin[16]; /* end of aliased methods in array -047f*/
361 struct { /* start aliased methods in array 0480- */
366 } Lin32[8]; /* end of aliased methods in array -04ff*/
368 struct { /* start aliased methods in array 0580- */
371 } PolyLin32[16]; /* end of aliased methods in array -05ff*/
372 struct { /* start aliased methods in array 0600- */
375 } ColorPolyLin[16]; /* end of aliased methods in array -067f*/
|
| /Linux-v6.6/Documentation/wmi/devices/ |
| D | dell-wmi-ddv.rst | 81 WMI methods. Other WMI methods may ignore this argument or interpret it
89 The format of the output should be thoroughly checked, since many methods can
92 The data format of many battery-related methods seems to be based on the
93 `Smart Battery Data Specification`, so unknown battery-related methods are
278 flow with other ACPI methods (_BIX or _BIF for battery related methods
281 related methods (sometimes overwriting static ACPI data fields can be used
|
| /Linux-v6.6/arch/arm/include/asm/ |
| D | spectre.h | 29 void spectre_v2_update_state(unsigned int state, unsigned int methods);
32 unsigned int methods) in spectre_v2_update_state() argument
|
| /Linux-v6.6/Documentation/driver-api/tty/ |
| D | tty_ldisc.rst | 52 Line discipline methods can call the methods of the underlying hardware driver.
58 Line discipline methods have access to :c:member:`tty_struct.flags` field. See
|
| /Linux-v6.6/drivers/net/wireless/quantenna/qtnfmac/ |
| D | bus.h | 36 /* mgmt methods */
40 /* control path methods */
43 /* data xfer methods */
|
| /Linux-v6.6/tools/perf/util/libunwind/ |
| D | arm64.c | 11 * Finally, the arch specific unwind methods are exported which will
31 * unwind methods.
|
