| /Zephyr-latest/tests/ztest/ztest_param/pytest/ |
| D | test_parameters.py | 11 assert "PASS - test_int_param" in output, f"Expected 'PASS - test_int_param' but got {lines}"
12 assert "PASS - test_dummy" in output, f"Expected 'PASS - test_dummy' but got {lines}"
13 …assert "PASS - test_string_param" in output, f"Expected 'PASS - test_string_param' but got {lines}"
19 assert "PASS - test_dummy" in output, f"Expected 'PASS - test_dummy' but got {lines}"
26 …assert pass_dummy_count == 2, f"Expected 2 occurrences of 'PASS - test_dummy' but found {pass_dumm…
33 …count == 2, f"Expected 2 occurrences of 'TESTSUITE ztest_params succeeded' but found {pass_ztest_p…
39 …E ztest_params succeeded" in output, f"Expected 'TESTSUITE ztest_params succeeded' but got {lines}"
|
| /Zephyr-latest/dts/bindings/regulator/ |
| D | regulator.yaml | 60 at boot but shouldn't prevent it from being turned off later.
152 indicates that protection should be enabled but limit setting can be
161 should be enabled but limit setting can be omitted.
167 still to be functional but approaching limit where it gets damaged.
169 detection and value '1' indicates that detection should be enabled but
177 indicates that protection should be enabled but limit setting can be
186 should be enabled but limit setting can be omitted. Limit is given as
193 still to be functional but approaching limit where it gets damaged.
195 detection and value '1' indicates that detection should be enabled but
204 value '1' indicates that protection should be enabled but limit setting
[all …]
|
| /Zephyr-latest/soc/snps/qemu_arc/ |
| D | Kconfig.defconfig | 21 # Technically ARC HS supports MPUv3, but not v2. But given MPUv3
22 # is the same as v2 but with minimal region size of 32 bytes, we
|
| /Zephyr-latest/lib/os/ |
| D | Kconfig.cbprintf | 17 bool "Space-optimized but feature-limited"
23 footprint, but provides fewer capabilities.
51 This will decrease stack space, but affects conversion of any type
52 with more than 32 bits. This includes not only intmax_t but any
60 With CBPRINTF_NANO all conversions will be attempted but values that
73 requirements slightly, but increases code size significantly.
82 added in C99, but the output is not easily understood so it rarely
85 Selecting this adds support for the conversion, but increases the
164 to determine the types of arguments, but instead, each argument is
|
| /Zephyr-latest/arch/posix/ |
| D | Linux.aarch64.cmake | 4 # distributions. Userspace is (generally) either 32-bit or 64-bit but not
20 "CONFIG_64BIT=y but this Aarch64 machine has a 32-bit userspace.\n"
29 "CONFIG_64BIT=n but this Aarch64 machine has a 64-bit userspace.\n"
|
| /Zephyr-latest/tests/drivers/stepper/drv8424/api/src/ |
| D | main.c | 78 zassert_equal(res, 4, "Micro step resolution not set correctly, should be %d but is %d", 4, in ZTEST_F()
87 zassert_equal(ret, -EINVAL, "Command should fail with error %d but returned %d", -EINVAL, in ZTEST_F()
96 zassert_equal(pos, 100u, "Actual position should be %u but is %u", 100u, pos); in ZTEST_F()
126 "Actual position should not have changed from %d but is %d", position_1, in ZTEST_F()
161 "Actual position should not have changed from %d but is %d", position_1, in ZTEST_F()
182 zassert_equal(pos, 50u, "Target position should be %d but is %d", 50u, pos); in ZTEST_F()
202 zassert_equal(pos, -50, "Target position should be %d but is %d", -50, pos); in ZTEST_F()
222 zassert_equal(pos, 0, "Target position should not have changed from %d but is %d", 0, pos); in ZTEST_F()
234 zassert_not_equal(ret, 0, "Command should fail with an error code, but returned 0"); in ZTEST_F()
237 zassert_equal(pos, 0, "Target position should not have changed from %d but is %d", 0, pos); in ZTEST_F()
[all …]
|
| /Zephyr-latest/lib/posix/options/ |
| D | spinlock.c | 67 /* The spinlock claims to be initialized but is actually not */ in get_posix_spinlock()
81 /* not specified as part of POSIX but this is the Linux behavior */ in pthread_spin_init()
103 /* not specified as part of POSIX but this is the Linux behavior */ in pthread_spin_destroy()
121 /* not specified as part of POSIX but this is the Linux behavior */ in pthread_spin_lock()
138 /* not specified as part of POSIX but this is the Linux behavior */ in pthread_spin_trylock()
153 /* not specified as part of POSIX but this is the Linux behavior */ in pthread_spin_unlock()
|
| /Zephyr-latest/boards/nxp/mimxrt1060_evk/ |
| D | CMakeLists.txt | 23 # the SDK, but we can reuse the block for the RT1050 as both boards use
29 "the MIMXRT1060-EVK, but targeting a custom board. You may need to "
54 message(WARNING "You are using SDRAM as RAM but no device "
62 "This timer will enable lower power modes, but at the cost of reduced "
|
| /Zephyr-latest/boards/shields/arduino_uno_click/boards/ |
| D | nrf9160dk_nrf9160_arduino_uno_click_common.dtsi | 10 * pins, but the nRF9160 DK maps these pins to two different pairs of
31 * control, but the Arduino Uno Click Shield board does not connect
33 * on the same pins, but just removes RTS/CTS from the pin groups.
|
| /Zephyr-latest/dts/bindings/gpio/ |
| D | panasonic,reduced-arduino-header.yaml | 36 2. Analog Input header, like on Arduino UNO layout, but A4 and A5 are
40 Arduino UNO layout, labeled from D0 at the bottom to D7 at the top, but D6
45 but D8 and D9 are not connected.
|
| /Zephyr-latest/boards/nxp/mimxrt1024_evk/ |
| D | CMakeLists.txt | 12 "the MIMXRT1024-EVK, but targeting a custom board. You may need to "
34 message(WARNING "You are using SDRAM as RAM but no device "
42 "This timer will enable lower power modes, but at the cost of reduced "
|
| /Zephyr-latest/boards/nxp/mimxrt1020_evk/ |
| D | CMakeLists.txt | 12 "the MIMXRT1020-EVK, but targeting a custom board. You may need to "
34 message(WARNING "You are using SDRAM as RAM but no device "
42 "This timer will enable lower power modes, but at the cost of reduced "
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | README.txt | 24 copies. But then, the biggest Zephyr application binaries we have on
46 basically Windows DLLs. But our compiler only generates code for ELF
52 time by a system binary (ld-linux.so). But there is no ld-linux.so in
58 support from the environment. But that only works for symbols that
66 clearly rule it out. But my experience with real EFI loaders is that
86 sneak around EFI areas. But the Zephyr loader should at least detect
|
| /Zephyr-latest/tests/subsys/zbus/hlp_priority_boost/src/ |
| D | main.c | 135 zassert_true(prio == 1, "The priority must be 1, but it is %d", prio); in ZTEST()
141 zassert_true(prio == 2, "The priority must be 2, but it is %d", prio); in ZTEST()
147 zassert_true(prio == 1, "The priority must be 1, but it is %d", prio); in ZTEST()
157 zassert_true(prio == 2, "The priority must be 2, but it is %d", prio); in ZTEST()
165 zassert_true(prio == 8, "The priority must be 8, but it is %d", prio); in ZTEST()
173 zassert_true(prio == 1, "The priority must be 1, but it is %d", prio); in ZTEST()
177 zassert_true(prio == 8, "The priority must be 8, but it is %d", prio); in ZTEST()
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig.nrf_mram | 18 Note that MRAM words are auto-erased when written to, but writing to a
19 pre-erased area is faster. Hence, the erase API is not required, but
|
| /Zephyr-latest/boards/nxp/mimxrt1064_evk/ |
| D | CMakeLists.txt | 17 "the MIMXRT1064-EVK, but targeting a custom board. You may need to "
39 message(WARNING "You are using SDRAM as RAM but no device "
47 "This timer will enable lower power modes, but at the cost of reduced "
|
| /Zephyr-latest/boards/nxp/mimxrt1160_evk/ |
| D | CMakeLists.txt | 12 "the MIMXRT1160-EVK, but targeting a custom board. You may need to "
34 message(WARNING "You are using SDRAM as RAM but no device "
42 "This timer will enable lower power modes, but at the cost of reduced "
|
| /Zephyr-latest/boards/nxp/mimxrt1040_evk/ |
| D | CMakeLists.txt | 17 "the MIMXRT1040-EVK, but targeting a custom board. You may need to "
39 message(WARNING "You are using SDRAM as RAM but no device "
47 "This timer will enable lower power modes, but at the cost of reduced "
|
| /Zephyr-latest/arch/nios2/core/ |
| D | cpu_idle.c | 13 /* Do nothing but unconditionally unlock interrupts and return to the in arch_cpu_idle()
23 /* Do nothing but restore IRQ state. This CPU does not have any in arch_cpu_atomic_idle()
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_MMU.txt | 21 entries. Zephyr manages both as needed, but symmetrically. The
23 and data spaces, but the hardware page table refill mechanism (see
40 initialization, but this mechanism isn't accessible to OS code except
80 one each for instruction/data TLBs, but in Zephyr they operate
105 practice. But it does have a chicken/egg problem with the initial
122 But now note that the load from that PTE address for the refill is
129 same way we do for data, but somewhat inexplicably, Xtensa does not
156 But that means that enabling page-level translation requires some
172 mapping condition, but it is safe as nothing will use it until we
180 exceptions is now complete, but cannot be used until we resolve the
[all …]
|
| /Zephyr-latest/dts/bindings/dac/ |
| D | ti,dacx0501.yaml | 29 resolution. mul2 will double the output range but lower the resolution, while div2 will
30 lower the range but double the resolution.
|
| /Zephyr-latest/boards/nxp/mimxrt1170_evk/ |
| D | CMakeLists.txt | 12 "the MIMXRT1170-EVK, but targeting a custom board. You may need to "
39 message(WARNING "You are using SDRAM as RAM but no external memory"
47 "This timer will enable lower power modes, but at the cost of reduced "
|
| /Zephyr-latest/boards/nxp/mimxrt1050_evk/ |
| D | CMakeLists.txt | 21 "the MIMXRT1050-EVK, but targeting a custom board. You may need to "
45 message(WARNING "You are using SDRAM as RAM but no device "
53 "This timer will enable lower power modes, but at the cost of reduced "
|
| /Zephyr-latest/subsys/stats/ |
| D | Kconfig | 19 but results in a larger code size.
29 but results in a larger code size.
|
| /Zephyr-latest/drivers/sensor/bosch/bme680/ |
| D | Kconfig | 24 lead to more accurate readings, but higher power consumption.
42 lead to more accurate readings, but higher power consumption.
60 lead to more accurate readings, but higher power consumption.
|
