Home
last modified time | relevance | path

Searched full:relies (Results 1 – 25 of 494) sorted by relevance

12345678910>>...20

/linux/arch/mips/include/asm/octeon/
H A Dcvmx-helper-board.h68 * data to determine board types and revisions. It relies on the
86 * data to determine board types and revisions. It relies on the
108 * data to determine board types and revisions. It relies on the
/linux/include/asm-generic/
H A Dqspinlock.h11 * qspinlock relies on atomic_*_release()/atomic_*_acquire() to be RCsc (or no
15 * qspinlock relies on a far greater (compared to asm-generic/spinlock.h) set
25 * qspinlock also heavily relies on mixed size atomic operations, in specific
H A Dticket_spinlock.h6 * It relies on atomic_fetch_add() having well defined forward progress
10 * It also relies on atomic_fetch_add() being safe vs smp_store_release() on a
H A Ddma.h9 * Some code relies on seeing MAX_DMA_ADDRESS though.
/linux/Documentation/scheduler/
H A Dmembarrier.rst31 - arm64 relies on the full barrier implied by switch_to().
35 by mmdrop(), otherwise. On powerpc and riscv, switch_mm() relies on
/linux/drivers/base/firmware_loader/
H A DKconfig125 relies on or uses a fallback mechanism in userspace. If you need to
131 old userspace may exist which relies upon it, and as such this
140 driver which explicitly relies on this fallback mechanism. Only two
/linux/Documentation/firmware-guide/acpi/
H A Dacpi-lid.rst77 and whether the "opened"/"closed" events are paired fully relies on the
90 are paired fully relies on the firmware implementation.
/linux/lib/
H A DKconfig.kasan103 Supported only on arm64 CPUs and relies on Top Byte Ignore.
119 Supported only on arm64 CPUs starting from ARMv8.5 and relies on
H A DKconfig.kcsan21 data-race detector that relies on compile-time instrumentation.
203 Weak memory modeling relies on additional instrumentation and may
/linux/Documentation/dev-tools/
H A Dkcsan.rst8 relies on compile-time instrumentation, and uses a watchpoint-based sampling
246 KCSAN relies on observing that two accesses happen concurrently. Crucially, we
258 relies on compiler instrumentation and "soft watchpoints".
262 watchpoints" are portability and greater flexibility. KCSAN then relies on the
/linux/kernel/printk/
H A Dprintk_ringbuffer.c468 * Relies on: in desc_read()
501 * Relies on: in desc_read()
517 * Relies on: in desc_read()
657 * Relies on: in data_push_tail()
695 * Relies on: in data_push_tail()
722 * Relies on: in data_push_tail()
822 * state. The implementation of prb_first_seq() relies on this. in desc_push_tail()
853 * Relies on: in desc_push_tail()
905 * Relies on: in desc_reserve()
938 * Relies on: in desc_reserve()
[all …]
/linux/arch/arm/kernel/
H A Dsleep.S84 /* This ldmia relies on the memory layout of the mpidr_hash struct */
171 * This ldmia relies on the memory layout of the mpidr_hash
/linux/include/uapi/linux/
H A Dvm_sockets.h108 * hypervisor. VMCI relies on it being 0, but this would be useful for other
123 * (any process other than the hypervisor). VMCI relies on it being 2, but
/linux/include/linux/usb/
H A Dsl811.h19 /* sl811 relies on an external source of VBUS current */
/linux/Documentation/devicetree/bindings/watchdog/
H A Dcnxt,cx92755-wdt.yaml10 The watchdog functionality in Conexant Digicolor SoCs relies on the so called
/linux/Documentation/hwmon/
H A Dscpi-hwmon.rst33 The driver relies on device tree node to indicate the presence of SCPI
H A Dftsteutates.rst31 only measure voltages up to 3.3V and thus relies on voltage dividers.
/linux/drivers/ntb/hw/idt/
H A DKconfig24 It's worth to note, that since a part of this driver relies on the
/linux/drivers/firmware/efi/libstub/
H A Dscreen_info.c12 * - using a configuration table, like below, which relies on the EFI init code
/linux/arch/arc/boot/
H A DMakefile3 # uImage build relies on mkimage being available on your host for ARC target
/linux/arch/mips/mm/
H A Dphysaddr.c18 * actual physical address. Enough code relies on in __debug_virt_addr_valid()
/linux/arch/x86/kernel/fpu/
H A Dbugs.c32 /* kernel_fpu_begin/end() relies on patched alternative instructions. */ in fpu__init_check_bugs()
/linux/arch/arm/mm/
H A Dphysaddr.c29 * actual physical address. Enough code relies on __pa(MAX_DMA_ADDRESS) in __virt_addr_valid()
/linux/arch/x86/lib/
H A Dusercopy.c27 * For NMI context invocations this relies on the nested NMI work to allow
/linux/arch/riscv/include/asm/
H A Dmembarrier.h38 * CPU1; this means membarrier relies on switch_mm() to in membarrier_arch_switch_mm()

12345678910>>...20