| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | glossary.txt | 73 In a cycle, each CPU's ordering interacts with that of the next:
80 CPU 0's smp_mb() interacts with that of CPU 1, which interacts
81 with that of CPU 2, which in turn interacts with that of CPU 0
|
| /openbmc/linux/Documentation/devicetree/bindings/bus/ |
| H A D | xlnx,versal-net-cdx.yaml | 30 with which APU (Application Processor Unit) interacts to find out
48 phandle to the remoteproc_r5 rproc node using which APU interacts
|
| /openbmc/linux/drivers/infiniband/hw/vmw_pvrdma/ |
| H A D | Kconfig | 7 RDMA adapter. It interacts with the VMXNet3 driver to provide
|
| /openbmc/linux/drivers/cdx/controller/ |
| H A D | Kconfig | 15 CDX controller drives the CDX bus. It interacts with
|
| /openbmc/openbmc/meta-openembedded/meta-initramfs/conf/ |
| H A D | layer.conf | 13 # choosing carefully how this layer interacts with all of the
|
| /openbmc/openbmc/poky/bitbake/lib/layerindexlib/tests/testdata/layer4/conf/ |
| H A D | layer.conf | 11 # choosing carefully how this layer interacts with all of the
|
| /openbmc/linux/tools/perf/tests/workloads/ |
| H A D | datasym.c | 30 * longer a continuous repeating pattern that interacts in datasym()
|
| /openbmc/u-boot/doc/SPI/ |
| H A D | status.txt | 10 - sf.c: SPI flash interface, which interacts controller driver.
|
| /openbmc/qemu/docs/devel/ |
| H A D | index.rst | 17 :ref:`development_process` and how the community interacts. Please pay
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/conf/ |
| H A D | layer.conf | 23 # choosing carefully how this layer interacts with all of the
|
| /openbmc/linux/drivers/gpu/drm/i915/gt/ |
| H A D | intel_mocs.h | 23 * interacts with the contexts and the GmmLib interface.
|
| /openbmc/linux/arch/um/kernel/skas/ |
| H A D | syscall.c | 25 * went to sleep, even if said userspace interacts with the kernel in in handle_syscall()
|
| /openbmc/linux/drivers/phy/ti/ |
| H A D | Kconfig | 84 This driver interacts with the "OMAP Control PHY Driver" to power
|
| /openbmc/u-boot/include/zfs/ |
| H A D | dmu.h | 18 * The DMU also interacts with the SPA. That interface is described in
|
| /openbmc/linux/drivers/staging/greybus/Documentation/firmware/ |
| H A D | firmware-management | 49 The Firmware Management Protocol interacts with Userspace using the character
186 The Component Authentication Protocol interacts with Userspace using the
|
| /openbmc/google-misc/subprojects/ncsid/doc/ |
| H A D | ncsid_internals.md | 18 - **External Components**. These are external services/daemons NC-SIs interacts
|
| /openbmc/linux/include/linux/ |
| H A D | mount.h | 44 * flag, consider how it interacts with shared mounts.
|
| /openbmc/docs/designs/ |
| H A D | certificate-revocation-list.md | 37 daemon interacts with the OpenBMC certificate management architecture via DBus
|
| /openbmc/bmcweb/ |
| H A D | OWNERS | 19 # how it interacts with OpenBMC, and how the bmcweb implementation compares to
|
| /openbmc/intel-ipmi-oem/include/ |
| H A D | sensorutils.hpp | 244 …UKtrYKGhq-CloKFZoK2goaTkCWhqGBgpaWAkilpqYmQgBklmasjoKTJgDAECTH&lang=sage&interacts=eJyLjgUAARUAuQ== in getSensorAttributes()
282 …UKtrYKGhq-CloKFZoK2goaTkCWhqGBgpaWAkilpqYmQgBklmasDlAlAMB8JP0=&lang=sage&interacts=eJyLjgUAARUAuQ== in scaleIPMIValueFromDouble()
|
| /openbmc/phosphor-host-ipmid/dbus-sdr/ |
| H A D | sensorutils.cpp | 236 …UKtrYKGhq-CloKFZoK2goaTkCWhqGBgpaWAkilpqYmQgBklmasjoKTJgDAECTH&lang=sage&interacts=eJyLjgUAARUAuQ== in getSensorAttributes()
274 …UKtrYKGhq-CloKFZoK2goaTkCWhqGBgpaWAkilpqYmQgBklmasDlAlAMB8JP0=&lang=sage&interacts=eJyLjgUAARUAuQ== in scaleIPMIValueFromDouble()
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | cxl.rst | 54 of the AFU. Only userspace interacts directly with the AFU.
57 AFU needs. This is what the kernel interacts with. For example, if
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | sva.rst | 157 * For each device with which a process interacts, there must be
269 device. When removing pages, it interacts with the device to remove any
|
| /openbmc/linux/samples/bpf/ |
| H A D | xdp_fwd_kern.c | 107 * to understand how this XDP-prog interacts with network stack. in xdp_fwd_flags()
|
| /openbmc/openbmc/meta-openembedded/meta-oe/conf/ |
| H A D | layer.conf | 21 # choosing carefully how this layer interacts with all of the
|