| /Zephyr-latest/samples/drivers/led/pca9633/src/ |
| D | main.c | 43 /* Turn on LEDs one by one */ in main()
53 /* Turn off LEDs one by one */ in main()
63 /* Set the brightness to half max of LEDs one by one */ in main()
73 /* Turn off LEDs one by one */ in main()
83 /* Test the blinking of LEDs one by one */ in main()
97 /* Turn off LEDs one by one */ in main()
|
| /Zephyr-latest/tests/subsys/mgmt/mcumgr/zcbor_bulk/src/ |
| D | main.c | 41 uint32_t one = 0; in ZTEST() local
48 ZCBOR_MAP_DECODE_KEY_DECODER("one", zcbor_uint32_decode, &one), in ZTEST()
54 /* { "hello":"world", "one":1, "bool_val":true } */ in ZTEST()
57 zcbor_tstr_put_lit(zsd, "one") && zcbor_uint32_put(zsd, 1) && in ZTEST()
70 zassert_equal(one, 1, "Expected 1"); in ZTEST()
82 uint32_t one = 0; in ZTEST() local
89 ZCBOR_MAP_DECODE_KEY_DECODER("one", zcbor_uint32_decode, &one), in ZTEST()
95 /* { "hello":"world", "one":1, "bool_val":true } */ in ZTEST()
98 zcbor_tstr_put_lit(zsd, "one") && zcbor_uint32_put(zsd, 1) && in ZTEST()
111 zassert_equal(one, 1, "Expected 1"); in ZTEST()
[all …]
|
| /Zephyr-latest/drivers/display/ |
| D | Kconfig.nrf_led_matrix | 12 GPIOs. The driver allows setting one of 256 levels of brightness
17 The driver uses one TIMER instance and, depending on what is set in
18 devicetree, one PWM instance or one or more GPIOTE and PPI channels
20 of LEDs in one row that can be lit simultaneously).
|
| /Zephyr-latest/tests/subsys/portability/cmsis_rtos_v1/src/ |
| D | timer.c | 50 /* Create one-shot timer */ in ZTEST()
53 zassert_true(id1 != NULL, "error creating one-shot timer"); in ZTEST()
61 zassert_true(status == osOK, "error starting one-shot timer"); in ZTEST()
63 /* Timer should fire only once if setup in one shot in ZTEST()
64 * mode. Wait for 3 times the one-shot time to see in ZTEST()
69 "error setting up one-shot timer"); in ZTEST()
72 zassert_true(status == osOK, "error stopping one-shot timer"); in ZTEST()
75 zassert_true(status == osOK, "error deleting one-shot timer"); in ZTEST()
|
| /Zephyr-latest/scripts/dts/python-devicetree/tests/test-bindings/ |
| D | interrupt-1-cell.yaml | 3 description: Interrupt controller with one cell
5 compatible: "interrupt-one-cell"
8 - one
|
| D | phandle-array-controller-1.yaml | 3 description: Controller with one data value
8 - one
11 - gpio-one
|
| /Zephyr-latest/samples/drivers/led/lp3943/src/ |
| D | main.c | 37 * Display a continuous pattern that turns on 16 LEDs at 1s one by in main()
38 * one until it reaches the end and turns off LEDs in reverse order. in main()
44 /* Turn on LEDs one by one */ in main()
54 /* Turn off LEDs one by one */ in main()
|
| /Zephyr-latest/tests/drivers/disk/disk_performance/ |
| D | README.txt | 11 * Sequential read test: This test performs sequential reads, first only over one
14 * Random read test: This test performs random reads across the disk, each one
18 one sector, than over multiple sequential sectors.
20 * Random write test: This test performs random writes across the disk, each one
|
| /Zephyr-latest/tests/subsys/portability/cmsis_rtos_v2/src/ |
| D | timer.c | 52 /* Create one-shot timer */ in ZTEST()
55 zassert_true(id1 != NULL, "error creating one-shot timer"); in ZTEST()
67 zassert_true(status == osOK, "error starting one-shot timer"); in ZTEST()
71 /* Timer should fire only once if setup in one shot in ZTEST()
72 * mode. Wait for 3 times the one-shot time to see in ZTEST()
77 "error setting up one-shot timer"); in ZTEST()
80 zassert_true(status == osOK, "error stopping one-shot timer"); in ZTEST()
83 zassert_true(status == osOK, "error deleting one-shot timer"); in ZTEST()
|
| /Zephyr-latest/samples/sensor/tmp108/ |
| D | Kconfig | 14 bool "One shot low power mode"
17 One shot requires a callback to be invoked after the tmp108 has
27 although this will work with one shot enabled,
38 although this will work with one shot enabled,
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/friendship/ |
| D | msg_va_collision.sh | 7 # Test that LPN sends only one Subscription List Add and only one Subscription List Remove message
15 # 3.1. LPN unsubscribes from one of the virtual addresses. At this step no Friend Subscription
18 # only one message, which it is still subscribed to.
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | mbox.rst | 11 is providing one or more channels, each one targeting one other CPU cluster
|
| /Zephyr-latest/samples/boards/nordic/coresight_stm/ |
| D | README.rst | 61 [00:00:00.227,264] <inf> app/app: test with one argument 100
62 [00:00:00.227,265] <inf> app/app: test with one argument 100
64 [00:00:00.585,558] <inf> rad/app: test with one argument 100
65 [00:00:00.585,569] <inf> rad/app: test with one argument 100
67 [00:00:00.624,408] <inf> ppr/app: test with one argument 100
68 [00:00:00.624,433] <inf> ppr/app: test with one argument 100
70 [00:00:00.625,249] <inf> flpr/app: test with one argument 100
71 [00:00:00.625,251] <inf> flpr/app: test with one argument 100
|
| /Zephyr-latest/tests/net/lib/mqtt/v3_1_1/mqtt_packet/ |
| D | README | 52 [PASS] 12 - SUBSCRIBE, one topic, qos = 0
53 [PASS] 13 - SUBSCRIBE, one topic, qos = 1
54 [PASS] 14 - SUBSCRIBE, one topic, qos = 2
55 [PASS] 15 - SUBACK, one topic, qos = 0
56 [PASS] 16 - SUBACK, one topic, qos = 1
57 [PASS] 17 - SUBACK, one topic, qos = 2
|
| /Zephyr-latest/dts/bindings/ppc/ |
| D | nxp,nx20p3483.yaml | 20 This value must be set using one of the NX20P348X_U_THRESHOLD_* defines.
32 This value must be set using one of the NX20P348X_I_THRESHOLD_* defines.
39 This value must be set using one of the NX20P348X_I_THRESHOLD_* defines.
|
| /Zephyr-latest/tests/drivers/i2c/i2c_target_api/ |
| D | README.txt | 12 Zephyr application issues commands to one controller that are responded
28 * Issue commands on one bus controller (operating as the bus controller) and
34 Transfer of commands from one bus controller to the other is
40 or the controller driver has bugs, the test will fail one or more I2C
|
| /Zephyr-latest/scripts/pylib/pytest-twister-harness/tests/resources/ |
| D | zen_of_python.py | 22 There should be one-- and preferably only one --obvious way to do it.
28 Namespaces are one honking great idea -- let's do more of those!
|
| /Zephyr-latest/drivers/sensor/tdk/icm42688/ |
| D | icm42688_emul.h | 12 * @brief Set one or more register values
16 * @param in One or more bytes to write to the registers
23 * @brief Get the values of one or more register values
|
| /Zephyr-latest/samples/drivers/led/lp50xx/ |
| D | README.rst | 15 :c:func:`led_write_channels` syscall) and then to each LED one by one (using the
21 For all the LEDs first (using channel API) and then for each LED one by one:
|
| /Zephyr-latest/drivers/sensor/asahi_kasei/akm09918c/ |
| D | akm09918c_emul.h | 12 * @brief Set one or more register values
16 * @param in One or more bytes to write to the registers
23 * @brief Get the values of one or more register values
|
| /Zephyr-latest/include/zephyr/mgmt/hawkbit/ |
| D | autohandler.h | 38 * autohandler to finish one run, or BIT() together with a value from
40 * @param timeout Waiting period for the desired set of events or one of the
62 * one.
64 * @retval 0 if @a if_bigger was true and the current delay was bigger than the new one.
|
| /Zephyr-latest/dts/bindings/test/ |
| D | vnd,gpio-one-cell.yaml | 4 description: Test GPIO node with one cell
6 compatible: "vnd,gpio-one-cell"
|
| /Zephyr-latest/drivers/timer/ |
| D | gecko_burtc_timer.c | 99 * announce the very next tick - in that case we skip one and in burtc_isr()
100 * announce the one after it instead in burtc_isr()
122 * beginning from the closest upcoming one: in sys_clock_set_timeout()
124 * 1 - skip upcoming one, but announce the one after it, etc. in sys_clock_set_timeout()
137 /* Which tick to announce (counting from the last announced one) */ in sys_clock_set_timeout()
150 * the very next tick - in that case we skip one and announce the one in sys_clock_set_timeout()
|
| /Zephyr-latest/include/zephyr/drivers/sensor/ |
| D | tle9104.h | 12 /** Open load detected, boolean with one bit per output */
14 /** Over current detected, boolean with one bit per output */
|
| /Zephyr-latest/doc/ |
| D | glossary.rst | 19 and at least one CMakeLists.txt file.
23 An application can sometimes be built for more than one type of board
45 contain one or more :term:`SoCs <SoC>`.
51 The Zephyr build system defines one or more board configurations
84 A group of one or more :term:`CPU cores <CPU core>`, all executing the same image
87 cluster. Multiple CPU clusters (each of one or more cores) can coexist in
93 which can contain one or more cores.
132 least one :term:`CPU cluster` (in turn with at least one :term:`CPU core`),
136 One or more :term:`SoCs <SoC>` or :term:`SoC series` that share enough
|
