| /openbmc/linux/Documentation/ABI/testing/ |
| H A 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
|
| /openbmc/linux/Documentation/driver-api/xilinx/ |
| H A 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
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | NPOSL-3.0 | 14 …communicate copies of the Original Work and Derivative Works to the public, with the proviso that …
34 …this License and all of its terms and conditions. If You distribute or communicate copies of the O…
48 …communicate this License without modification. Nothing in this License permits You to modify this …
58 …communicate the Original Work or Derivative Works thereof under this Non-Profit OSL 3.0 license on…
|
| H A D | CC-BY-2.5-AU | 37 …c. to publish, communicate to the public, distribute copies or records of, exhibit or display publ…
39 …d. to publish, communicate to the public, distribute copies or records of, exhibit or display publ…
54 …communicate to the public, distribute, publicly exhibit or display, publicly perform, or publicly …
56 …b. If you publish, communicate to the public, distribute, publicly exhibit or display, publicly pe…
58 …Except as otherwise agreed in writing by the Licensor, if You publish, communicate to the public, …
60 …Except as otherwise agreed in writing by the Licensor, if you publish, communicate to the public, …
96 …a. Each time You publish, communicate to the public, distribute or publicly digitally perform the …
98 …b. Each time You publish, communicate to the public, distribute or publicly digitally perform a De…
|
| H A D | UCL-1.0 | 13 …communicate copies of the Original Work and Derivative Works to the public, with the proviso that …
34 …this License and all of its terms and conditions. If You distribute or communicate copies of the O…
48 …communicate this License without modification. Nothing in this License permits You to modify this …
|
| H A D | OSL-3.0 | 9 …communicate copies of the Original Work and Derivative Works to the public, with the proviso that …
19 …this License and all of its terms and conditions. If You distribute or communicate copies of the O…
26 …communicate this License without modification. Nothing in this License permits You to modify this …
|
| H A D | TGPPL-1.0 | 23 c. to distribute or communicate copies of the Original Work and Derivative
25 Derivative Works that You distribute or communicate shall be licensed
111 distribute or communicate copies of the Original Work or a Derivative
169 Wilcox-O'Hearn. Permission is granted to copy, distribute, or communicate
173 distribute or communicate your modified version (the "Modified License")
|
| H A D | AFL-3.0 | 9 c) to distribute or communicate copies of the Original Work and Derivative Works to the public, und…
19 …this License and all of its terms and conditions. If You distribute or communicate copies of the O…
26 …communicate this License without modification. Nothing in this License permits You to modify this …
|
| /openbmc/linux/drivers/crypto/cavium/cpt/ |
| H A 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
|
| /openbmc/linux/drivers/crypto/marvell/octeontx/ |
| H A 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
|
| /openbmc/openbmc/meta-security/recipes-mac/smack/udp-smack-test/ |
| H A D | test_smack_udp_sockets.sh | 40 echo "Sockets with different labels should not communicate on udp"
58 echo "Sockets with different labels, but having rw access, should communicate on udp"
73 echo "Sockets with same labels should communicate on udp"
|
| /openbmc/openbmc/meta-security/recipes-mac/smack/tcp-smack-test/ |
| H A D | test_smack_tcp_sockets.sh | 41 echo "Sockets with different labels should not communicate on tcp"
59 echo "Sockets with different labels, but having rw access, should communicate on tcp"
74 echo "Sockets with same labels should communicate on tcp"
|
| /openbmc/linux/drivers/virt/coco/sev-guest/ |
| H A 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
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A 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
|
| H A 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
|
| /openbmc/docs/designs/ |
| H A D | bmc-reset-with-host-up.md | 68 communicate with the host
126 host has failed to respond to any of the different mechanisms to communicate
141 If the chassis power is on but the BMC is unable to communicate with the host
147 the host as-is, even if it is unable to communicate with the host over IPMI or
148 PLDM. It will log an error indicating it was unable to communicate with the host
|
| /openbmc/linux/drivers/peci/controller/ |
| H A D | Kconfig | 12 connected to it, and communicate with them using PECI protocol.
28 to it and communicate with them using PECI protocol.
|
| /openbmc/linux/drivers/usb/storage/ |
| H A 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.
|
| H A 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.
|
| H A 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.
|
| H A 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.
|
| /openbmc/ipmbbridge/ |
| H A D | README.md | 66 bmc-addr : This is BMC target address to communicate between BMC and device.
67 remote-addr : This is Remote/requester target address to communicate between BMC and device.
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/ |
| H A D | 0046-Corstone1000-Change-MMCOMM-buffer-location.patch | 6 MM Communicate buffer is accessed by normal world but at the moment
7 it's allocated in the secure ram. This moves mm communicate buffer
|
| /openbmc/linux/drivers/w1/masters/ |
| H A 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
|
| /openbmc/linux/include/linux/ |
| H A D | psp-tee.h | 18 * and the API exported by AMD Secure Processor driver to communicate with
70 * which it can communicate.
|