Home
last modified time | relevance | path

Searched full:communication (Results 1 – 25 of 1126) sorted by relevance

12345678910>>...46

/Linux-v5.10/drivers/net/ethernet/amazon/ena/
Dena_com.h367 * @ena_dev: ENA communication layer struct
378 * @ena_dev: ENA communication layer struct
386 * @ena_dev: ENA communication layer struct
391 * @ena_dev: ENA communication layer struct
396 * @ena_dev: ENA communication layer struct
408 * @ena_dev: ENA communication layer struct
417 * @ena_dev: ENA communication layer struct
426 * @ena_dev: ENA communication layer struct
437 * @ena_dev: ENA communication layer struct
443 * @ena_dev: ENA communication layer struct
[all …]
/Linux-v5.10/drivers/mailbox/
DKconfig5 Mailbox is a framework to control hardware communication between
39 An implementation of the ARM PL320 Interprocessor Communication
50 Mailbox implementation for communication with the the firmware
60 interprocessor communication involving DSP, IVA1.0 and IVA2 in
77 This driver provides support for inter-processor communication
83 bool "Platform Communication Channel Driver"
87 ACPI 5.0+ spec defines a generic mode of communication
115 hardware for interprocessor communication.
123 is a communication entity found on few of Texas Instrument's keystone
124 and K3 architecture SoCs. These may be used for communication between
[all …]
/Linux-v5.10/drivers/media/cec/platform/
DKconfig14 The CEC bus is present in the HDMI connector and enables communication
25 CEC bus is present in the HDMI connector and enables communication
40 CEC bus is present in the HDMI connector and enables communication
52 The CEC bus is present in the HDMI connector and enables communication
63 CEC bus is present in the HDMI connector and enables communication
74 CEC bus is present in the HDMI connector and enables communication
86 CEC bus is present in the HDMI connector and enables communication
97 The CEC bus is present in the HDMI connector and enables communication
109 CEC bus is present in the HDMI connector and enables communication
/Linux-v5.10/drivers/rpmsg/
DKconfig23 Say y here to enable support providing communication channels to
37 Say y here to enable support for the GLINK RPM communication driver,
38 which serves as a channel for communication with the RPM in GLINK
47 Say y here to enable support for the GLINK SMEM communication driver,
48 which provides support for using the GLINK communication protocol
58 providing communication channels to remote processors in Qualcomm
/Linux-v5.10/Documentation/ABI/testing/
Dconfigfs-most40 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)
Dsysfs-bus-rpmsg6 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
/Linux-v5.10/drivers/firmware/tegra/
DKconfig8 IVC (Inter-VM Communication) protocol is part of the IPC
9 (Inter Processor Communication) framework on Tegra. It maintains the
10 data and the different communication channels in SysRAM or RAM and
21 IVC module as the message communication protocol.
/Linux-v5.10/include/rdma/
Dib_cm.h274 * ib_cm_handler - User-defined callback to process communication events.
275 * @cm_id: Communication identifier associated with the reported event.
276 * @event: Information about the communication event.
278 * IB_CM_REQ_RECEIVED and IB_CM_SIDR_REQ_RECEIVED communication events
283 * to a user's existing communication identifier.
286 * however, returning a non-zero value instructs the communication manager to
306 * ib_create_cm_id - Allocate a communication identifier.
307 * @device: Device associated with the cm_id. All related communication will
310 * @context: User specified context associated with the communication
313 * Communication identifiers are used to track connection states, service
[all …]
Drdma_cm.h211 * @id: Communication identifier associated with the QP attributes to
260 * communication events. Events that should be reported to the CM and
283 * @id: Communication identifier associated with the request.
302 * @id: Communication identifier to associated with service type.
307 * performing route resolution, as existing communication on the
316 * @id: Communication identifier to configure.
326 * @id: Communication identifer to configure.
336 * @id: Communication identifier associated with the address.
343 * @id: Communication identifier that received the REJECT event.
351 * @id: Communication identifier that received the REJECT event.
[all …]
/Linux-v5.10/Documentation/netlabel/
Dintroduction.rst15 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
/Linux-v5.10/net/iucv/
DKconfig7 Select this option if you want to use inter-user communication
9 communication link between VM guests.
17 based on z/VM inter-user communication vehicle or based on
/Linux-v5.10/Documentation/devicetree/bindings/iio/
Dsensorhub.txt9 - 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
/Linux-v5.10/drivers/clk/sunxi/
DKconfig26 usually needed for the PMIC communication, mostly.
34 Those are usually needed for the PMIC communication,
42 usually needed for the PMIC communication, mostly.
/Linux-v5.10/drivers/staging/media/atomisp/pci/runtime/bufq/interface/
Dia_css_bufq.h67 *-host to SP event communication queue
68 * -SP to host event communication queue
103 * @brief Enqueue an event item into host to SP communication event queue.
120 * @brief Dequeue an item from SP to host communication event queue.
142 * @brief Dequeue an item from SP to host communication EOF event queue.
/Linux-v5.10/Documentation/driver-api/usb/
Dtypec_bus.rst8 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
/Linux-v5.10/include/uapi/linux/
Dmei.h14 * FW Client (given by UUID). This opens a communication channel
17 * Only in close() (file_operation release()) the communication between
99 * The IOCTL opens a communication channel between a host client and
103 * Upone close() the communication is terminated.
/Linux-v5.10/drivers/bluetooth/
DKconfig112 UART (H4) is serial protocol for communication between Bluetooth
127 Nokia H4+ is serial protocol for communication between Bluetooth
138 BCSP (BlueCore Serial Protocol) is serial protocol for communication
151 communication between host and Atheros AR300x Bluetooth devices.
163 HCILL (HCI Low Level) is a serial protocol for communication
178 communication may have bit errors, overrun errors or burst
254 Marvell is serial protocol for communication between Bluetooth
/Linux-v5.10/Documentation/devicetree/bindings/mailbox/
Domap-mailbox.txt4 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
/Linux-v5.10/Documentation/ABI/stable/
Dsysfs-driver-ib_srp22 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
/Linux-v5.10/include/net/iucv/
Diucv.h55 * IUCV_IPLOCAL Specifies that the communication partner has to be on the
155 * type 0x03 has been received. The communication peer shutdown
156 * his end of the communication path. The path still exists and
163 * type 0x04 has been received. The communication peer has quiesced
170 * type 0x05 has been received. The communication peer has resumed
251 * @userdata: 16 bytes of data reflected to the communication partner
255 * external interrupt and now wishes to complete the IUCV communication path.
268 * @userdata: 16 bytes of data reflected to the communication partner
284 * @userdata: 16 bytes of data reflected to the communication partner
296 * @userdata: 16 bytes of data reflected to the communication partner
[all …]
/Linux-v5.10/drivers/iio/common/ssp_sensors/
Dssp.h154 * @com_fail_cnt: communication fail count
164 * @batch_latency_buf: yet unknown but existing in communication protocol
165 * @batch_opt_buf: yet unknown but existing in communication protocol
166 * @accel_position: yet unknown but existing in communication protocol
167 * @mag_position: yet unknown but existing in communication protocol
/Linux-v5.10/drivers/misc/vmw_vmci/
Dvmci_route.c97 * host local communication. The hypervisor in vmci_route()
169 * VM to VM communication is not in vmci_route()
171 * communication destined for the host in vmci_route()
197 * VM communication here, since we want to be able to use the guest in vmci_route()
198 * driver on older versions that do support VM to VM communication. in vmci_route()
/Linux-v5.10/Documentation/admin-guide/blockdev/drbd/
Ddrbd-connection-state-overview.dot16 label="{communication loss|{Timeout|BrokenPipe|NetworkFailure}}" ]
54 // comm_error [label="communication trouble"]
61 Unconnected -> StandAlone [ label="drbdadm disconnect\lor serious communication trouble" ]
/Linux-v5.10/include/net/
Daf_vsock.h40 bool cached_peer_allow_dgram; /* Dgram communication allowed to
95 /* Transport provides host->guest communication */
97 /* Transport provides guest->host communication */
99 /* Transport provides DGRAM communication */
101 /* Transport provides local (loopback) communication */
/Linux-v5.10/Documentation/devicetree/bindings/soc/qcom/
Dqcom,glink.txt4 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

12345678910>>...46