Searched full:communication (Results 1 – 25 of 215) sorted by relevance
123456789
| /Documentation/devicetree/bindings/iio/ |
| D | sensorhub.txt | 9 - interrupts: communication interrupt
10 - ap-mcu-gpios: [out] ap to sensorhub line - used during communication
11 - mcu-ap-gpios: [in] sensorhub to ap - used during communication
|
| /Documentation/netlabel/ |
| D | introduction.rst | 15 is composed of three main components, the protocol engines, the communication
31 Communication Layer
34 The communication layer exists to allow NetLabel configuration and monitoring
35 from user space. The NetLabel communication layer uses a message based
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-rpmsg | 6 Every rpmsg device is a communication channel with a remote
18 Every rpmsg device is a communication channel with a remote
36 Every rpmsg device is a communication channel with a remote
58 Every rpmsg device is a communication channel with a remote
82 Every rpmsg device is a communication channel with a remote
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | drbd-connection-state-overview.dot | 16 label="{communication loss|{Timeout|BrokenPipe|NetworkFailure}}" ]
54 // comm_error [label="communication trouble"]
61 Unconnected -> StandAlone [ label="drbdadm disconnect\lor serious communication trouble" ]
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,glink.txt | 4 communication between subsystem-pairs on various Qualcomm platforms. Two types
22 signal this processor about communication related events
42 communication channel. The name of the nodes are not important. The properties
|
| D | qcom,apr.txt | 4 communication between Application processor and QDSP. APR is mainly
50 which uses apr as communication between Apps and QDSP.
|
| D | qcom,smd.txt | 4 communication channel for sending data between the various subsystems in
23 signal this processor about communication related updates
|
| /Documentation/driver-api/usb/ |
| D | typec_bus.rst | 8 Alternate modes require communication with the partner using Vendor Defined
10 The communication is SVID (Standard or Vendor ID) specific, i.e. specific for
24 matching SVID and mode. Communication between the port driver and alternate mode
30 partners to the alternate mode drivers. No direct SVID specific communication is
51 If the communication with the partner using the SVID specific commands results
|
| /Documentation/driver-api/ |
| D | smsc_ece1099.rst | 33 Communication Protocol
39 interface. SMBus is a serial communication protocol between
53 The BC-Link is a proprietary bus that allows communication
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | omap-mailbox.txt | 4 The OMAP mailbox hardware facilitates communication between different processors
7 communication is achieved through a set of registers for message storage and
17 and tx interrupt source per h/w fifo. Communication between different processors
77 used for the communication between the host processor and a remote processor.
114 the intended sub-mailbox child node to be used for communication. The equivalent
115 "mbox-names" property value can be used to give a name to the communication channel
|
| D | nvidia,tegra186-hsp.txt | 5 interprocessor communication. So the interprocessor communication (IPC)
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-ib_srp | 21 InfiniBand service ID used to establish communication with
95 Description: Number of RDMA channels used for communication with the SRP
115 Description: InfiniBand destination GID used for communication with the SRP
158 for communication with the SRP target.
172 Description: InfiniBand service ID used for establishing communication with
179 Description: InfiniBand GID of the source port used for communication with
|
| /Documentation/devicetree/bindings/input/ |
| D | hid-over-i2c.txt | 10 If this binding is used, the kernel module i2c-hid will handle the communication
34 or powering it on, before it is ready for communication.
|
| /Documentation/mic/ |
| D | scif_overview.rst | 2 Symmetric Communication Interface (SCIF)
5 The Symmetric Communication Interface (SCIF (pronounced as skiff)) is a low
7 SCIF provides inter-node communication within a single host platform, where a
11 is to deliver the maximum possible performance given the communication
|
| /Documentation/devicetree/bindings/i2c/ |
| D | nvidia,tegra20-i2c.txt | 11 controller. This only support master mode of I2C communication. Register
16 master and slave mode of I2C communication. The i2c-tegra driver only
17 support master mode of I2C communication. Driver of I2C controller is
|
| /Documentation/i2c/busses/ |
| D | i2c-taos-evm.rst | 44 The communication protocol is text-based and pretty simple. It is
46 module. The communication is rather slow, because the serial port has
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-log.rst | 47 The structure used for communication between kernel and userspace are
49 diversity, and 2-way communication nature of the exchanges between
51 communication.
|
| /Documentation/hwmon/ |
| D | lm70.rst | 40 Communication with the LM70 is simple: when the temperature is to be sensed,
41 the driver accesses the LM70 using SPI communication: 16 SCLK cycles
|
| /Documentation/driver-api/nfc/ |
| D | nfc-pn544.rst | 2 Kernel driver for the NXP Semiconductors PN544 Near Field Communication chip
10 communication. The driver goes under drives/nfc/ and is compiled as a
|
| D | index.rst | 4 Near Field Communication
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | wkup_m3_ipc.txt | 8 to boot the wkup_m3, it handles communication with the CM3 using IPC registers
29 channel for communication. Must point to appropriate
|
| /Documentation/devicetree/bindings/sound/ |
| D | mt6351.txt | 3 The communication between MT6351 and SoC is through Mediatek PMIC wrapper.
|
| D | mt6358.txt | 3 The communication between MT6358 and SoC is through Mediatek PMIC wrapper.
|
| D | cs4270.txt | 14 deasserted before communication to the codec starts.
|
| /Documentation/devicetree/bindings/serial/ |
| D | arm_sbsa_uart.txt | 3 in the PL011 driver. It's baudrate and other communication parameters
|
123456789