| /openbmc/linux/drivers/net/ethernet/amazon/ena/ |
| H A D | ena_com.h | 369 * @ena_dev: ENA communication layer struct
380 * @ena_dev: ENA communication layer struct
388 * @ena_dev: ENA communication layer struct
393 * @ena_dev: ENA communication layer struct
398 * @ena_dev: ENA communication layer struct
410 * @ena_dev: ENA communication layer struct
419 * @ena_dev: ENA communication layer struct
428 * @ena_dev: ENA communication layer struct
439 * @ena_dev: ENA communication layer struct
445 * @ena_dev: ENA communication layer struct
[all …]
|
| /openbmc/linux/drivers/media/cec/platform/ |
| H A 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
|
| /openbmc/linux/drivers/mailbox/ |
| H A D | Kconfig | 5 Mailbox is a framework to control hardware communication between
58 An implementation of the ARM PL320 Interprocessor Communication
69 Mailbox implementation for communication with the the firmware
79 interprocessor communication involving DSP, IVA1.0 and IVA2 in
96 This driver provides support for inter-processor communication
102 bool "Platform Communication Channel Driver"
106 ACPI 5.0+ spec defines a generic mode of communication
134 hardware for interprocessor communication.
143 is a communication entity found on few of Texas Instrument's keystone
144 and K3 architecture SoCs. These may be used for communication between
[all …]
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/ |
| H A D | 0009-FF-A-v15-arm_ffa-efi-introduce-FF-A-MM-communication.patch | 4 Subject: [PATCH] FF-A v15: arm_ffa: efi: introduce FF-A MM communication
6 Add MM communication support using FF-A transport
9 EFI MM communication protocol. MM partitions such as StandAlonneMM
16 and copied from the communication buffer to the MM shared buffer.
24 The response data is copied back to the communication buffer and
27 MM communication protocol supports FF-A 64-bit direct messaging.
65 * communication channel with the Standalone MM (Management Mode)
108 + int "Memory size of the shared MM communication buffer"
113 + buffer used for communication between the MM feature in U-Boot and
117 + It is assumed that the MM SP knows the size of the shared MM communication buffer.
[all …]
|
| H A D | 0010-FF-A-v15-arm_ffa-efi-corstone1000-enable-MM-communic.patch | 4 Subject: [PATCH] FF-A v15: arm_ffa: efi: corstone1000: enable MM communication
6 turn on EFI MM communication
8 On corstone1000 platform MM communication between u-boot
|
| /openbmc/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
|
| /openbmc/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
|
| /openbmc/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
|
| /openbmc/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 …]
|
| /openbmc/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.
|
| /openbmc/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
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/MCTP/ |
| H A D | Endpoint.interface.yaml | 2 Describe an MCTP endpoint. It is an MCTP communication terminus. An MCTP
22 a particular MCTP endpoint within a system for MCTP communication and
24 that comprise an MCTP communication network within a system. MCTP EIDs
34 communication payload in an MCTP message. The well defined message
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | ComponentIntegrity.v1_3_0.json | 83 "description": "Information about communication between two components.",
84 …"longDescription": "This object shall contain information about communication between two componen…
101 … "description": "The active sessions or communication channels between two components.",
112 … or communication channels between two components. The active sessions or communication channels …
168 …ntIntegrityType` property. If the service has not established secure communication with the devic…
492 "description": "Information about communication between two components.",
493 …"longDescription": "This object shall contain information about communication between two componen…
510 … "description": "The active sessions or communication channels between two components.",
521 … or communication channels between two components. The active sessions or communication channels …
601 … "description": "Information about communication between the SPDM Requester and SPDM Responder.",
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | ComponentIntegrity.v1_3_0.json | 83 "description": "Information about communication between two components.",
84 …"longDescription": "This object shall contain information about communication between two componen…
101 … "description": "The active sessions or communication channels between two components.",
112 … or communication channels between two components. The active sessions or communication channels …
168 …ntIntegrityType` property. If the service has not established secure communication with the devic…
492 "description": "Information about communication between two components.",
493 …"longDescription": "This object shall contain information about communication between two componen…
510 … "description": "The active sessions or communication channels between two components.",
521 … or communication channels between two components. The active sessions or communication channels …
601 … "description": "Information about communication between the SPDM Requester and SPDM Responder.",
[all …]
|
| /openbmc/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
|
| /openbmc/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.
|
| /openbmc/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.
|
| /openbmc/u-boot/drivers/mailbox/ |
| H A D | Kconfig | 10 the basis of a variety of inter-process/inter-CPU communication
32 Texas Instruments. Secure proxy is a communication entity mainly
33 used for communication between multiple processors with the SoC.
|
| /openbmc/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.
|
| /openbmc/linux/drivers/staging/media/atomisp/pci/runtime/bufq/interface/ |
| H A 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.
|
| /openbmc/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
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/libiec61850/ |
| H A D | libiec61850_1.5.3.bb | 3 communication systems in Substation Automation Systems \
5 (DER). It is seen as one of the communication standards \
9 61850-9-2/Sampled Values communication protocols \
|
| /openbmc/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()) the communication between
99 * The IOCTL opens a communication channel between a host client and
103 * Upone close() the communication is terminated.
|