Searched full:semantics (Results 1 – 25 of 512) sorted by relevance
12345678910>>...21
| /linux-5.10/drivers/net/wireless/ath/ath6kl/ |
| D | bmi.h | 54 * Semantics: Host is done using BMI
62 * Semantics: Host reads ATH6KL memory
73 * Semantics: Host writes ATH6KL memory
84 * Semantics: Causes ATH6KL to execute code
95 * Semantics: Set Target application starting address
104 * Semantics: Read a 32-bit Target SOC register.
114 * Semantics: Write a 32-bit Target SOC register.
126 * Semantics: Fetch the 4-byte Target information
141 * Semantics: Install a ROM Patch.
155 * Semantics: Uninstall a previously-installed ROM Patch,
[all …]
|
| /linux-5.10/Documentation/core-api/ |
| D | atomic_ops.rst | 2 Semantics and Behavior of Atomic and Bitmask Operations
28 :ref:`Documentation/core-api/local_ops.rst <local_ops>` for the semantics of
222 memory barrier semantics which satisfy the above requirements, that is
233 semantics are required.
244 Again, these primitives provide explicit memory barrier semantics around
251 provide explicit memory barrier semantics around the operation::
257 This primitive must provide explicit memory barrier semantics around
274 atomic_cmpxchg will only satisfy its atomicity semantics as long as all
281 The semantics for atomic_cmpxchg are the same as those defined for 'cas'
298 If a caller requires memory barrier semantics around an atomic_t
[all …]
|
| /linux-5.10/arch/sparc/include/uapi/asm/ |
| D | fcntl.h | 23 * Before Linux 2.6.33 only O_DSYNC semantics were implemented, but using
25 * for O_DSYNC semantics now, but using the correct symbolic name for it.
26 * This new value is used to request true Posix O_SYNC semantics. It is
28 * new headers get at least O_DSYNC semantics on older kernels.
|
| /linux-5.10/Documentation/locking/ |
| D | locktypes.rst | 86 Owner semantics
90 semantics:
140 rw_semaphore complies by default with the strict owner semantics, but there
193 semantics:
205 PREEMPT_RT kernel due to the PREEMPT_RT specific spinlock_t semantics.
227 The semantics of spinlock_t change with the state of PREEMPT_RT.
230 exactly the same semantics.
236 based on rt_mutex which changes the semantics:
253 PREEMPT_RT kernels preserve all other spinlock_t semantics:
312 implementation, thus changing semantics:
[all …]
|
| D | mutex-design.rst | 75 Semantics chapter
91 These semantics are fully enforced when CONFIG DEBUG_MUTEXES is enabled.
150 Unless the strict semantics of mutexes are unsuitable and/or the critical
|
| /linux-5.10/arch/alpha/include/uapi/asm/ |
| D | fcntl.h | 20 * Before Linux 2.6.33 only O_DSYNC semantics were implemented, but using
22 * for O_DSYNC semantics now, but using the correct symbolic name for it.
23 * This new value is used to request true Posix O_SYNC semantics. It is
25 * new headers get at least O_DSYNC semantics on older kernels.
|
| /linux-5.10/arch/mips/include/uapi/asm/ |
| D | fcntl.h | 24 * Before Linux 2.6.33 only O_DSYNC semantics were implemented, but using
26 * for O_DSYNC semantics now, but using the correct symbolic name for it.
27 * This new value is used to request true Posix O_SYNC semantics. It is
29 * new headers get at least O_DSYNC semantics on older kernels.
|
| /linux-5.10/include/linux/ |
| D | atomic.h | 16 * - Acquire: Provides ACQUIRE semantics, _acquire suffix.
17 * - Release: Provides RELEASE semantics, _release suffix.
21 * semantics apply only to the load and RELEASE semantics only to the
|
| /linux-5.10/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 11 # drivers if they share a common core requirement and use disjoint semantics to
18 # A perhaps not so obvious implication of this is that, if semantics on these
31 # due to the disjoint use of semantics on expressing each bell's relationship
43 # problem consisted on matching semantics with newly introduced features.
|
| D | kconfig-language.rst | 599 b) Match dependency semantics:
652 Work on kconfig is welcomed on both areas of clarifying semantics and on
659 Kconfig should have at least clear and well defined semantics which also
666 Semantics of Kconfig
673 semantics is welcomed. One project deduced Kconfig semantics through
675 the deduced semantics matches our intended Kconfig design goals.
677 Having well defined semantics can be useful for tools for practical
679 express in boolean abstraction of the inferred semantics of Kconfig to
688 only reverse engineering techniques have been used to deduce semantics from
701 abstraction the inferred semantics of Kconfig to translate Kconfig logic into
|
| /linux-5.10/Documentation/devicetree/bindings/mips/cavium/ |
| D | ciu3.txt | 13 The second cell indicates the triggering semantics, and may have a
14 value of either 4 for level semantics, or 1 for edge semantics.
|
| /linux-5.10/Documentation/ |
| D | atomic_bitops.txt | 36 SEMANTICS
66 Except for a successful test_and_set_bit_lock() which has ACQUIRE semantics and
67 clear_bit_unlock() which has RELEASE semantics.
|
| /linux-5.10/include/sound/ |
| D | snd_wavefront.h | 56 #define mpu_command_port base + 1 /* write semantics */
57 #define mpu_status_port base + 1 /* read semantics */
59 #define status_port base + 3 /* read semantics */
60 #define control_port base + 3 /* write semantics */
|
| /linux-5.10/include/asm-generic/bitops/ |
| D | instrumented-lock.h | 21 * This operation is atomic and provides release barrier semantics.
49 * This operation is atomic and provides acquire barrier semantics if
66 * This operation is atomic and provides release barrier semantics.
|
| D | lock.h | 14 * This operation is atomic and provides acquire barrier semantics if
38 * This operation is atomic and provides release barrier semantics.
|
| /linux-5.10/tools/include/uapi/asm-generic/ |
| D | fcntl.h | 66 * Before Linux 2.6.33 only O_DSYNC semantics were implemented, but using
68 * for O_DSYNC semantics now, but using the correct symbolic name for it.
69 * This new value is used to request true Posix O_SYNC semantics. It is
71 * new headers get at least O_DSYNC semantics on older kernels.
|
| /linux-5.10/include/uapi/asm-generic/ |
| D | fcntl.h | 67 * Before Linux 2.6.33 only O_DSYNC semantics were implemented, but using
69 * for O_DSYNC semantics now, but using the correct symbolic name for it.
70 * This new value is used to request true Posix O_SYNC semantics. It is
72 * new headers get at least O_DSYNC semantics on older kernels.
|
| /linux-5.10/Documentation/filesystems/ |
| D | virtiofs.rst | 28 guest and host to increase performance and provide semantics that are not
68 Mapping /dev/fuse to virtqueues requires solving differences in semantics
71 prioritize certain requests over others. Virtqueues have queue semantics and
|
| D | sharedsubtree.rst | 12 5) Detailed semantics
24 that got mounted recently. Shared subtree semantics provide the necessary
202 Apart from the above semantics this feature provides the
207 The above semantics allows a way to share mounts across
239 5) Detailed semantics
241 The section below explains the detailed semantics of
357 5b) Bind semantics
434 5c) Rbind semantics
471 5d) Move semantics
548 5e) Mount semantics
[all …]
|
| /linux-5.10/arch/riscv/include/asm/ |
| D | bitops.h | 152 * This operation is atomic and provides acquire barrier semantics.
166 * This operation is atomic and provides release barrier semantics.
180 * It does provide release barrier semantics so it can be used to unlock
187 * provide release semantics anyway.
|
| /linux-5.10/arch/arc/include/asm/ |
| D | barrier.h | 16 * - Operand supports fine grained load/store/load+store semantics
19 * - DMB guarantees SMP as well as local barrier semantics
|
| D | cmpxchg.h | 23 * LLOCK/SCOND themselves don't provide any such semantics in __cmpxchg()
74 * LLSC: only different in data-type, semantics are exactly same
76 * semantics, and this lock also happens to be used by atomic_*()
|
| /linux-5.10/include/uapi/linux/ |
| D | rseq.h | 66 * semantics. This field should only be read by the thread which
78 * Read by user-space with single-copy atomicity semantics. This
106 * atomicity semantics. This field should only be updated by the
|
| /linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | dev-encoder.rst | 164 follow standard semantics.
190 follow standard semantics.
199 follow standard semantics.
216 follow standard semantics.
226 follow standard semantics.
388 follow standard semantics.
421 follow standard semantics.
452 standard semantics.
545 per the standard semantics of the V4L2 control interface. The client may
552 semantics of the V4L2 control interface. If the client needs to apply the
|
| /linux-5.10/kernel/locking/ |
| D | qrwlock.c | 30 * so spin with ACQUIRE semantics until the lock is available in queued_read_lock_slowpath()
45 * The ACQUIRE semantics of the following spinning code ensure in queued_read_lock_slowpath()
|
12345678910>>...21