Home
last modified time | relevance | path

Searched refs:ever (Results 1 – 25 of 148) sorted by relevance

123456

/Linux-v5.10/drivers/gpu/drm/nouveau/include/nvkm/subdev/bios/
Drammap.h19 u8 ever, u8 ehdr, u8 ecnt, u8 elen, int idx,
24 u8 ever, u8 ehdr, u8 ecnt, u8 elen, int idx,
/Linux-v5.10/Documentation/locking/
Dlockstat.rst56 - shortest (non-0) time we ever had to wait for a lock
58 - longest time we ever had to wait for a lock
69 - shortest (non-0) time we ever held the lock
71 - longest time we ever held the lock
Dlockdep-design.rst25 dependency just means the order ever happened. The validator maintains a
46 - 'ever held in STATE context'
47 - 'ever held as readlock in STATE context'
48 - 'ever held with STATE enabled'
49 - 'ever held as readlock with STATE enabled'
59 - 'ever used' [ == !unused ]
94 For a given STATE, whether the lock is ever acquired in that STATE
102 | ever in irq | '?' | '-' |
117 A lock is irq-safe means it was ever used in an irq context, while a lock
118 is irq-unsafe means it was ever acquired with irq enabled.
[all …]
Dspinlocks.rst43 example, internal driver data structures that nobody else ever touches).
118 This is useful if you know that the data in question is only ever
/Linux-v5.10/drivers/gpu/drm/nouveau/nvkm/subdev/bios/
Drammap.c147 u8 ever, u8 ehdr, u8 ecnt, u8 elen, int idx, u8 *ver, u8 *hdr) in nvbios_rammapSe() argument
151 *ver = ever; in nvbios_rammapSe()
191 u8 ever, u8 ehdr, u8 ecnt, u8 elen, int idx, in nvbios_rammapSp() argument
194 data = nvbios_rammapSe(bios, data, ever, ehdr, ecnt, elen, idx, ver, hdr); in nvbios_rammapSp()
/Linux-v5.10/arch/arm64/boot/dts/qcom/
Dsdm636-sony-xperia-ganges-mermaid.dts8 /* Mermaid uses sdm636, but it's different ever so slightly
/Linux-v5.10/Documentation/scheduler/
Dsched-arch.rst29 2. need_resched/TIF_NEED_RESCHED is only ever set, and will never
31 threads need only ever query need_resched, and may never set or
/Linux-v5.10/arch/x86/configs/
Dxen.config27 # move to generic config if it ever does.
/Linux-v5.10/drivers/staging/nvec/
DREADME11 that other Tegra boards (not yet mainlined, if ever) also use it.
/Linux-v5.10/Documentation/ABI/stable/
Dsysfs-devices-system-cpu20 If a process ever sets the DSCR (via direct access to the
/Linux-v5.10/arch/mips/sgi-ip27/
DTODO2 not to write to the IOC3 ever.
/Linux-v5.10/arch/alpha/
DKconfig.debug37 on the Alpha. The only time you would ever not say Y is to say M in
/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-class-devlink15 This file indicates if the device link will ever be
101 above. If this is ever the value, there's a bug in the kernel.
Dsysfs-block-dm38 bio-based DM devices so it will only ever report 0 for
/Linux-v5.10/security/keys/
DKconfig82 if the boot PCRs and other criteria match. Userspace will only ever
101 Userspace only ever sees/stores encrypted blobs.
/Linux-v5.10/arch/powerpc/lib/
Ddiv64.S33 andc r11,r6,r10 # ever be too large, only too small)
/Linux-v5.10/Documentation/filesystems/
Dfuse-io.rst31 uncached, but fully written pages). No READ requests are ever sent for writes,
/Linux-v5.10/Documentation/devicetree/bindings/display/rockchip/
Ddw_hdmi-rockchip.txt44 will switch to the unwedge pinctrl state for 10ms if it ever gets an
/Linux-v5.10/Documentation/devicetree/bindings/
Dcommon-properties.txt22 will ever be performed. Use this if the hardware "self-adjusts"
/Linux-v5.10/Documentation/usb/
Dmtouchusb.rst75 I am not a MicroTouch/3M employee, nor have I ever been. 3M does not support
/Linux-v5.10/arch/powerpc/kernel/vdso64/
Dsigtramp.S295 # we ever have some call chain that returns somewhere past the addi?
/Linux-v5.10/tools/kvm/kvm_stat/
Dkvm_stat.txt70 When used with option -L/--log-to-file, the header is only ever
/Linux-v5.10/arch/powerpc/boot/
Ddiv64.S33 andc r11,r6,r10 # ever be too large, only too small)
/Linux-v5.10/Documentation/process/
Dcode-of-conduct-interpretation.rst21 system kernel ever, and we do not want to do anything to cause the
22 quality of submission and eventual result to ever decrease.
/Linux-v5.10/Documentation/admin-guide/
Dunicode.rst46 two (in case 1024- or 2048-character fonts ever become necessary).
81 keyboard symbols that are unlikely to ever be added to Unicode proper

123456