| /openbmc/linux/sound/hda/ |
| H A D | hdac_component.c | 28 * driver that needs the interaction with graphics driver.
61 * needs the interaction with graphics driver.
116 * driver that needs the interaction with graphics driver.
151 * driver that needs the interaction with graphics driver.
247 * driver that needs the interaction with graphics driver.
272 * driver that needs the interaction with graphics driver.
327 * driver that needs the interaction with graphics driver.
|
| /openbmc/linux/Documentation/virt/kvm/arm/ |
| H A D | hyp-abi.rst | 7 This file documents the interaction between the Linux kernel and the
9 KVM). It doesn't cover the interaction of the kernel with the
11 hypervisor), or any hypervisor-specific interaction when the kernel is
|
| /openbmc/openbmc/poky/meta-yocto-bsp/lib/oeqa/controllers/ |
| H A D | grubtarget.py | 61 bb.fatal('Serial interaction failed: %s' % str(e))
69 bb.fatal('Serial interaction failed: %s' % str(e))
|
| H A D | beaglebonetarget.py | 89 bb.fatal('Serial interaction failed: %s' % str(e))
97 bb.fatal('Serial interaction failed: %s' % str(e))
|
| /openbmc/linux/Documentation/dev-tools/kunit/ |
| H A D | faq.rst | 54 - An integration test tests the interaction between a minimal set of components,
56 test to test the interaction between a driver and a piece of hardware, or to
57 test the interaction between the userspace libraries the kernel provides and
|
| /openbmc/linux/Documentation/sound/designs/ |
| H A D | tracepoints.rst | 34 interaction between applications and ALSA PCM core. Once decided, runtime of
123 Each driver can join in the interaction as long as it prepared for two stuffs
133 The driver can refers to result of the interaction in a callback of
|
| /openbmc/qemu/docs/devel/ |
| H A D | conflict-resolution.rst | 59 including unsolicited interaction with those enforcing the guidelines
60 and interaction on social media; being denied participation to in-person
|
| /openbmc/linux/drivers/net/dsa/hirschmann/ |
| H A D | hellcreek_hwtstamp.c | 50 /* Interaction with the timestamp hardware is prevented here. It is in hellcreek_set_hwtstamp_config()
105 * enable the interaction with the HW timestamping in hellcreek_set_hwtstamp_config()
381 * and the interaction with the HW timestamping is enabled. If not, stop in hellcreek_port_txtstamp()
424 * and the interaction with the HW timestamping is enabled. If not, stop in hellcreek_port_rxtstamp()
|
| /openbmc/openbmc/poky/meta/recipes-core/systemd/systemd/ |
| H A D | systemd-pager.sh | 2 # by busybox is not. This make many interaction with systemd pretty
|
| /openbmc/linux/drivers/misc/uacce/ |
| H A D | Kconfig | 6 without interaction with the kernel space in data path.
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | s390-drivers.rst | 12 for interaction with the hardware and interfaces for interacting with
74 Interaction with the driver core is done via the common I/O layer, which
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/mdbus2/ |
| H A D | mdbus2_git.bb | 1 SUMMARY = "Mickey's DBus Introspection and Interaction Utility V2"
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-pyproject-api_1.8.0.bb | 4 SUMMARY = "pyproject-api aims to abstract away interaction with pyproject.toml style projects in a …
|
| /openbmc/docs/ |
| H A D | Makefile | 7 tflags = -interaction=nonstopmode -halt-on-error
|
| /openbmc/linux/tools/testing/selftests/powerpc/pmu/ebb/ |
| H A D | reg_access_test.c | 14 * kernel interaction required.
|
| /openbmc/u-boot/drivers/tee/ |
| H A D | Kconfig | 28 Interaction from the U-Boot command line in possible via the
|
| /openbmc/linux/drivers/ntb/test/ |
| H A D | Kconfig | 26 to and from the window without additional software interaction.
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libnet/ |
| H A D | libnet-telnet-perl_3.05.bb | 6 ultimately means communicating with a program designed for human interaction. \
|
| /openbmc/linux/Documentation/scheduler/ |
| H A D | schedutil.rst | 152 interaction should be 'fast' and non-blocking. Schedutil supports
153 rate-limiting DVFS requests for when hardware interaction is slow and
|
| /openbmc/linux/Documentation/networking/ |
| H A D | operstates.rst | 92 contains link policy. This is needed for userspace interaction
145 IF_OPER_UP if userspace interaction is disabled. Otherwise
|
| /openbmc/linux/include/scsi/ |
| H A D | scsi_transport_fc.h | 210 * The transport fully manages all get functions w/o driver interaction.
216 * managed by the transport w/o driver interaction.
344 * w/o driver interaction.
350 * managed by the transport w/o driver interaction.
512 * The transport fully manages all get functions w/o driver interaction.
518 * managed by the transport w/o driver interaction.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-crypto/pkcs11-helper/ |
| H A D | pkcs11-helper_1.30.0.bb | 2 DESCRIPTION = "pkcs11-helper is a library that simplifies the interaction with PKCS \
|
| /openbmc/linux/arch/arm/mach-at91/ |
| H A D | sam_secure.c | 42 * OP-TEE kernel driver is not needed for the type of interaction made in sam_secure_init()
|
| /openbmc/openbmc/meta-openembedded/meta-xfce/recipes-xfce/libxfce4ui/ |
| H A D | libxfce4ui_4.20.0.bb | 1 SUMMARY = "Xfce4 Widget library and X Window System interaction"
|
| /openbmc/pldm/configurations/ |
| H A D | entityMap.json | 7 …rchitecture to the Redfish client, facilitating streamlined communication and system interaction.",
|