Home
last modified time | relevance | path

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

12345678910>>...98

/kernel/linux/linux-5.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 …]
/kernel/linux/linux-6.6/drivers/net/ethernet/amazon/ena/
Dena_com.h369 * @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 …]
/kernel/linux/linux-5.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 …]
/kernel/linux/linux-5.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
/kernel/linux/linux-6.6/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
/kernel/linux/linux-6.6/drivers/mailbox/
DKconfig5 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 …]
/kernel/linux/linux-5.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
/kernel/linux/linux-6.6/drivers/rpmsg/
DKconfig39 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
/kernel/linux/linux-6.6/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
/kernel/linux/linux-5.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
/kernel/linux/linux-6.6/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
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 …]
Drdma_cm.h222 * @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 …]
/kernel/linux/linux-6.6/Documentation/driver-api/surface_aggregator/
Doverview.rst18 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
/kernel/linux/linux-6.6/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
22 IVC module as the message communication protocol.
/kernel/linux/linux-5.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.
/kernel/linux/linux-5.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 …]
/kernel/linux/linux-5.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
/kernel/linux/linux-6.6/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
/kernel/linux/linux-5.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
/kernel/linux/linux-6.6/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
/kernel/linux/linux-5.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
/kernel/linux/linux-6.6/drivers/gpu/drm/i915/gt/uc/abi/
Dguc_communication_mmio_abi.h10 * 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.

12345678910>>...98