| /Zephyr-latest/drivers/bbram/ |
| D | Kconfig.stm32 | 14 application data. They are implemented in the backup domain that remains
15 powered-on by VBAT when the VDD power is switched off. They are not reset
16 by system reset or when the device wakes up from Standby mode. They are
|
| /Zephyr-latest/dts/bindings/memory-controllers/ |
| D | st,stm32-bbram.yaml | 8 application data. They are implemented in the backup domain that remains
9 powered-on by VBAT when the VDD power is switched off. They are not reset
10 by system reset or when the device wakes up from Standby mode. They are
|
| /Zephyr-latest/tests/drivers/adc/adc_accuracy_test/ |
| D | README.txt | 7 read on an ADC one. If they match, the test passes.
15 if they match. Note that DAC and ADC are expected to generate/read
21 to see if they match.
|
| /Zephyr-latest/tests/subsys/fs/multi-fs/src/ |
| D | main.c | 18 * They have to be executed in order. in ZTEST()
29 * They have to be executed in order. in ZTEST()
42 * They have to be executed in order. in ZTEST()
53 * They have to be executed in order. in ZTEST()
|
| /Zephyr-latest/tests/bsim/bluetooth/host/misc/sample_test/ |
| D | prj.conf | 21 # Always enable asserts in tests, they're virtually free on native targets.
47 # explaining why they might be useful. That way, someone trying to debug your
54 # They might matter for other tests though. They are printed by the
|
| /Zephyr-latest/doc/services/tfm/ |
| D | testsuites.rst | 18 NS/S boundary via the PSA APIs. They provide a useful sanity check for proper
40 They also provide a useful test case to validate any PRs that make meaningful
42 to the core TF-M module(s). They should generally be run as a coherence check
|
| /Zephyr-latest/tests/bsim/bluetooth/host/privacy/device/ |
| D | README.rst | 12 type. That, even if they have previously exchanged IRK; (Core Specification version 5.4, vol. 1
14 * After devices have exchanged IRK, they must correctly resolve RPA when receiving packets from the
|
| /Zephyr-latest/tests/subsys/fs/littlefs/src/ |
| D | testfs_mount_flags.c | 14 /* Using smallest partition for this tests as they do not write
15 * a lot of data, basically they just check flags.
|
| D | testfs_open_flags.c | 42 /* Using smallest partition for this tests as they do not write in ZTEST()
43 * a lot of data, basically they just check flags. in ZTEST()
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings.rst | 15 These pages introduce bindings, describe what they do, note where they are
|
| /Zephyr-latest/arch/x86/core/ |
| D | Kconfig.intel64 | 28 processing and early kernel/CPU initialization. They need only
30 so they are typically smaller than the ISR stacks.
58 # and we check to be sure they're a valid combination in arch.h. yes, ugh.
|
| /Zephyr-latest/include/zephyr/arch/xtensa/ |
| D | thread.h | 17 /* Xtensa doesn't use these structs, but Zephyr core requires they be
18 * defined so they can be included in struct _thread_base. Dummy
|
| /Zephyr-latest/tests/benchmarks/thread_metric/ |
| D | testcase.yaml | 7 # Native platforms excluded as they are not relevant: These benchmarks run some kernel primitives
8 # in a loop during a predefined time counting how many times they execute. But in the POSIX arch,
|
| /Zephyr-latest/samples/bluetooth/periodic_sync_rsp/ |
| D | README.rst | 21 Flash this sample to multiple devices and they will be given different
22 subevents and response slots, to that they can communicate with the
|
| /Zephyr-latest/scripts/west_commands/fetchers/ |
| D | __init__.py | 18 # Fetchers are supposed to gracefully handle failures when they
19 # import anything outside of stdlib, but they sometimes do
|
| /Zephyr-latest/tests/lib/p4workq/src/ |
| D | main.c | 72 /* Pick 0-3 random item slots and submit them if they aren't in stress_handler()
165 * they get scheduled as needed, up to NUM_CPUS (at which point the
167 * priorities and verify that they get scheduled too (to allow
180 * (note they have lower priority than the current thread so in ZTEST()
181 * we can be sure to run). They should all be made active in ZTEST()
194 /* Now add more at higher priorities, they should get in ZTEST()
195 * scheduled (so that they can preempt the running ones) until in ZTEST()
|
| /Zephyr-latest/doc/project/ |
| D | proposals.rst | 46 Items are examined for similarity with existing features, how they fit with
58 assignee are open for grabs, meaning that they can be picked up and implemented
67 they have very different purposes and should not be confused. A project roadmap
87 they are still executing according to plan.
|
| /Zephyr-latest/dts/bindings/gpio/ |
| D | nordic,nrf-gpio-forwarder.yaml | 53 They are set to 0 in the nrf-gpio-forwarder node as they are ignored anyway.
56 files. They are merged into a single node with multiple child nodes when
|
| /Zephyr-latest/subsys/logging/ |
| D | Kconfig.filtering | 34 specified level if it is greater than this option, otherwise they use
51 specified level if it is greater than this option, otherwise they use
|
| /Zephyr-latest/scripts/west_commands/runners/ |
| D | __init__.py | 16 # Runners are supposed to gracefully handle failures when they
17 # import anything outside of stdlib, but they sometimes do
|
| /Zephyr-latest/soc/openisa/rv32m1/ |
| D | wdog.S | 41 /* Disable interrupts if they're on. This is timing-sensitive code. */
61 /* Re-enable interrupts if they were disabled. */
|
| /Zephyr-latest/include/zephyr/drivers/ |
| D | loopback_disk.h | 31 * if they are string literals, but care must be taken for ctx, as well as for file_path and
32 * disk_access_name if they are constructed dynamically.
|
| /Zephyr-latest/tests/bluetooth/common/testlib/src/ |
| D | conn_ref.c | 23 * The functions in this file will trigger an assert if they attempt to
29 * behavor due to NULL pointer dereferencing. They will assert on any
|
| /Zephyr-latest/kernel/ |
| D | idle.c | 31 * enter an idle state, because they can't be notified in idle()
32 * of scheduler changes (i.e. threads they should in idle()
33 * run). They just spin instead, with a minimal in idle()
|
| /Zephyr-latest/dts/arm/nxp/ |
| D | nxp_rt1010.dtsi | 67 /* Remove GPIO3-GPIO9, they don't exist on RT1010 */
100 /* Remove Quad TImers, they don't exist on RT1010 */
123 /* Fixup LPI2C1 and LPI2C2, they have different base addr on RT1010 */
149 /* Remove LPI2C3 & LPI2C4, they don't exist on RT1010 */
156 /* Fixup LPSPI1 and LPSPI2, they have different base addr on RT1010 */
179 /* Remove LPUART5-8, they don't exist on RT1010 */
238 /* Remove FlexPWM2-4, they don't exist on RT1010 */
261 /* Remove USDHC, they don't exist on RT1010 */
268 /* Remove FLEXCAN, they don't exist on RT1010 */
|
