Searched full:communication (Results 1 – 25 of 307) sorted by relevance
12345678910>>...13
| /Documentation/ABI/testing/ |
| D | configfs-most | 40 for MediaLB communication only)
46 communication only)
95 for MediaLB communication only)
101 communication only)
150 for MediaLB communication only)
156 communication only)
216 for MediaLB communication only)
222 communication only)
|
| 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/driver-api/surface_aggregator/ |
| D | overview.rst | 18 4, Surface Book 1), due to the use of a different communication interface
45 Communication chapter
48 The type of communication interface between host and EC depends on the
51 5th and later generations, communication takes place via a USART serial
57 Currently, this subsystem only supports SAM-over-SSH. The SSH communication
67 communication interface for SAM on 5th- and all later-generation Surface
68 devices. On the highest level, communication can be separated into two main
|
| /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/devicetree/bindings/remoteproc/ |
| D | qcom,glink-edge.yaml | 7 title: Qualcomm G-Link Edge communication channel nodes
13 Qualcomm G-Link subnode represents communication edge, channels and devices
52 ID of the shared memory used by GLINK for communication with remote
|
| D | qcom,pas-common.yaml | 69 Qualcomm Shared Memory subnode which represents communication edge,
76 Qualcomm G-Link subnode which represents communication edge, channels
|
| /Documentation/virt/geniezone/ |
| D | introduction.rst | 15 kernel for vCPU scheduling, memory management, inter-VM communication and virtio
44 - Inter-VM Communication
46 Communication among guest VMs was provided mainly on RPC. More communication
|
| /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/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/networking/ |
| D | tipc.rst | 10 TIPC (Transparent Inter Process Communication) is a protocol that is specially
11 designed for intra-cluster communication. It can be configured to transmit
29 Welcome to the Transparent Inter Process Communication service, TIPC in short,
58 It can also use a service address to create and join a Communication Group,
62 datagram mode and in communication group mode.
66 Communication between any two nodes in a cluster is maintained by one or two
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | ti,omap-mailbox.yaml | 13 The OMAP Mailbox hardware facilitates communication between different
16 interconnect bus. The communication is achieved through a set of registers
27 h/w fifo. Communication between different processors is achieved through the
49 within a SoC. The sub-mailboxes (actual communication channels) are
59 phandle to the intended sub-mailbox child node to be used for communication.
61 communication channel to be used by the client user.
68 uni-directional communication channel. A typical sub-mailbox device uses
90 node and represents the actual communication channel used to send and
|
| D | qcom-ipcc.yaml | 7 title: Qualcomm Technologies, Inc. Inter-Processor Communication Controller
13 The Inter-Processor Communication Controller (IPCC) is a centralized hardware
|
| /Documentation/virt/gunyah/ |
| D | index.rst | 46 - Inter-VM Communication:
63 Para-virtualization of devices is supported using inter-VM communication and
79 For example, inter-VM communication using Gunyah doorbells and message queues
102 Communication with the resource manager from other virtual machines happens as
129 A VM requires boot configuration to establish communication with the resource
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-ib_srp | 22 InfiniBand service ID used to establish communication with
98 Description: Number of RDMA channels used for communication with the SRP
118 Description: InfiniBand destination GID used for communication with the SRP
161 for communication with the SRP target.
175 Description: InfiniBand service ID used for establishing communication with
182 Description: InfiniBand GID of the source port used for communication with
|
| /Documentation/devicetree/bindings/iio/ |
| D | samsung,sensorhub-rinato.yaml | 31 Application Processor to sensorhub line - used during communication
36 Sensorhub to Application Processor - used during communication
|
| /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/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/input/ |
| D | hid-over-i2c.yaml | 21 If this binding is used, the kernel module i2c-hid will handle the communication
51 or powering it on, before it is ready for communication.
|
| /Documentation/hwmon/ |
| D | lm70.rst | 44 Communication with the LM70 is simple: when the temperature is to be sensed,
45 the driver accesses the LM70 using SPI communication: 16 SCLK cycles
|
| /Documentation/devicetree/bindings/sound/ |
| D | mt6351.txt | 3 The communication between MT6351 and SoC is through Mediatek PMIC wrapper.
|
| D | cs4270.txt | 14 deasserted before communication to the codec starts.
|
| /Documentation/networking/device_drivers/wwan/ |
| D | iosm.rst | 14 manage the MBIM interface to enable data communication towards WWAN.
47 MBIM protocol communication.
72 up to 8 IP sessions for simultaneous IP communication.
|
| /Documentation/devicetree/bindings/serial/ |
| D | arm_sbsa_uart.txt | 3 in the PL011 driver. It's baudrate and other communication parameters
|
12345678910>>...13