Searched full:semantics (Results 1 – 25 of 628) sorted by relevance
12345678910>>...26
| /linux-6.12.1/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-6.12.1/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.
|
| D | kconfig-language.rst | 645 b) Match dependency semantics:
698 Work on kconfig is welcomed on both areas of clarifying semantics and on
705 Kconfig should have at least clear and well defined semantics which also
712 Semantics of Kconfig
719 semantics is welcomed. One project deduced Kconfig semantics through
721 the deduced semantics matches our intended Kconfig design goals.
722 Another project formalized a denotational semantics of a core subset of
725 Having well defined semantics can be useful for tools for practical
727 express in boolean abstraction of the inferred semantics of Kconfig to
731 The kismet tool, based on the semantics in [10]_, finds abuses of reverse
[all …]
|
| /linux-6.12.1/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.
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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-6.12.1/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-6.12.1/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-6.12.1/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
|
| D | mutex_types.h | 14 * Simple, straightforward mutexes with strict semantics:
28 * These semantics are fully enforced when DEBUG_MUTEXES is
|
| /linux-6.12.1/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-6.12.1/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
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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``,
|
| /linux-6.12.1/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-6.12.1/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.
|
| 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-6.12.1/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-6.12.1/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
203 Apart from the above semantics this feature provides the
208 The above semantics allows a way to share mounts across
240 5) Detailed semantics
242 The section below explains the detailed semantics of
358 5b) Bind semantics
435 5c) Rbind semantics
472 5d) Move semantics
549 5e) Mount semantics
[all …]
|
| /linux-6.12.1/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
|
| D | ext-ctrls-codec-stateless.rst | 31 Semantics". For further documentation, refer to the above
176 Semantics". For further documentation, refer to the above
280 List Semantics". For further documentation, refer to the above
315 :ref:`h264`, section 7.4.3 "Slice Header Semantics". For further
410 section 7.4.3.2 "Prediction Weight Table Semantics".
1594 See section '7.3.1 Tx mode semantics' of the :ref:`vp9` specification for more details.
1806 See section '7.2 Uncompressed header semantics' of the :ref:`vp9` specification
1836 See section '7.2.7 Interpolation filter semantics' of the :ref:`vp9` specification
1863 See section '7.3.6 Frame reference mode semantics' of the :ref:`vp9` specification for more details.
1998 '7.2.8 Loop filter semantics' of the :ref:`vp9` specification for more details.
[all …]
|
| /linux-6.12.1/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
|
| /linux-6.12.1/Documentation/driver-api/ |
| D | device-io.rst | 113 semantics. Using the relaxed read functions will provide significant
292 architecture-specific modes, with a shared set of semantics.
373 Like ioremap(), but explicitly requests non-posted write semantics. On some
374 architectures and buses, ioremap() mappings have posted write semantics, which
378 due to the posted write semantics, this is not the case with respect to other
379 devices. ioremap_np() explicitly requests non-posted semantics, which means
386 semantics and portable drivers should use an abstraction that automatically
400 Using ioremap_np() for PCI BARs will at best result in posted write semantics,
403 Note that non-posted write semantics are orthogonal to CPU-side ordering
|
| /linux-6.12.1/kernel/locking/ |
| D | qrwlock.c | 30 * so spin with ACQUIRE semantics until the lock is available in queued_read_lock_slowpath()
47 * The ACQUIRE semantics of the following spinning code ensure in queued_read_lock_slowpath()
|
12345678910>>...26