| /linux/drivers/net/ethernet/amazon/ena/ |
| H A D | ena_com.h | 375 * @ena_dev: ENA communication layer struct
386 * @ena_dev: ENA communication layer struct
394 * @ena_dev: ENA communication layer struct
399 * @ena_dev: ENA communication layer struct
404 * @ena_dev: ENA communication layer struct
416 * @ena_dev: ENA communication layer struct
425 * @ena_dev: ENA communication layer struct
434 * @ena_dev: ENA communication layer struct
445 * @ena_dev: ENA communication layer struct
451 * @ena_dev: ENA communication layer struct
[all …]
|
| /linux/drivers/rpmsg/ |
| H A D | Kconfig | 39 Say y here to enable support providing communication channels to
53 Say y here to enable support for the GLINK RPM communication driver,
54 which serves as a channel for communication with the RPM in GLINK
63 Say y here to enable support for the GLINK SMEM communication driver,
64 which provides support for using the GLINK communication protocol
74 providing communication channels to remote processors in Qualcomm
|
| /linux/Documentation/ABI/testing/ |
| H A 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)
|
| H A 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
|
| /linux/include/rdma/ |
| H A D | ib_cm.h | 274 * 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
305 * ib_create_cm_id - Allocate a communication identifier.
306 * @device: Device associated with the cm_id. All related communication will
309 * @context: User specified context associated with the communication
312 * Communication identifiers are used to track connection states, service
[all …]
|
| H A D | rdma_cm.h | 222 * @id: Communication identifier associated with the QP attributes to
271 * communication events. Events that should be reported to the CM and
294 * @id: Communication identifier associated with the request.
313 * @id: Communication identifier to associated with service type.
318 * performing route resolution, as existing communication on the
327 * @id: Communication identifier to configure.
337 * @id: Communication identifer to configure.
349 * @id: Communication identifier associated with the address.
356 * @id: Communication identifier that received the REJECT event.
364 * @id: Communication identifier that received the REJECT event.
[all …]
|
| /linux/Documentation/driver-api/surface_aggregator/ |
| H A 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
|
| /linux/drivers/firmware/tegra/ |
| H A D | Kconfig | 8 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
22 IVC module as the message communication protocol.
|
| /linux/Documentation/netlabel/ |
| H A 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
|
| /linux/drivers/gpu/drm/xe/abi/ |
| H A D | guc_relay_communication_abi.h | 16 * DOC: GuC Relay Communication
18 * The communication between Virtual Function (VF) drivers and Physical Function
55 * It is also possible that PF driver will initiate communication with the
80 * Function (VF) drivers to communicate using `GuC Relay Communication`_.
104 * The `GuC Relay Communication`_ can be used to pass `Relay Message`_ between
106 * `GuC Relay Communication`_ uses error codes that mostly match errno values.
|
| H A D | guc_communication_mmio_abi.h | 10 * DOC: GuC MMIO based communication
12 * The MMIO based communication between Host and GuC relies on special
27 * The MMIO based communication is mainly used during driver initialization
28 * phase to setup the `CTB based communication`_ that will be used afterwards.
|
| /linux/Documentation/security/tpm/ |
| H A D | tpm_tis.rst | 21 Communication is based on a 20 KiB buffer shared by the TPM chip through a
24 sets of registers for communication between the CPU and TPM. These
25 communication endpoints are called localities in the TCG terminology.
30 communication, the kernel writes the TPM_ACCESS.activeLocality bit. This
|
| /linux/Documentation/devicetree/bindings/mailbox/ |
| H A 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
|
| /linux/net/iucv/ |
| H A D | Kconfig | 7 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/drivers/gpu/drm/i915/gt/uc/abi/ |
| H A D | guc_communication_mmio_abi.h | 10 * DOC: GuC MMIO based communication
12 * The MMIO based communication between Host and GuC relies on special
27 * The MMIO based communication is mainly used during driver initialization
28 * phase to setup the `CTB based communication`_ that will be used afterwards.
|
| /linux/drivers/platform/surface/aggregator/ |
| H A D | Kconfig | 26 is the device responsible for the communication with the EC, and a
35 due to a difference in the communication interface of the controller,
67 transport and communication problems, such as invalid data sent to or
68 received from the EC, dropped data, and communication timeouts.
|
| /linux/tools/testing/selftests/drivers/net/ |
| H A D | README.rst | 52 and communication method.
68 Communication method used to run commands on the remote endpoint.
76 Communication methods are defined by classes in ``lib/py/remote_{name}.py``.
83 Arguments used to construct the communication channel.
84 Communication channel dependent::
|
| /linux/drivers/clk/sunxi/ |
| H A D | Kconfig | 25 usually needed for the PMIC communication, mostly.
32 Those are usually needed for the PMIC communication,
40 usually needed for the PMIC communication, mostly.
|
| /linux/Documentation/driver-api/usb/ |
| H A 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
|
| /linux/include/uapi/linux/ |
| H A D | mei.h | 14 * FW Client (given by UUID). This opens a communication channel
17 * Only in close() (file_operation release()) is the communication between
99 * The IOCTL opens a communication channel between a host client and
103 * Upon close() the communication is terminated.
|
| /linux/sound/soc/intel/avs/ |
| H A D | registers.h | 43 /* SKL Intel HD Audio Inter-Processor Communication Registers */
55 /* CNL Intel HD Audio Inter-Processor Communication Registers */
84 /* DSP -> HOST communication window */
86 /* HOST -> DSP communication window */
|
| /linux/Documentation/ABI/stable/ |
| H A 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
|
| /linux/drivers/iio/common/ssp_sensors/ |
| H A D | ssp.h | 154 * @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/drivers/misc/vmw_vmci/ |
| H A D | vmci_route.c | 97 * 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/drivers/nfc/ |
| H A D | Kconfig | 3 # Near Field Communication (NFC) devices
6 menu "Near Field Communication (NFC) devices"
58 This driver supports communication between the virtual NCI device and
|