Searched full:communicate (Results 1 – 25 of 1167) sorted by relevance
12345678910>>...47
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/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
|
| /kernel/linux/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
19 Any driver who wants to communicate with PMC using EEMI APIs use the
|
| /kernel/linux/linux-6.6/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
19 Any driver who wants to communicate with PMC using EEMI APIs use the
|
| /kernel/linux/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/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
|
| /kernel/linux/linux-6.6/drivers/crypto/marvell/octeontx/ |
| D | otx_cptvf_mbox.c | 169 * Communicate VQs size to PF to program CPT(0)_PF_Q(0-15)_CTL of the VF.
183 * Communicate VF group required to PF and get the VQ binded to that group
202 * Communicate VF group required to PF and get the VQ binded to that group
216 * Communicate to PF that VF is UP and running
228 * Communicate to PF that VF is DOWN and running
|
| /kernel/linux/linux-6.6/drivers/virt/coco/sev-guest/ |
| D | Kconfig | 9 SEV-SNP firmware provides the guest a mechanism to communicate with
12 userspace interface to communicate with the PSP to request the
|
| /kernel/linux/linux-6.6/Documentation/ABI/stable/ |
| D | sysfs-driver-w1_ds2438 | 6 Users: any user space application which wants to communicate with DS2438
13 Users: any user space application which wants to communicate with DS2438
|
| 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
|
| /kernel/linux/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
|
| /kernel/linux/linux-6.6/drivers/peci/controller/ |
| D | Kconfig | 12 connected to it, and communicate with them using PECI protocol.
28 to it and communicate with them using PECI protocol.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/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.
|
| /kernel/linux/linux-6.6/drivers/w1/masters/ |
| D | Kconfig | 12 Say Y here if you want to communicate with your 1-wire devices
48 Say Y here if you want to communicate with your 1-wire devices using
|
| /kernel/linux/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).
|
| /kernel/linux/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
|
| /kernel/linux/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
|
12345678910>>...47