| /openbmc/linux/Documentation/devicetree/bindings/gpio/ |
| H A D | rockchip,rk3328-grf-gpio.yaml | 12 for general purpose. It is manipulated by the GRF_SOC_CON10 register.
|
| /openbmc/qemu/linux-user/x86_64/ |
| H A D | vdso.ld | 50 * But since we manipulated the segment layout,
|
| /openbmc/qemu/linux-user/arm/ |
| H A D | vdso.ld | 43 * But since we manipulated the segment layout,
|
| /openbmc/qemu/linux-user/ppc/ |
| H A D | vdso-32.ld | 47 * But since we manipulated the segment layout,
|
| H A D | vdso-64.ld | 45 * But since we manipulated the segment layout,
|
| /openbmc/linux/drivers/i3c/master/mipi-i3c-hci/ |
| H A D | cmd.h | 15 * may be manipulated by the core code.
|
| /openbmc/qemu/linux-user/loongarch64/ |
| H A D | vdso.ld | 49 * But since we manipulated the segment layout,
|
| /openbmc/qemu/linux-user/riscv/ |
| H A D | vdso.ld | 50 * But since we manipulated the segment layout,
|
| /openbmc/linux/drivers/of/ |
| H A D | Kconfig | 73 On some platforms, the device tree can be manipulated at runtime.
|
| /openbmc/qemu/linux-user/s390x/ |
| H A D | vdso.ld | 48 * But since we manipulated the segment layout,
|
| /openbmc/qemu/linux-user/aarch64/ |
| H A D | vdso.ld | 48 * But since we manipulated the segment layout,
|
| /openbmc/qemu/linux-user/i386/ |
| H A D | vdso.ld | 53 * But since we manipulated the segment layout,
|
| /openbmc/linux/Documentation/admin-guide/gpio/ |
| H A D | gpio-mockup.rst | 8 using the standard GPIO character device interface as well as manipulated
|
| H A D | gpio-sim.rst | 8 using the standard GPIO character device interface as well as manipulated
|
| /openbmc/qemu/linux-user/hppa/ |
| H A D | vdso.ld | 55 But since we manipulated the segment layout,
|
| /openbmc/linux/Documentation/security/ |
| H A D | credentials.rst | 155 These are manipulated implicitly by changes to the traditional UNIX
156 credentials, but can also be manipulated directly by the ``capset()``
176 credentials are manipulated and inherited over certain operations such as
|
| /openbmc/phosphor-pid-control/ |
| H A D | ipmi.md | 16 mentioned above, these can be manipulated through normal IPMI commands, and are
|
| /openbmc/linux/arch/x86/coco/ |
| H A D | core.c | 170 * source of entropy that can be neither observed nor manipulated is in cc_random_init()
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/flite/flite/ |
| H A D | 0001-Remove-defining-const-as-nothing.patch | 45 -/* To allow some normally const fields to manipulated during building */
|
| /openbmc/linux/Documentation/livepatch/ |
| H A D | system-state.rst | 53 The state can be manipulated using two functions:
|
| /openbmc/linux/Documentation/virt/kvm/arm/ |
| H A D | hypercalls.rst | 18 pseudo-registers" that can be manipulated using the GET/SET_ONE_REG
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | quota.h | 59 * quota that is being manipulated (see above).
|
| /openbmc/linux/Documentation/locking/ |
| H A D | spinlocks.rst | 119 manipulated from a "process context", ie no interrupts involved.
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | fdt-fixup.txt | 124 it is safe to call it after the tree has already been manipulated.
|
| /openbmc/linux/tools/include/linux/ |
| H A D | compiler.h | 206 /* Make the optimizer believe the variable can be manipulated arbitrarily. */
|