| /linux/Documentation/wmi/ |
| H A 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/Documentation/wmi/devices/ |
| H A D | uniwill-laptop.rst | 23 Description("Class used to operate methods on a ULong"),
141 by calling ACPI control methods. The ``uniwill-laptop`` driver uses this device to communicate
142 with the EC because the ACPI control methods are faster than the WMI methods described above.
144 ACPI control methods used for reading registers take a single ACPI integer containing the address
146 control methods used for writing registers however take two ACPI integers, with the additional
147 ACPI integer containing the data to be written into the register. Such ACPI control methods return
155 control methods are unused because they provide no benefit when compared to the native memory
162 (read) and ``ECRW`` (write) ACPI control methods, with the maximum register address being ``0xFFF``.
163 The OEM software waits 6 ms after calling one of those ACPI control methods, likely to avoid
170 ``PCWD`` (write) ACPI control methods. The exact address format is unknown, and poking random PCI
[all …]
|
| H A 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
300 flow with other ACPI methods (_BIX or _BIF for battery related methods
303 related methods (sometimes overwriting static ACPI data fields can be used
|
| H A D | msi-wmi-platform.rst | 37 Description("Class used to operate methods on a package"),
132 happen when a invalid byte field is ultimately accessed), all methods require a 32 byte input
188 that many methods just copy a part of the embedded controller memory into the output buffer.
190 This means that the remaining WMI methods can be reverse-engineered by looking which part of
192 debugfs interface for directly executing WMI methods. Additionally, any safety checks regarding
|
| H A D | alienware-wmi.rst | 18 exposes Thermal_Information and Thermal_Control methods through the Platform
78 between methods. Usually, the first byte corresponds to a specific *operation*
241 The control of two GPIO pins of this MCU is exposed as WMI methods for debugging
263 Some GPIO control methods break the usual argument structure and take a
286 Due to how WMI methods are implemented on the firmware level, this method
|
| /linux/include/rdma/ |
| H A D | uverbs_named_ioctl.h | 56 .methods = &UVERBS_OBJECT_METHODS(_object_id) \
70 .methods = &UVERBS_OBJECT_METHODS(_object_id) \
81 .methods = &UVERBS_OBJECT_METHODS(_object_id) \
|
| /linux/arch/arm/include/asm/ |
| H A 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/fs/debugfs/ |
| H A D | file.c | 80 unsigned int methods = 0; in __debugfs_file_get() local
93 methods |= HAS_LSEEK; in __debugfs_file_get()
95 methods |= HAS_READ; in __debugfs_file_get()
97 methods |= HAS_WRITE; in __debugfs_file_get()
103 methods |= HAS_LSEEK; in __debugfs_file_get()
105 methods |= HAS_READ; in __debugfs_file_get()
107 methods |= HAS_WRITE; in __debugfs_file_get()
109 methods |= HAS_IOCTL; in __debugfs_file_get()
111 methods |= HAS_POLL; in __debugfs_file_get()
114 fsd->methods = methods; in __debugfs_file_get()
[all …]
|
| H A D | internal.h | 46 unsigned int methods; member
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A 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/Documentation/admin-guide/laptops/ |
| H A 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
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/Documentation/infiniband/ |
| H A 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/Documentation/driver-api/tty/ |
| H A 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/Documentation/sound/soc/ |
| H A 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/Documentation/power/ |
| H A 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/Documentation/firmware-guide/acpi/ |
| H A D | DSD-properties-rules.rst | 70 possibly leading to a conflict with AML methods in the ACPI namespace. In
72 manipulate hardware normally controlled by ACPI methods related to power
74 resource objects), or by ACPI device disabling/enabling methods, like _DIS and
|
| /linux/drivers/net/wireless/purelifi/plfxlc/ |
| H A D | Kconfig | 10 methods including Open, WPA, WPA2-Personal and
|
| /linux/Documentation/networking/ |
| H A 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`,
213 methods such as 1000base-X and SGMII.
231 For further information on these methods, please see the inline
396 :c:func:`mac_link_down` methods.
400 :c:type:`struct phylink_mac_ops <phylink_mac_ops>` methods are called
|
| /linux/sound/aoa/ |
| H A D | aoa-gpio.h | 73 struct gpio_methods *methods; member
|
| /linux/Documentation/admin-guide/ |
| H A D | video-output.rst | 7 can be used to hook platform specific methods to enable/disable video output
|
| /linux/Documentation/i2c/ |
| H A D | fault-codes.rst | 38 Also, codes returned by adapter probe methods follow rules which are
81 Returned by driver probe() methods. This is a bit more
98 Returned by driver probe() methods to indicate that they
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-power_state | 7 management methods.
|
| H A D | sysfs-devices-real_power_state | 7 power management methods and use ACPI power resources for power
|
| /linux/Documentation/arch/arm64/ |
| H A D | arm-acpi.rst | 381 can be controlled through the optional ACPI methods _PS0, _PS1, _PS2, and _PS3;
391 methods. They are then tied back to D-states for a particular device
396 The kernel ACPI code will also assume that the _PSx methods follow the normal
397 ACPI rules for such methods:
411 Such code in _PSx methods will of course be very platform specific. But,
430 methods to be expected). The only exceptions to this are CPU clocks where
431 CPPC provides a much richer interface than ACPI methods. If the clocks
435 they could do so by providing ACPI methods that could be invoked by Linux
437 such methods, even if they are provided. Such methods are not currently
|
| /linux/drivers/soc/loongson/ |
| H A D | Kconfig | 27 Disk), ACPI S5 (Soft Shutdown) and supports multiple wake-up methods
|