Home
last modified time | relevance | path

Searched refs:assume (Results 1 – 25 of 213) sorted by relevance

123456789

/Linux-v5.4/Documentation/devicetree/bindings/regulator/
Dtps62360-regulator.txt15 If this property is missing, then assume that there is no GPIO
18 If this property is missing, then assume that there is no GPIO
21 If this property is missing, then assume the state as low (0).
23 If this property is missing, then assume the state as low (0).
/Linux-v5.4/tools/testing/selftests/rcutorture/formal/srcu-cbmc/src/
Dassume.h7 #define assume(x) \ macro
14 #define assume(x) __CPROVER_assume(x) macro
Dsimple_sync_srcu.c46 assume(try_check_zero(sp, idx, trycount)); in synchronize_srcu()
50 assume(try_check_zero(sp, idx^1, trycount)); in synchronize_srcu()
Dpreempt.c66 assume(thread_cpu_id >= 0); in preempt_disable()
67 assume(thread_cpu_id < NR_CPUS); in preempt_disable()
Dlocks.h85 assume(lock_impl_trylock(lock)); in lock_impl_lock()
194 assume(prev_count); in wait_for_completion()
Dmisc.h25 #define udelay(x) assume(0)
/Linux-v5.4/arch/m68k/ifpsp060/
Dos.S152 clr.l %d1 | assume success
187 clr.l %d1 | assume success
223 clr.l %d1 | assume success
245 clr.l %d1 | assume success
267 clr.l %d1 | assume success
291 clr.l %d1 | assume success
/Linux-v5.4/arch/unicore32/kernel/
Ddebug-macro.S51 @ However, now we assume UART0 is active: epip4d
52 @ We assume r1 and r2 can be clobbered.
/Linux-v5.4/arch/mips/kernel/
Dr2300_fpu.S68 li v0, 0 # assume success
102 li v0, 0 # assume success
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-firmware-gsmi42 "factory defaults". Callers should assume that
57 Callers should assume that a reboot is needed
/Linux-v5.4/Documentation/admin-guide/device-mapper/
Dzero.rst21 desired size of the sparse device. For this example, we'll assume a 10TB
29 space available to the sparse device. For this example, we'll assume /dev/sdb1
/Linux-v5.4/Documentation/devicetree/bindings/net/
Dhisilicon-hns-nic.txt27 LAN Switch while the CPU side assume itself have one single NIC connect to
54 ports connected to a LAN Switch while the CPU side assume itself have one
/Linux-v5.4/Documentation/driver-api/driver-model/
Ddesign-patterns.rst16 While the kernel contains a few device drivers that assume that they will
17 only be probed() once on a certain system (singletons), it is custom to assume
/Linux-v5.4/Documentation/devicetree/bindings/net/wireless/
Dti,wlcore.txt26 Note: the *-clock-frequency properties assume internal clocks. In case of external
/Linux-v5.4/arch/arm/include/debug/
Dsa1100.S25 @ We assume r1 can be clobbered.
/Linux-v5.4/Documentation/devicetree/bindings/gpio/
Dgpio-mm-lantiq.txt19 - lantiq,shadow : The default value that we shall assume as already set on the
Dgpio-stp-xway.txt18 - lantiq,shadow : The default value that we shall assume as already set on the
/Linux-v5.4/drivers/memstick/core/
DKconfig11 If you say Y here, the MemoryStick layer will assume that all
/Linux-v5.4/arch/arm/kernel/
Dhead.S506 bne __fixup_smp_on_up @ no, assume UP
514 reteq lr @ yes, assume SMP
519 bne __fixup_smp_on_up @ no, assume UP
/Linux-v5.4/Documentation/devicetree/bindings/usb/
Dusb3503.txt25 REFCLK signal and assume that a value from the primary reference
/Linux-v5.4/Documentation/crypto/
Ddescore-readme.txt182 1) i assume everything is byte addressable, although i don't actually
184 i assume word pointers can be freely cast to and from char pointers.
189 i assume sizeof(word) == 4 EVERYWHERE.
238 i assume that the use of a constant is more expensive than using a register:
250 i assume that indexing is cheaper or equivalent to auto increment/decrement,
254 i assume that addresses can be cheaply formed from two registers,
/Linux-v5.4/Documentation/devicetree/bindings/arm/
Dcoresight-cpu-debug.txt29 - cpu : the CPU phandle the debug module is affined to. Do not assume it
/Linux-v5.4/Documentation/devicetree/bindings/pmem/
Dpmem-region.txt40 If this property is absent then the OS must assume that the region
/Linux-v5.4/Documentation/devicetree/bindings/mmc/
Dsynopsys-dw-mshc.txt33 we'd assume that the write protect is hooked up directly to the
54 ciu clock is missing we'll just assume that the clock is running at
/Linux-v5.4/arch/arm/boot/dts/
Dsocfpga_arria10_socdk.dtsi74 * These skews assume the user's FPGA design is adding 600ps of delay

123456789