Searched full:communication (Results 1 – 25 of 1353) sorted by relevance
12345678910>>...55
| /linux-6.12.1/drivers/net/ethernet/amazon/ena/ |
| D | ena_com.h | 378 * @ena_dev: ENA communication layer struct
389 * @ena_dev: ENA communication layer struct
397 * @ena_dev: ENA communication layer struct
402 * @ena_dev: ENA communication layer struct
407 * @ena_dev: ENA communication layer struct
419 * @ena_dev: ENA communication layer struct
428 * @ena_dev: ENA communication layer struct
437 * @ena_dev: ENA communication layer struct
448 * @ena_dev: ENA communication layer struct
454 * @ena_dev: ENA communication layer struct
[all …]
|
| /linux-6.12.1/drivers/mailbox/ |
| D | Kconfig | 5 Mailbox is a framework to control hardware communication between
59 An implementation of the ARM PL320 Interprocessor Communication
70 Mailbox implementation for communication with the the firmware
80 interprocessor communication involving DSP, IVA1.0 and IVA2 in
88 This driver provides support for inter-processor communication
94 bool "Platform Communication Channel Driver"
98 ACPI 5.0+ spec defines a generic mode of communication
126 hardware for interprocessor communication.
135 is a communication entity found on few of Texas Instrument's keystone
136 and K3 architecture SoCs. These may be used for communication between
[all …]
|
| /linux-6.12.1/drivers/media/cec/platform/ |
| D | Kconfig | 14 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-6.12.1/drivers/rpmsg/ |
| 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-6.12.1/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
|
| /linux-6.12.1/include/rdma/ |
| 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 …]
|
| 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-6.12.1/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
|
| /linux-6.12.1/drivers/firmware/tegra/ |
| 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-6.12.1/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
|
| /linux-6.12.1/Documentation/security/tpm/ |
| 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-6.12.1/drivers/gpu/drm/xe/abi/ |
| 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.
|
| 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-6.12.1/net/iucv/ |
| 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-6.12.1/drivers/gpu/drm/i915/gt/uc/abi/ |
| 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-6.12.1/drivers/platform/surface/aggregator/ |
| 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-6.12.1/drivers/staging/media/atomisp/pci/runtime/bufq/interface/ |
| D | ia_css_bufq.h | 67 *-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-6.12.1/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
|
| /linux-6.12.1/drivers/clk/sunxi/ |
| 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-6.12.1/tools/testing/selftests/drivers/net/ |
| 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-6.12.1/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
|
| /linux-6.12.1/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
|
| /linux-6.12.1/sound/soc/intel/avs/ |
| D | registers.h | 41 /* SKL Intel HD Audio Inter-Processor Communication Registers */
53 /* CNL Intel HD Audio Inter-Processor Communication Registers */
82 /* DSP -> HOST communication window */
84 /* HOST -> DSP communication window */
|
| /linux-6.12.1/include/uapi/linux/ |
| 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.
|
12345678910>>...55