Searched full:communication (Results 1 – 25 of 2003) sorted by relevance
12345678910>>...81
| /kernel/linux/linux-5.10/drivers/net/ethernet/amazon/ena/ |
| D | ena_com.h | 367 * @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 …]
|
| /kernel/linux/linux-4.19/drivers/net/ethernet/amazon/ena/ |
| D | ena_com.h | 370 * @ena_dev: ENA communication layer struct
381 * @ena_dev: ENA communication layer struct
389 * @ena_dev: ENA communication layer struct
394 * @ena_dev: ENA communication layer struct
399 * @ena_dev: ENA communication layer struct
414 * @ena_dev: ENA communication layer struct
423 * @ena_dev: ENA communication layer struct
432 * @ena_dev: ENA communication layer struct
443 * @ena_dev: ENA communication layer struct
449 * @ena_dev: ENA communication layer struct
[all …]
|
| /kernel/linux/linux-5.10/drivers/mailbox/ |
| D | Kconfig | 5 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 …]
|
| /kernel/linux/linux-4.19/drivers/mailbox/ |
| D | Kconfig | 4 Mailbox is a framework to control hardware communication between
38 An implementation of the ARM PL320 Interprocessor Communication
49 interprocessor communication involving DSP, IVA1.0 and IVA2 in
66 This driver provides support for inter-processor communication
72 bool "Platform Communication Channel Driver"
76 ACPI 5.0+ spec defines a generic mode of communication
104 hardware for interprocessor communication.
112 communication entity found on few of Texas Instrument's keystone
113 architecture SoCs. These may be used for communication between
150 providing an interface for invoking the inter-process communication
[all …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/drivers/rpmsg/ |
| D | Kconfig | 23 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
|
| /kernel/linux/linux-4.19/drivers/rpmsg/ |
| D | Kconfig | 28 Say y here to enable support for the GLINK RPM communication driver,
29 which serves as a channel for communication with the RPM in GLINK
38 Say y here to enable support for the GLINK SMEM communication driver,
39 which provides support for using the GLINK communication protocol
49 providing communication channels to remote processors in Qualcomm
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
21 IVC module as the message communication protocol.
|
| /kernel/linux/linux-5.10/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
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 …]
|
| D | rdma_cm.h | 211 * @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 …]
|
| /kernel/linux/linux-4.19/include/rdma/ |
| D | ib_cm.h | 298 * ib_cm_handler - User-defined callback to process communication events.
299 * @cm_id: Communication identifier associated with the reported event.
300 * @event: Information about the communication event.
302 * IB_CM_REQ_RECEIVED and IB_CM_SIDR_REQ_RECEIVED communication events
307 * to a user's existing communication identifier.
310 * however, returning a non-zero value instructs the communication manager to
330 * ib_create_cm_id - Allocate a communication identifier.
331 * @device: Device associated with the cm_id. All related communication will
334 * @context: User specified context associated with the communication
337 * Communication identifiers are used to track connection states, service
[all …]
|
| D | rdma_cm.h | 229 * @id: Communication identifier associated with the QP attributes to
299 * communication events. Events that should be reported to the CM and
322 * @id: Communication identifier associated with the request.
341 * @id: Communication identifier to associated with service type.
346 * performing route resolution, as existing communication on the
355 * @id: Communication identifier to configure.
365 * @id: Communication identifer to configure.
374 * @id: Communication identifier associated with the address.
381 * @id: Communication identifier that received the REJECT event.
389 * @id: Communication identifier that received the REJECT event.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/netlabel/ |
| D | introduction.txt | 12 is composed of three main components, the protocol engines, the communication
27 * Communication Layer
29 The communication layer exists to allow NetLabel configuration and monitoring
30 from user space. The NetLabel communication layer uses a message based
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| 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
|
| /kernel/linux/linux-4.19/net/iucv/ |
| D | Kconfig | 6 Select this option if you want to use inter-user communication
8 communication link between VM guests.
16 based on z/VM inter-user communication vehicle or based on
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/drivers/firmware/tegra/ |
| D | Kconfig | 7 IVC (Inter-VM Communication) protocol is part of the IPC
8 (Inter Processor Communication) framework on Tegra. It maintains the
20 IVC module as the message communication protocol.
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/mailbox/ |
| D | omap-mailbox.txt | 4 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
56 used for the communication between the host processor and a remote processor.
93 the intended sub-mailbox child node to be used for communication. The equivalent
94 "mbox-names" property value can be used to give a name to the communication channel
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/ |
| D | sensorhub.txt | 9 - 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
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/iio/ |
| D | sensorhub.txt | 9 - 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
|
| /kernel/linux/linux-5.10/drivers/clk/sunxi/ |
| D | Kconfig | 26 usually needed for the PMIC communication, mostly.
34 Those are usually needed for the PMIC communication,
42 usually needed for the PMIC communication, mostly.
|
| /kernel/linux/linux-5.10/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.
|
12345678910>>...81