Searched refs:cases (Results 1 – 25 of 252) sorted by relevance
1234567891011
1 Test cases for the devicetree.h API.
1 Test cases for the device API devicetree data.
1 Test cases for the devicetree.h extensions (GPIO, SPI, etc).
5 int "OS interrupt via which to deliver fuzz cases"8 In this sample, new fuzz cases are delivered to Zephyr
5 These samples demonstrate various use cases for the Thread protocol and underlying IEEE 802.15.4.
5 These samples demonstrate various Wi-Fi use cases for boards that support it.
13 # 32M should be enough for basic use-cases
10 - Target supporting I2C (with RTIO for the I2C_RTIO test-cases), e.g: mimxrt1010_evk.
10 * separate conflicting configuration options and create new test cases
9 These test cases cover:
20 it can be used to amortize write performance for some use cases.
16 in most cases we want to toggle the reset signals.
10 Some example use cases for snippets are:
35 These resources allow a good part of the ETSI test cases to be run51 the ETSI test cases:
24 Skip the tests that require it in such a cases.
13 cases, the mesh node can't rely on the Configuration Client to detect or determine
30 memory access is required in an ISR or for special use cases.
10 # In both cases, it is safe to do a separate_arguments on the argument.
43 In specific cases, this check might provide wrong verdict and should
11 the measurement. By default, module is using :c:func:`k_cycle_get_32` but in cases when higher
15 Xtensa architecture. This helps identify cases where cached and uncached
106 a per-test basis and is not meant to be used outside test cases.127 minimal mode for all test cases. For tests that need alternate150 running all test cases with User Mode and HW Stack Protection features162 for all test cases if the hardware supports it.
7 // Comments: Some false positives on empty default cases in switch statements.
87 /* Enable GPIO modules which are needed for below use cases:
21 cases, the digits of these sequences correspond to the numerical part of the kit
