Searched full:variants (Results 1 – 25 of 1127) sorted by relevance
12345678910>>...46
| /kernel/linux/linux-4.19/Documentation/scheduler/ |
| D | completion.txt | 35 struct completion, the waiting part through a call to one of the variants of
94 _interruptible/_killable variants is not advisable as they will require
98 or _timeout variants of wait_for_completion().
132 uninterruptible. wait_for_completion() and its variants are only safe
138 As all variants of wait_for_completion() can (obviously) block for a long
142 Variants available:
145 The below variants all return status and this status should be checked in
181 Further variants include _killable which uses TASK_KILLABLE as the
189 The _io variants wait_for_completion_io() behave the same as the non-_io
190 variants, except for accounting waiting time as waiting on IO, which has
|
| /kernel/linux/linux-5.10/scripts/atomic/ |
| D | atomics.tbl | 3 # Where meta contains a string of variants to generate.
4 # Upper-case implies _{acquire,release,relaxed} variants.
9 # * R - return: returns base type (has _return variants)
10 # * F/f - fetch: returns base type (has fetch_ variants)
|
| /kernel/linux/linux-5.10/Documentation/scheduler/ |
| D | completion.rst | 39 - the waiting part through a call to one of the variants of wait_for_completion(),
79 variants of wait_for_completion(), as it must be assured that memory de-allocation
125 To emphasise this again: in particular when using some of the waiting API variants
127 _killable() and _interruptible()) variants, the wait might complete
174 uninterruptible. wait_for_completion() and its variants are only safe
180 As all variants of wait_for_completion() can (obviously) block for a long
185 wait_for_completion*() variants available:
188 The below variants all return status and this status should be checked in
228 Further variants include _killable which uses TASK_KILLABLE as the
235 The _io variants wait_for_completion_io() behave the same as the non-_io
[all …]
|
| /kernel/linux/linux-5.10/include/linux/mtd/ |
| D | spinand.h | 196 * There are 3 possible variants:
249 * struct spinand_op_variants - SPI NAND operation variants
250 * @ops: the list of variants for a given operation
251 * @nops: the number of variants
253 * Some operations like read-from-cache/write-to-cache have several variants
255 * cycles. This structure is a way to describe the different variants supported
297 * @op_variants: operations variants
298 * @op_variants.read_cache: variants of the read-cache operation
299 * @op_variants.write_cache: variants of the write-cache operation
300 * @op_variants.update_cache: variants of the update-cache operation
|
| /kernel/linux/linux-4.19/include/linux/mtd/ |
| D | spinand.h | 202 * struct spinand_op_variants - SPI NAND operation variants
203 * @ops: the list of variants for a given operation
204 * @nops: the number of variants
206 * Some operations like read-from-cache/write-to-cache have several variants
208 * cycles. This structure is a way to describe the different variants supported
249 * @op_variants: operations variants
250 * @op_variants.read_cache: variants of the read-cache operation
251 * @op_variants.write_cache: variants of the write-cache operation
252 * @op_variants.update_cache: variants of the update-cache operation
|
| /kernel/linux/linux-4.19/arch/arm/mach-bcm/ |
| D | Kconfig | 37 which includes the following variants:
47 which includes the following variants:
116 variants.
125 BCM21663 and BCM21664 variants.
|
| /kernel/linux/linux-5.10/arch/arm/mach-bcm/ |
| D | Kconfig | 36 which includes the following variants:
46 which includes the following variants:
113 variants.
121 BCM21663 and BCM21664 variants.
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | atomic.h | 11 * Relaxed variants of xchg, cmpxchg and some atomic operations.
13 * We support four variants:
35 * The idea here is to build acquire/release variants by adding explicit
|
| D | seqlock.h | 130 * Lockdep is never used in any for the raw write variants.
317 * @s: Pointer to seqcount_t or any of the seqcount_LOCKNAME_t variants
342 * @s: Pointer to seqcount_t or any of the seqcount_LOCKNAME_t variants
356 * @s: Pointer to seqcount_t or any of the seqcount_LOCKNAME_t variants
368 * @s: Pointer to seqcount_t or any of the seqcount_LOCKNAME_t variants
389 * @s: Pointer to seqcount_t or any of the seqcount_LOCKNAME_t variants
414 * @s: Pointer to seqcount_t or any of the seqcount_LOCKNAME_t variants
438 * @s: Pointer to seqcount_t or any of the seqcount_LOCKNAME_t variants
458 * @s: Pointer to seqcount_t or any of the seqcount_LOCKNAME_t variants
477 * @s: Pointer to seqcount_t or any of the seqcount_LOCKNAME_t variants
[all …]
|
| /kernel/linux/linux-4.19/Documentation/fb/ |
| D | s3fb.txt | 10 S3 Trio64 (and variants V+, UV+, V2/DX, V2/GX)
11 S3 Virge (and variants VX, DX, GX and GX2+)
26 * 4 bpp pseudocolor modes (with 18bit palette, two variants)
|
| /kernel/linux/linux-4.19/include/linux/mfd/ |
| D | stmpe.h | 38 * For registers whose locations differ on variants, the correct address is
101 * different variants. Indexed by one of STMPE_IDX_*.
103 * @num_gpios: number of gpios, differs for variants
|
| /kernel/linux/linux-4.19/Documentation/RCU/ |
| D | torture.txt | 41 done via timers. Defaults to "1" for variants of RCU that
42 permit this. (Or, more accurately, variants of RCU that do
156 variants.
160 variants.
167 synchronous variants.
171 synchronous, and polling variants.
174 along with expedited and synchronous variants.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | opencores,or1k-pic.txt | 5 - compatible : should be "opencores,or1k-pic-level" for variants with
6 level triggered interrupt lines, "opencores,or1k-pic-edge" for variants with
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/interrupt-controller/ |
| D | opencores,or1k-pic.txt | 5 - compatible : should be "opencores,or1k-pic-level" for variants with
6 level triggered interrupt lines, "opencores,or1k-pic-edge" for variants with
|
| /kernel/linux/linux-5.10/Documentation/fb/ |
| D | s3fb.rst | 10 S3 Trio64 (and variants V+, UV+, V2/DX, V2/GX)
11 S3 Virge (and variants VX, DX, GX and GX2+)
26 * 4 bpp pseudocolor modes (with 18bit palette, two variants)
|
| /kernel/linux/linux-5.10/include/crypto/ |
| D | chacha.h | 9 * The ChaCha paper specifies 20, 12, and 8-round variants. In general, it is
11 * variants can be needed in some performance-sensitive scenarios. The generic
12 * ChaCha code currently allows only the 20 and 12-round variants.
|
| /kernel/linux/linux-5.10/arch/xtensa/ |
| D | Makefile | 64 vardirs := $(patsubst %,arch/xtensa/variants/%/,$(variant-y))
73 …ldvar := $(shell test -e $(srctree)/arch/xtensa/variants/$(VARIANT)/Makefile && echo arch/xtensa/v…
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | mds.rst | 10 on internal buffers in Intel CPUs. The variants are:
73 All variants have the same mitigation strategy at least for the single CPU
166 and not by any other MDS variant. The other MDS variants cannot be
168 the Load Ports are shared. So on CPUs affected by other variants, the
187 The mitigation is hooked into all variants of halt()/mwait(), but does
|
| /kernel/linux/linux-4.19/Documentation/x86/ |
| D | mds.rst | 10 on internal buffers in Intel CPUs. The variants are:
73 All variants have the same mitigation strategy at least for the single CPU
166 and not by any other MDS variant. The other MDS variants cannot be
168 the Load Ports are shared. So on CPUs affected by other variants, the
187 The mitigation is hooked into all variants of halt()/mwait(), but does
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | timekeeping.rst | 12 The recommended simplest form returns an opaque ktime_t, with variants
62 For all of the above, there are variants that return the time in a
100 Some additional variants exist for more specialized cases:
137 These variants are safe to call from any context, including from
|
| /kernel/linux/linux-4.19/Documentation/core-api/ |
| D | timekeeping.rst | 12 The recommended simplest form returns an opaque ktime_t, with variants
62 For all of the above, there are variants that return the time in a
100 Some additional variants exist for more specialized cases:
133 These variants are safe to call from any context, including from
|
| /kernel/linux/linux-4.19/arch/xtensa/ |
| D | Makefile | 64 vardirs := $(patsubst %,arch/xtensa/variants/%/,$(variant-y))
73 …ldvar := $(shell test -e $(srctree)/arch/xtensa/variants/$(VARIANT)/Makefile && echo arch/xtensa/v…
|
| /kernel/linux/linux-5.10/include/linux/mfd/ |
| D | stmpe.h | 52 * For registers whose locations differ on variants, the correct address is
115 * different variants. Indexed by one of STMPE_IDX_*.
117 * @num_gpios: number of gpios, differs for variants
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | arm,versatile.yaml | 13 The ARM Versatile boards are two variants of ARM926EJ-S evaluation boards
39 0x10000000 in all the Versatile variants.
|
| /kernel/linux/linux-5.10/Documentation/ |
| D | asm-annotations.rst | 111 architecture specific ``__ALIGN`` bytes. There are also ``_NOALIGN`` variants
149 one. ``_NOALIGN`` variants exist too. The use is the same as for the ``FUNC``
194 * ``SYM_DATA`` and ``SYM_DATA_LOCAL`` are variants for simple, mostly one-line
211 symbol marked by them. They are used either in ``_LABEL`` variants of the
|
12345678910>>...46