Searched full:semantics (Results 1 – 25 of 1128) sorted by relevance
12345678910>>...46
| /kernel/linux/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/linux-6.6/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 9 # kconfig semantics which are documented here. One known practical implication
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.
|
| /kernel/linux/linux-6.6/Documentation/ |
| D | atomic_bitops.txt | 36 SEMANTICS
63 Except for a successful test_and_set_bit_lock() which has ACQUIRE semantics,
64 clear_bit_unlock() which has RELEASE semantics and test_bit_acquire which has
65 ACQUIRE semantics.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/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.
|
| /kernel/linux/linux-6.6/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.
224 The semantics of spinlock_t change with the state of PREEMPT_RT.
227 exactly the same semantics.
233 based on rt_mutex which changes the semantics:
250 PREEMPT_RT kernels preserve all other spinlock_t semantics:
309 implementation, thus changing semantics:
[all …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/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.
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/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.
|
| /kernel/linux/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
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/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.
|
| /kernel/linux/linux-6.6/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
136 * user-space with single-copy atomicity semantics. This field should
144 * user-space with single-copy atomicity semantics. This field should
|
| /kernel/linux/linux-6.6/tools/testing/selftests/rseq/ |
| D | rseq-abi.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
152 * user-space with single-copy atomicity semantics. This field should
160 * user-space with single-copy atomicity semantics. This field should
|
| /kernel/linux/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.
|
| /kernel/linux/linux-6.6/Documentation/bpf/ |
| D | graph_ds_impl.rst | 7 implementation of semantics specific to those data structures.
15 semantics or APIs are made or implied here.
30 Luckily, some restrictions which necessitated the use of BPF map semantics are
33 and semantics more closely match those exposed to the rest of the kernel.
40 Unless otherwise stated, examples and semantics below apply to both graph data
50 for kfuncs, the API and semantics for these data structures can be evolved in
116 obvious. The verifier could enforce the same semantics as for ``bpf_obj_drop``,
|
| /kernel/linux/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 */
|
| /kernel/linux/linux-6.6/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 */
|
| /kernel/linux/linux-6.6/include/asm-generic/bitops/ |
| D | instrumented-lock.h | 21 * This operation is atomic and provides release barrier semantics.
51 * This operation is atomic and provides acquire barrier semantics if
68 * This operation is atomic and provides release barrier semantics.
|
12345678910>>...46