| /kernel/linux/linux-4.19/net/bluetooth/ |
| D | Kconfig | 102 cases are run first thing at module load time. When the Bluetooth
103 subsystem is compiled into the kernel image, then the test cases
107 bool "ECDH test cases"
110 Run test cases for ECDH cryptographic functionality used by the
114 bool "SMP test cases"
117 Run test cases for SMP cryptographic functionality, including both
|
| /kernel/linux/linux-5.10/tools/testing/selftests/tc-testing/ |
| D | README | 59 cases. To disable execution within the namespace, pass the -N option
77 future). A test suite has one or more test cases in it.
106 executed as part of the test. More will be added as test cases require.
111 The NAMES values are used to substitute into the commands in the test cases.
131 Execute test cases that use a physical device, where
137 select which test cases: files plus directories; filtered by categories
150 Execute the specified test cases with specified IDs
153 select action to perform on selected test cases
155 -l, --list List all test cases, or those only within the
157 -s, --show Display the selected test cases
[all …]
|
| D | tdc.py | 68 Get all required plugins from the list of test cases and return
86 Get all required plugins from the list of test cases and load any plugin
431 Open the JSON file containing the test cases and return them
468 'selection', 'select which test cases: ' +
471 'action', 'select action to perform on selected test cases')
486 help='Execute the specified test cases with specified IDs')
489 help='List all test cases, or those only within the specified category')
492 help='Display the selected test cases')
495 help='Generate ID numbers for new test cases')
504 help='Execute test cases that use a physical device, ' +
[all …]
|
| /kernel/linux/linux-5.10/net/bluetooth/ |
| D | Kconfig | 119 cases are run first thing at module load time. When the Bluetooth
120 subsystem is compiled into the kernel image, then the test cases
124 bool "ECDH test cases"
127 Run test cases for ECDH cryptographic functionality used by the
131 bool "SMP test cases"
134 Run test cases for SMP cryptographic functionality, including both
|
| /kernel/linux/linux-4.19/tools/testing/selftests/tc-testing/ |
| D | README | 73 future). A test suite has one or more test cases in it.
102 executed as part of the test. More will be added as test cases require.
107 The NAMES values are used to substitute into the commands in the test cases.
131 select which test cases: files plus directories; filtered by categories
144 Execute the specified test cases with specified IDs
147 select action to perform on selected test cases
149 -l, --list List all test cases, or those only within the
151 -s, --show Display the selected test cases
152 -i, --id Generate ID numbers for new test cases
242 Jamal Hadi Salim, for providing valuable test cases
|
| /kernel/linux/linux-5.10/scripts/coccinelle/misc/ |
| D | cond_no_effect.cocci | 5 // There can be false positives in cases where the positional
7 // is a placeholder for not yet handled cases.
17 // the two known cases are:
38 // All other cases look like bugs or at least lack of documentation
|
| /kernel/linux/linux-4.19/scripts/coccinelle/misc/ |
| D | cond_no_effect.cocci | 4 // There can be false positives in cases where the positional
6 // is a placeholder for not yet handled cases.
16 // the two known cases are:
37 // All other cases look like bugs or at least lack of documentation
|
| /kernel/linux/linux-4.19/tools/testing/selftests/tc-testing/creating-testcases/ |
| D | AddingTestCases.txt | 1 tdc - Adding test cases for tdc
5 ADDING TEST CASES
10 template.json for the required JSON format for test cases.
18 If you wish to store your custom test cases elsewhere, be sure to run
76 in the test cases. tdc will output a series of TAP results for the skipped
|
| /kernel/linux/linux-4.19/Documentation/RCU/ |
| D | rcuref.txt | 7 those unusual cases where percpu-ref would consume too much memory,
73 update (write) stream. In such cases, atomic_inc_not_zero() might be
75 use atomic_inc() in such cases.
78 search_and_reference() code path. In such cases, the
117 In cases where delete() can sleep, synchronize_rcu() can be called from
|
| /kernel/linux/linux-5.10/tools/testing/selftests/tc-testing/creating-testcases/ |
| D | AddingTestCases.txt | 1 tdc - Adding test cases for tdc
5 ADDING TEST CASES
10 template.json for the required JSON format for test cases.
18 If you wish to store your custom test cases elsewhere, be sure to run
81 in the test cases. tdc will output a series of TAP results for the skipped
|
| /kernel/linux/linux-5.10/tools/usb/ |
| D | hcd-tests.sh | 37 # NOTE: the 'in' and 'out' cases are usually bulk, but can be
106 echo '** Control test cases:'
124 echo '** Host Write (OUT) test cases:'
155 echo '** Host ISOCHRONOUS Write (OUT) test cases:'
182 echo '** Host Read (IN) test cases:'
208 echo '** Host ISOCHRONOUS Read (IN) test cases:'
|
| /kernel/linux/linux-4.19/tools/usb/ |
| D | hcd-tests.sh | 37 # NOTE: the 'in' and 'out' cases are usually bulk, but can be
106 echo '** Control test cases:'
124 echo '** Host Write (OUT) test cases:'
155 echo '** Host ISOCHRONOUS Write (OUT) test cases:'
182 echo '** Host Read (IN) test cases:'
208 echo '** Host ISOCHRONOUS Read (IN) test cases:'
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iommu/ |
| D | iommu.txt | 44 the specific IOMMU. Below are a few examples of typical use-cases:
51 In such cases the number of cells will usually be 1 as in the next case.
53 in order to enable translation for a given master. In such cases the single
54 address cell corresponds to the master device's ID. In some cases more than
62 Note that these are merely examples and real-world use-cases may use different
85 have a means to turn off translation. But it is invalid in such cases to
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/iommu/ |
| D | iommu.txt | 44 the specific IOMMU. Below are a few examples of typical use-cases:
51 In such cases the number of cells will usually be 1 as in the next case.
53 in order to enable translation for a given master. In such cases the single
54 address cell corresponds to the master device's ID. In some cases more than
62 Note that these are merely examples and real-world use-cases may use different
85 have a means to turn off translation. But it is invalid in such cases to
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/slimbus/ |
| D | bus.txt | 18 In some cases it may be necessary to describe non-probeable device
20 such cases, child nodes for those devices will be present as
28 Instance ID Is for the cases where multiple Devices of the
|
| /kernel/linux/linux-5.10/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 79 from the current review queue. Likewise for cases where patches would
198 at the end of the week. In some cases pull requests could additionally
217 Q: Verifier changes and test cases
219 Q: I made a BPF verifier change, do I need to add test cases for
223 it is absolutely necessary to add test cases to the BPF kernel
228 cases, including a lot of corner cases that LLVM BPF back end may
229 generate out of the restricted C code. Thus, adding test cases is
231 affect prior use-cases. Thus, treat those test cases as: verifier
244 The more test cases we add to BPF selftests, the better the coverage
311 commit is in net-next (or in some cases bpf-next). The ``Fixes:`` tag is
[all …]
|
| /kernel/linux/linux-4.19/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 84 from the current review queue. Likewise for cases where patches would
203 at the end of the week. In some cases pull requests could additionally
222 Q: Verifier changes and test cases
224 Q: I made a BPF verifier change, do I need to add test cases for
228 it is absolutely necessary to add test cases to the BPF kernel
233 cases, including a lot of corner cases that LLVM BPF back end may
234 generate out of the restricted C code. Thus, adding test cases is
236 affect prior use-cases. Thus, treat those test cases as: verifier
249 The more test cases we add to BPF selftests, the better the coverage
316 commit is in net-next (or in some cases bpf-next). The ``Fixes:`` tag is
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/slimbus/ |
| D | bus.txt | 18 In some cases it may be necessary to describe non-probeable device
20 such cases, child nodes for those devices will be present as
28 Instance ID Is for the cases where multiple Devices of the
|
| /kernel/linux/linux-5.10/Documentation/RCU/ |
| D | rcuref.rst | 11 those unusual cases where percpu-ref would consume too much memory,
82 update (write) stream. In such cases, atomic_inc_not_zero() might be
84 use atomic_inc() in such cases.
87 search_and_reference() code path. In such cases, the
139 In cases where delete() can sleep, synchronize_rcu() can be called from
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | device-io.rst | 78 writes have occurred in the specific cases the author cares. This kind
80 cases, the read used to flush the device may be expected to fail (if the
109 complete. In many cases, however, the driver may want to indicate that the
112 these cases, although only some platforms will honor the relaxed
115 provides examples of how to use readX_relaxed(). In many cases, a majority
|
| /kernel/linux/linux-5.10/arch/mips/math-emu/ |
| D | sp_maddf.c | 46 * Handle the cases when at least one of x, y or z is a NaN. in _sp_maddf()
64 /* ZERO z cases are handled separately below */ in _sp_maddf()
84 * Cases of addition of infinities with opposite signs in _sp_maddf()
105 /* Handle cases +0 + (-0) and similar ones. */ in _sp_maddf()
108 * Cases of addition of zeros of equal signs in _sp_maddf()
|
| /kernel/linux/linux-4.19/tools/testing/selftests/rcutorture/doc/ |
| D | TINY_RCU.txt | 1 This document gives a brief rationale for the TINY_RCU test cases.
19 In common code tested by TREE_RCU test cases.
|
| /kernel/linux/linux-5.10/tools/testing/selftests/rcutorture/doc/ |
| D | TINY_RCU.txt | 1 This document gives a brief rationale for the TINY_RCU test cases.
19 In common code tested by TREE_RCU test cases.
|
| /kernel/linux/linux-5.10/Documentation/powerpc/ |
| D | ultravisor.rst | 312 Use cases
386 Use cases
437 Use cases
483 Use cases
544 Use cases
593 Use cases
638 Use cases
673 Use cases
720 Use cases
770 Use cases
[all …]
|
| /kernel/linux/linux-5.10/include/dt-bindings/mux/ |
| D | mux.h | 5 * Most Multiplexer bindings specify an idle state. In most cases, the
6 * multiplexer can be left as is when idle, and in some cases it can
|