Home
last modified time | relevance | path

Searched refs:methods (Results 1 – 25 of 252) sorted by relevance

1234567891011

/linux/sound/aoa/fabrics/
H A Dlayout.c645 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/Documentation/wmi/
H A Dacpi-interface.rst16 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 Duniwill-laptop.rst23 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 Ddell-wmi-ddv.rst81 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 Dmsi-wmi-platform.rst37 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
/linux/drivers/i2c/busses/
H A Di2c-scmi.c28 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/sound/aoa/core/
H A Dgpio-feature.c181 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()
248 methods.set_master = ftr_gpio_set_master; in ftr_gpio_init()
249 methods.get_master = ftr_gpio_get_master; in ftr_gpio_init()
402 static struct gpio_methods methods = { variable
418 struct gpio_methods *ftr_gpio_methods = &methods;
H A Dgpio-pmf.c226 static struct gpio_methods methods = { variable
242 struct gpio_methods *pmf_gpio_methods = &methods;
/linux/include/rdma/
H A Duverbs_named_ioctl.h56 .methods = &UVERBS_OBJECT_METHODS(_object_id) \
70 .methods = &UVERBS_OBJECT_METHODS(_object_id) \
81 .methods = &UVERBS_OBJECT_METHODS(_object_id) \
/linux/fs/debugfs/
H A Dfile.c80 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 Dinternal.h46 unsigned int methods; member
/linux/arch/arm/include/asm/
H A Dspectre.h29 void spectre_v2_update_state(unsigned int state, unsigned int methods);
32 unsigned int methods) in spectre_v2_update_state() argument
/linux/Documentation/userspace-api/media/v4l/
H A Dio.rst9 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 Dsony-laptop.rst102 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/sound/aoa/codecs/
H A Donyx.c750 onyx->codec.gpio->methods->all_amps_off(onyx->codec.gpio); in onyx_switch_clock()
753 onyx->codec.gpio->methods->all_amps_restore(onyx->codec.gpio); in onyx_switch_clock()
785 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 0); in onyx_resume()
787 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 1); in onyx_resume()
789 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 0); in onyx_resume()
829 if (!onyx->codec.gpio || !onyx->codec.gpio->methods) { in onyx_init_codec()
834 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 0); in onyx_init_codec()
836 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 1); in onyx_init_codec()
838 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 0); in onyx_init_codec()
H A Dtas.c642 tas->codec.gpio->methods->all_amps_off(tas->codec.gpio); in tas_reset_init()
644 tas->codec.gpio->methods->set_hw_reset(tas->codec.gpio, 0); in tas_reset_init()
646 tas->codec.gpio->methods->set_hw_reset(tas->codec.gpio, 1); in tas_reset_init()
648 tas->codec.gpio->methods->set_hw_reset(tas->codec.gpio, 0); in tas_reset_init()
650 tas->codec.gpio->methods->all_amps_restore(tas->codec.gpio); in tas_reset_init()
688 tas->codec.gpio->methods->all_amps_off(tas->codec.gpio); in tas_switch_clock()
698 tas->codec.gpio->methods->all_amps_restore(tas->codec.gpio); in tas_switch_clock()
766 if (!tas->codec.gpio || !tas->codec.gpio->methods) { in tas_init_codec()
/linux/Documentation/infiniband/
H A Dcore_locking.rst14 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 Dtty_ldisc.rst52 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 Djack.rst34 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/filesystems/
H A Dsysfs.rst58 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
246 - New implementations of show() methods should only use sysfs_emit() or
255 - The object passed to the methods will be pinned in memory via sysfs
/linux/Documentation/driver-api/pm/
H A Ddevices.rst42 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/Documentation/power/
H A Dbasic-pm-debugging.rst60 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/tools/
H A Dkdoc_parser.rst23 Parser classes and methods
/linux/Documentation/firmware-guide/acpi/
H A DDSD-properties-rules.rst70 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/Documentation/networking/device_drivers/ethernet/huawei/
H A Dhinic3.rst45 hinic3_queue_common.[ch] Common structures and methods for NIC queues
54 hinic3_hwdev.[ch] HW structures and methods abstractions
61 hinic3_nic_dev.h NIC structures and methods abstractions

1234567891011