Home
last modified time | relevance | path

Searched full:communicate (Results 1 – 25 of 682) sorted by relevance

12345678910>>...28

/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-driver-w1_therm13 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-6.12.1/Documentation/driver-api/xilinx/
Deemi.rst8 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
/linux-6.12.1/drivers/crypto/cavium/cpt/
Dcptvf_mbox.c104 * 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-6.12.1/drivers/crypto/marvell/octeontx/
Dotx_cptvf_mbox.c169 * 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
/linux-6.12.1/drivers/w1/masters/
DKconfig23 Say Y here if you want to communicate with your 1-wire devices
59 Say Y here if you want to communicate with your 1-wire devices using
85 Say Y here if you want to communicate with your 1-wire devices using
/linux-6.12.1/drivers/firmware/efi/stmm/
Dmm_communication.h129 * struct smm_variable_access - Used to communicate with StMM by
161 * struct smm_variable_getnext - Used to communicate with StMM for
179 * struct smm_variable_query_info - Used to communicate with StMM for
220 * struct smm_variable_var_check_property - Used to communicate variable
/linux-6.12.1/drivers/virt/coco/sev-guest/
DKconfig10 SEV-SNP firmware provides the guest a mechanism to communicate with
13 userspace interface to communicate with the PSP to request the
/linux-6.12.1/Documentation/ABI/stable/
Dsysfs-driver-w1_ds24386 Users: any user space application which wants to communicate with DS2438
13 Users: any user space application which wants to communicate with DS2438
Dsysfs-driver-w1_ds28e046 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-6.12.1/drivers/peci/controller/
DKconfig12 connected to it, and communicate with them using PECI protocol.
28 to it and communicate with them using PECI protocol.
/linux-6.12.1/drivers/soc/apple/
DKconfig16 communicate with those.
28 for the protocol library used to communicate with those. It is used
/linux-6.12.1/drivers/usb/storage/
Dscsiglue.h10 * describes in detail the protocol used to communicate with such
18 * that they are used to communicate wait, failed and OK on commands.
Dinitializers.h9 * describes in detail the protocol used to communicate with such
17 * that they are used to communicate wait, failed and OK on commands.
Dprotocol.h10 * describes in detail the protocol used to communicate with such
18 * that they are used to communicate wait, failed and OK on commands.
Ddebug.h13 * describes in detail the protocol used to communicate with such
21 * that they are used to communicate wait, failed and OK on commands.
Dtransport.h10 * describes in detail the protocol used to communicate with such
18 * that they are used to communicate wait, failed and OK on commands.
Dinitializers.c9 * describes in detail the protocol used to communicate with such
17 * that they are used to communicate wait, failed and OK on commands.
/linux-6.12.1/drivers/gpu/drm/xe/abi/
Dguc_relay_communication_abi.h21 * To communicate with the PF driver, VF's drivers use `VF2GUC_RELAY_TO_PF`_
31 * Likewise, to communicate with the VF drivers, PF driver use
80 * Function (VF) drivers to communicate using `GuC Relay Communication`_.
/linux-6.12.1/include/linux/
Dpsp-tee.h18 * and the API exported by AMD Secure Processor driver to communicate with
70 * which it can communicate.
/linux-6.12.1/samples/
DKconfig121 communicate with a remote QRTR service, using QMI encoded messages.
128 to communicate with an AMP-configured remote processor over
148 the connector interface and a user space tool to communicate
/linux-6.12.1/include/uapi/linux/
Dmei.h16 * will communicate with the associated FW client.
101 * and write will communicate with the associated FW client
/linux-6.12.1/Documentation/driver-api/md/
Dmd-cluster.rst60 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-6.12.1/Documentation/driver-api/usb/
Dbulk-streams.rst63 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-6.12.1/drivers/block/drbd/
Ddrbd_protocol.h325 /* we don't need it yet, but we may as well communicate it now */
334 * We don't need to communicate chunk/boundary/segment ... limits.
342 /* We may need to communicate integrity stuff at some point,
346 * Receiving side uses "blkdev_issue_discard()", no need to communicate
/linux-6.12.1/drivers/net/arcnet/
DKconfig28 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

12345678910>>...28