Searched full:communicate (Results 1 – 25 of 525) sorted by relevance
12345678910>>...21
| /linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-driver-w1_therm | 13 Users: any user space application which wants to communicate with
29 Users: any user space application which wants to communicate with
43 Users: any user space application which wants to communicate with
65 Users: any user space application which wants to communicate with
86 Users: any user space application which wants to communicate with
107 Users: any user space application which wants to communicate with
135 Users: any user space application which wants to communicate with
|
| /linux-5.10/Documentation/driver-api/xilinx/ |
| D | eemi.rst | 8 ZynqMP has an interface to communicate with secure firmware. Firmware
10 used by any driver to communicate with PMC(Platform Management Controller).
16 device to communicate with a power management controller (PMC) on a
21 structure. Any driver who want to communicate with PMC using EEMI APIs
|
| /linux-5.10/drivers/crypto/cavium/cpt/ |
| D | cptvf_mbox.c | 104 * Communicate VQs size to PF to program CPT(0)_PF_Q(0-15)_CTL of the VF.
123 * Communicate VF group required to PF and get the VQ binded to that group
142 * Communicate VF group required to PF and get the VQ binded to that group
160 * Communicate to PF that VF is UP and running
177 * Communicate to PF that VF is DOWN and running
|
| /linux-5.10/drivers/crypto/marvell/octeontx/ |
| D | otx_cptvf_mbox.c | 171 * Communicate VQs size to PF to program CPT(0)_PF_Q(0-15)_CTL of the VF.
187 * Communicate VF group required to PF and get the VQ binded to that group
206 * Communicate VF group required to PF and get the VQ binded to that group
222 * Communicate to PF that VF is UP and running
236 * Communicate to PF that VF is DOWN and running
|
| /linux-5.10/Documentation/ABI/stable/ |
| D | sysfs-driver-w1_ds28e04 | 6 Users: any user space application which wants to communicate with DS28E04-100
15 Users: any user space application which wants to communicate with DS28E04-100
|
| /linux-5.10/drivers/usb/storage/ |
| D | scsiglue.h | 10 * describes in detail the protocol used to communicate with such
18 * that they are used to communicate wait, failed and OK on commands.
|
| D | initializers.h | 9 * describes in detail the protocol used to communicate with such
17 * that they are used to communicate wait, failed and OK on commands.
|
| D | protocol.h | 10 * describes in detail the protocol used to communicate with such
18 * that they are used to communicate wait, failed and OK on commands.
|
| D | debug.h | 13 * describes in detail the protocol used to communicate with such
21 * that they are used to communicate wait, failed and OK on commands.
|
| D | transport.h | 10 * describes in detail the protocol used to communicate with such
18 * that they are used to communicate wait, failed and OK on commands.
|
| D | initializers.c | 9 * describes in detail the protocol used to communicate with such
17 * that they are used to communicate wait, failed and OK on commands.
|
| /linux-5.10/Documentation/devicetree/bindings/firmware/xilinx/ |
| D | xlnx,zynqmp-firmware.txt | 6 ZynqMP has an interface to communicate with secure firmware. Firmware
8 used by any driver to communicate to PMUFW(Platform Management Unit).
|
| /linux-5.10/samples/ |
| D | Kconfig | 92 communicate with a remote QRTR service, using QMI encoded messages.
99 to communicate with an AMP-configured remote processor over
119 the connector interface and a user space tool to communicate
|
| /linux-5.10/drivers/w1/masters/ |
| D | Kconfig | 12 Say Y here if you want to communicate with your 1-wire devices
55 Say Y here if you want to communicate with your 1-wire devices using
|
| /linux-5.10/include/linux/ |
| D | psp-tee.h | 18 * and the API exported by AMD Secure Processor driver to communicate with
70 * which it can communicate.
|
| /linux-5.10/Documentation/networking/ |
| D | framerelay.rst | 15 net-tools archives is 'dlcicfg'. This program will communicate with the
20 The DLCI uses a number of function calls to communicate with the FRAD, all
|
| D | ipddp.rst | 15 networks can use to communicate via IP. AppleTalk-IP is simply IP datagrams
18 Through this driver you can either allow your Linux box to communicate
|
| /linux-5.10/Documentation/devicetree/bindings/mailbox/ |
| D | fsl,mu.yaml | 14 communicate and coordinate by passing messages (e.g. data, status
39 - description: To communicate with i.MX8 SCU with fast IPC
|
| /linux-5.10/Documentation/networking/device_drivers/ethernet/marvell/ |
| D | octeontx2.rst | 119 - VFs cannot communicate with AF directly, they send mbox message to PF and PF
130 - These VFs can be used by applications or virtual machines to communicate between them
133 - These communicate directly with AF (PF0) via mbox.
|
| /linux-5.10/include/uapi/linux/ |
| D | mei.h | 16 * will communicate with the associated FW client.
101 * and write will communicate with the associated FW client with
|
| /linux-5.10/Documentation/driver-api/md/ |
| D | md-cluster.rst | 60 Each node has to communicate with other nodes when starting or ending
128 The DLM LVB is used to communicate within nodes of the cluster. There
135 communicate.
139 The lock resource which carries the data to communicate.
147 communicate.
|
| /linux-5.10/Documentation/driver-api/usb/ |
| D | bulk-streams.rst | 63 Stream ID 0 is reserved, and should not be used to communicate with devices. If
75 If a driver wishes to stop using streams to communicate with the device, it
|
| /linux-5.10/drivers/block/drbd/ |
| D | drbd_protocol.h | 323 /* we don't need it yet, but we may as well communicate it now */
332 * We don't need to communicate chunk/boundary/segment ... limits.
340 /* We may need to communicate integrity stuff at some point,
344 * Receiving side uses "blkdev_issue_discard()", no need to communicate
|
| /linux-5.10/drivers/net/arcnet/ |
| D | Kconfig | 28 arc0 device. You need to say Y here to communicate with
41 of NetBSD. You do not need to say Y here to communicate with
|
| /linux-5.10/drivers/staging/most/Documentation/ |
| D | driver_usage.txt | 66 Host wants to communicate with hardware via MediaLB.
69 Host wants to communicate with the hardware via I2C.
72 Host wants to communicate with the hardware via USB.
|
12345678910>>...21