Searched full:communicate (Results 1 – 25 of 490) sorted by relevance
12345678910>>...20
| /Linux-v5.4/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-v5.4/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-v5.4/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-v5.4/samples/ |
| D | Kconfig | 73 communicate with a remote QRTR service, using QMI encoded messages.
80 to communicate with an AMP-configured remote processor over
100 the connector interface and a user space tool to communicate
|
| /Linux-v5.4/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-v5.4/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-v5.4/drivers/staging/speakup/ |
| D | TODO | 12 ports. Currently, we communicate directly with the hardware
16 communicate with USB devices. The current serial port handling code is
|
| /Linux-v5.4/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-v5.4/Documentation/networking/ |
| D | framerelay.txt | 9 net-tools archives is 'dlcicfg'. This program will communicate with the
14 The DLCI uses a number of function calls to communicate with the FRAD, all
|
| D | ipddp.txt | 10 networks can use to communicate via IP. AppleTalk-IP is simply IP datagrams
13 Through this driver you can either allow your Linux box to communicate
|
| /Linux-v5.4/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-v5.4/arch/um/drivers/ |
| D | Kconfig | 217 UMLs on a single host to communicate with each other, but not to
252 UMLs on a single host to communicate with each other and also
287 If you need UMLs on multiple physical hosts to communicate as if
288 they shared an Ethernet network, say Y. If you need to communicate
|
| /Linux-v5.4/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-v5.4/drivers/gpu/drm/ |
| D | drm_panel.c | 139 * the panel. After this has completed it is possible to communicate with any
159 * is usually no longer possible to communicate with the panel until another
197 * drivers. For smart panels it should still be possible to communicate with
|
| /Linux-v5.4/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-v5.4/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-v5.4/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.
|
| /Linux-v5.4/arch/powerpc/include/asm/ |
| D | icswx.h | 8 * instruction. This instruction is used to communicate with PowerPC
10 * to communicate with the coprocessor.
|
| /Linux-v5.4/drivers/net/appletalk/ |
| D | Kconfig | 9 AppleTalk is the protocol that Apple computers can use to communicate
36 AppleTalk is the protocol that Apple computers can use to communicate
|
| /Linux-v5.4/Documentation/driver-api/mei/ |
| D | iamt.rst | 6 Prominent usage of the Intel ME Interface is to communicate with Intel(R)
38 Applications running locally on the platform communicate with Intel AMT Release
|
12345678910>>...20
