Searched full:relies (Results 1 – 25 of 554) sorted by relevance
12345678910>>...23
68 * data to determine board types and revisions. It relies on the86 * data to determine board types and revisions. It relies on the108 * data to determine board types and revisions. It relies on the
11 * qspinlock relies on atomic_*_release()/atomic_*_acquire() to be RCsc (or no15 * qspinlock relies on a far greater (compared to asm-generic/spinlock.h) set25 * qspinlock also heavily relies on mixed size atomic operations, in specific
6 * It relies on atomic_fetch_add() having well defined forward progress10 * It also relies on atomic_fetch_add() being safe vs smp_store_release() on a
9 * Some code relies on seeing MAX_DMA_ADDRESS though.
118 relies on or uses a fallback mechanism in userspace. If you need to124 old userspace may exist which relies upon it, and as such this133 driver which explicitly relies on this fallback mechanism. Only two
1 - This driver is too old and relies on a different API.
77 and whether the "opened"/"closed" events are paired fully relies on the90 are paired fully relies on the firmware implementation.
105 Supported only on arm64 CPUs and relies on Top Byte Ignore.124 Supported only on arm64 CPUs starting from ARMv8.5 and relies on
3 The watchdog functionality in Conexant Digicolor SoCs relies on the so called
108 * hypervisor. VMCI relies on it being 0, but this would be useful for other123 * (any process other than the hypervisor). VMCI relies on it being 2, but
8 relies on compile-time instrumentation, and uses a watchpoint-based sampling236 KCSAN relies on observing that two accesses happen concurrently. Crucially, we248 relies on compiler instrumentation and "soft watchpoints".252 watchpoints" are portability and greater flexibility. KCSAN then relies on the
19 /* sl811 relies on an external source of VBUS current */
33 The driver relies on device tree node to indicate the presence of SCPI
31 only measure voltages up to 3.3V and thus relies on voltage dividers.
24 It's worth to note, that since a part of this driver relies on the
464 * Relies on: in desc_read()497 * Relies on: in desc_read()513 * Relies on: in desc_read()653 * Relies on: in data_push_tail()691 * Relies on: in data_push_tail()718 * Relies on: in data_push_tail()818 * state. The implementation of prb_first_seq() relies on this. in desc_push_tail()849 * Relies on: in desc_push_tail()901 * Relies on: in desc_reserve()934 * Relies on: in desc_reserve()[all …]
84 /* This ldmia relies on the memory layout of the mpidr_hash struct */167 * This ldmia relies on the memory layout of the mpidr_hash
20 IOMMUFD will provide /dev/vfio/vfio instead of VFIO. This relies on
12 * - using a configuration table, like below, which relies on the EFI init code
7 It relies on transferring the wall clock and counter value from the
13 kprobe_multi_test # relies on fentry
29 /* kernel_fpu_begin/end() relies on patched alternative instructions. */ in fpu__init_check_bugs()
18 * actual physical address. Enough code relies on in __debug_virt_addr_valid()
3 # uImage build relies on mkimage being availble on your host for ARC target
29 * actual physical address. Enough code relies on __pa(MAX_DMA_ADDRESS) in __virt_addr_valid()
