| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-vfio-mdev | 72 Userspace applications interested in knowing the name of
85 Userspace applications interested in knowing the details of
|
| H A D | debugfs-ec | 8 Knowing the EC GPE one can watch the amount of HW events related to
|
| H A D | sysfs-platform-dell-privacy-wmi | 44 consumed by various applications interested in knowing the Privacy
|
| /openbmc/linux/tools/testing/selftests/rseq/ |
| H A D | rseq-s390.h | 58 * explicitly defined as additional exit points. Knowing all exit points is
85 * explicitly defined as additional exit points. Knowing all exit points is
|
| H A D | rseq-x86.h | 80 * explicitly defined as additional exit points. Knowing all exit points is
167 * explicitly defined as additional exit points. Knowing all exit points is
|
| H A D | rseq-ppc.h | 81 * explicitly defined as additional exit points. Knowing all exit points is
117 * explicitly defined as additional exit points. Knowing all exit points is
|
| /openbmc/linux/Documentation/devicetree/bindings/mailbox/ |
| H A D | amlogic,meson-gxbb-mhu.yaml | 17 received data. However, there is no specified way of knowing if the sent
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | access-marking.txt | 97 to generate false positives because KCSAN will have no way of knowing
121 to generate false positives because KCSAN will have no way of knowing
142 to generate false positives because KCSAN will have no way of knowing
159 because KCSAN will have no way of knowing that the resulting data race
|
| /openbmc/linux/arch/arm64/boot/dts/qcom/ |
| H A D | ipq9574-rdp449.dts | 53 * During regulator registration, kernel not knowing the initial voltage,
|
| H A D | ipq9574-rdp453.dts | 53 * During regulator registration, kernel not knowing the initial voltage,
|
| H A D | ipq9574-rdp454.dts | 53 * During regulator registration, kernel not knowing the initial voltage,
|
| H A D | ipq9574-rdp418.dts | 53 * During regulator registration, kernel not knowing the initial voltage,
|
| H A D | ipq9574-rdp433.dts | 57 * During regulator registration, kernel not knowing the initial voltage,
|
| /openbmc/linux/include/net/ |
| H A D | cls_cgroup.h | 62 * disable bh. Knowing this, it is possible to detect softirq based in task_get_classid()
|
| /openbmc/qemu/linux-user/loongarch64/ |
| H A D | vdso.ld | 33 * We can't prelink to any address without knowing something about
|
| /openbmc/qemu/linux-user/riscv/ |
| H A D | vdso.ld | 34 * We can't prelink to any address without knowing something about
|
| /openbmc/qemu/linux-user/aarch64/ |
| H A D | vdso.ld | 32 * We can't prelink to any address without knowing something about
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | kasan.txt | 54 requires knowing how much contiguous physical memory a system has _at compile
|
| /openbmc/linux/drivers/pwm/ |
| H A D | pwm-lpss-platform.c | 47 * knowing about this. On devices where the controller is unused in pwm_lpss_probe_platform()
|
| /openbmc/linux/drivers/leds/ |
| H A D | TODO | 41 Userspace is interested in knowing "this LED can produce arbitrary
|
| /openbmc/u-boot/doc/device-tree-bindings/gpio/ |
| H A D | gpio-pcf857x.txt | 8 low/high value, without knowing the last value written since the chip came out
|
| /openbmc/linux/drivers/gpu/drm/i915/gt/ |
| H A D | intel_gt_sysfs.c | 30 * We are interested at knowing from where the interface in intel_gt_sysfs_get_drvdata()
|
| /openbmc/linux/Documentation/devicetree/bindings/gpio/ |
| H A D | nxp,pcf8575.yaml | 18 input and reporting a low/high value, without knowing the last value written
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 110 | 69 # qemu is incapable of knowing the directory of the top image from the filename
|
| /openbmc/qemu/bsd-user/ |
| H A D | signal-common.h | 21 * emulation of the system call knowing that no signals can be taken
|