| /linux-6.12.1/sound/aoa/fabrics/ |
| D | layout.c | 645 if (gpio->methods && gpio->methods->get_##n) \
647 gpio->methods->get_##n(gpio); \
654 if (gpio->methods && gpio->methods->set_##n) \
655 gpio->methods->set_##n(gpio, \
737 v = ldev->gpio.methods->get_detect(&ldev->gpio, in detected_get()
741 v = ldev->gpio.methods->get_detect(&ldev->gpio, in detected_get()
861 v = ldev->gpio.methods->get_detect(&ldev->gpio, AOA_NOTIFY_HEADPHONE); in layout_notify()
865 ldev->gpio.methods->set_speakers(&ldev->gpio, !v); in layout_notify()
866 ldev->gpio.methods->set_headphone(&ldev->gpio, v); in layout_notify()
867 ldev->gpio.methods->set_lineout(&ldev->gpio, 0); in layout_notify()
[all …]
|
| /linux-6.12.1/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-6.12.1/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-6.12.1/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;
|
| D | gpio-pmf.c | 235 static struct gpio_methods methods = { variable
251 struct gpio_methods *pmf_gpio_methods = &methods;
|
| /linux-6.12.1/include/rdma/ |
| 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-6.12.1/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-6.12.1/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-6.12.1/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
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-6.12.1/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-6.12.1/sound/aoa/codecs/ |
| D | onyx.c | 779 onyx->codec.gpio->methods->all_amps_off(onyx->codec.gpio); in onyx_switch_clock()
782 onyx->codec.gpio->methods->all_amps_restore(onyx->codec.gpio); in onyx_switch_clock()
821 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 0); in onyx_resume()
823 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 1); in onyx_resume()
825 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 0); in onyx_resume()
869 if (!onyx->codec.gpio || !onyx->codec.gpio->methods) { in onyx_init_codec()
874 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 0); in onyx_init_codec()
876 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 1); in onyx_init_codec()
878 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 0); in onyx_init_codec()
|
| D | tas.c | 674 tas->codec.gpio->methods->all_amps_off(tas->codec.gpio); in tas_reset_init()
676 tas->codec.gpio->methods->set_hw_reset(tas->codec.gpio, 0); in tas_reset_init()
678 tas->codec.gpio->methods->set_hw_reset(tas->codec.gpio, 1); in tas_reset_init()
680 tas->codec.gpio->methods->set_hw_reset(tas->codec.gpio, 0); in tas_reset_init()
682 tas->codec.gpio->methods->all_amps_restore(tas->codec.gpio); in tas_reset_init()
720 tas->codec.gpio->methods->all_amps_off(tas->codec.gpio); in tas_switch_clock()
730 tas->codec.gpio->methods->all_amps_restore(tas->codec.gpio); in tas_switch_clock()
800 if (!tas->codec.gpio || !tas->codec.gpio->methods) { in tas_init_codec()
|
| /linux-6.12.1/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
|
| 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
184 that many methods just copy a part of the embedded controller memory into the output buffer.
186 This means that the remaining WMI methods can be reverse-engineered by looking which part of
188 debugfs interface for directly executing WMI methods. Additionally, any safety checks regarding
|
| /linux-6.12.1/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-6.12.1/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-6.12.1/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
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
304 driver-specific methods stored in ``dev->driver->pm``, but they don't have to do
[all …]
|
| /linux-6.12.1/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-6.12.1/drivers/net/wireless/purelifi/plfxlc/ |
| D | Kconfig | 10 methods including Open, WPA, WPA2-Personal and
|
| /linux-6.12.1/Documentation/filesystems/ |
| D | sysfs.rst | 58 the filesystem. sysfs forwards file I/O operations to methods defined
156 show and store methods of the attribute owners::
170 calls the associated methods.
198 To read or write attributes, show() or store() methods must be
243 - show() methods should return the number of bytes printed into the
255 - The object passed to the methods will be pinned in memory via sysfs
|
| /linux-6.12.1/Documentation/firmware-guide/acpi/ |
| 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-6.12.1/sound/aoa/ |
| D | aoa-gpio.h | 73 struct gpio_methods *methods; member
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | video-output.rst | 7 can be used to hook platform specific methods to enable/disable video output
|
| /linux-6.12.1/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`,
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-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-devices-power_state | 7 management methods.
|