Searched full:talking (Results 1 – 25 of 189) sorted by relevance
12345678
/linux-5.10/drivers/platform/chrome/ |
D | Kconfig | 61 protocol for talking to the EC is defined by the bus driver. 71 If you say Y here, you get support for talking to the ChromeOS 80 If you say Y here, you get support for talking to the ChromeOS EC 93 If you say Y here, you get support for talking to the ChromeOS EC 106 If you say Y here, you get support for talking to the ChromeOS EC 115 If you say Y here, you get support for talking to the ChromeOS EC
|
/linux-5.10/include/uapi/linux/ |
D | tty.h | 24 #define N_SMSBLOCK 12 /* SMS block mode - for talking to GSM data */ 33 #define N_CAIF 20 /* CAIF protocol for talking to modems */
|
D | ipmi.h | 113 * Channel for talking directly with the BMC. When using this 214 * The address type depends upon the channel type. When talking 216 * (IPMI_UNUSED_ADDR_TYPE). When talking to an IPMB channel, you must 219 * When talking to normal channels, the driver takes care of the
|
D | cuda.h | 3 * Definitions for talking to the CUDA. The CUDA is a microcontroller
|
/linux-5.10/include/linux/ |
D | cuda.h | 3 * Definitions for talking to the CUDA. The CUDA is a microcontroller
|
D | pmu.h | 3 * Definitions for talking to the PMU. The PMU is a microcontroller
|
/linux-5.10/include/asm-generic/ |
D | barrier.h | 25 * talking to devices. 180 /* Barriers for virtual machine guests when talking to an SMP host */
|
/linux-5.10/drivers/iio/dummy/ |
D | Kconfig | 30 a normal driver talking to hardware.
|
/linux-5.10/Documentation/hwmon/ |
D | sch5627.rst | 28 The hardware monitoring part of the SMSC SCH5627 is accessed by talking
|
/linux-5.10/tools/include/asm-generic/ |
D | barrier.h | 22 * talking to devices.
|
/linux-5.10/arch/x86/um/asm/ |
D | barrier.h | 9 * And yes, this is required on UP too when we're talking
|
/linux-5.10/tools/arch/s390/include/asm/ |
D | barrier.h | 15 * And yes, this is required on UP too when we're talking
|
/linux-5.10/arch/powerpc/include/asm/ |
D | pmi.h | 6 * Definitions for talking with PMI device on PowerPC
|
/linux-5.10/drivers/platform/chrome/wilco_ec/ |
D | Kconfig | 7 If you say Y here, you get support for talking to the ChromeOS
|
/linux-5.10/tools/arch/x86/include/asm/ |
D | barrier.h | 11 * And yes, this is required on UP too when we're talking
|
/linux-5.10/arch/sparc/include/asm/ |
D | prom.h | 8 * Definitions for talking to the Open Firmware PROM on
|
/linux-5.10/Documentation/userspace-api/media/dvb/ |
D | audio_data_types.rst | 10 talking to the audio device.
|
/linux-5.10/arch/s390/include/asm/ |
D | barrier.h | 13 * And yes, this is required on UP too when we're talking
|
/linux-5.10/drivers/auxdisplay/ |
D | Kconfig | 61 If you don't know what I'm talking about, load the parport module, 80 If you don't know what I'm talking about, ignore it. 129 If you don't know what I'm talking about, ignore it.
|
/linux-5.10/include/linux/usb/ |
D | quirks.h | 27 and can't handle talking to these interfaces */
|
/linux-5.10/drivers/virtio/ |
D | virtio_ring.c | 1712 * @_vq: the struct virtqueue we're talking about. 1747 * @vq: the struct virtqueue we're talking about. 1769 * @vq: the struct virtqueue we're talking about. 1791 * @vq: the struct virtqueue we're talking about. 1879 * @_vq: the struct virtqueue we're talking about. 1911 * @_vq: the struct virtqueue we're talking about. 1931 * @_vq: the struct virtqueue we're talking about. 1952 * @_vq: the struct virtqueue we're talking about. 1974 * @_vq: the struct virtqueue we're talking about. 1993 * @_vq: the struct virtqueue we're talking about. [all …]
|
/linux-5.10/Documentation/devicetree/bindings/display/panel/ |
D | tpo,tpg110.yaml | 18 SPI. By talking to the TPG110 over SPI, the strapped properties
|
/linux-5.10/arch/x86/include/asm/ |
D | barrier.h | 10 * And yes, this might be required on UP too when we're talking
|
/linux-5.10/drivers/usb/phy/ |
D | phy-keystone.c | 3 * phy-keystone - USB PHY, talking to dwc3 controller in Keystone.
|
/linux-5.10/Documentation/fb/ |
D | deferred_io.rst | 21 the real work talking to the device.
|
12345678