| /Zephyr-Core-2.7.6/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-Core-2.7.6/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-Core-2.7.6/tests/subsys/portability/cmsis_rtos_v1/src/ |
| D | timer.c | 50 /* Create one-shot timer */ in test_timer()
53 zassert_true(id1 != NULL, "error creating one-shot timer"); in test_timer()
61 zassert_true(status == osOK, "error starting one-shot timer"); in test_timer()
63 /* Timer should fire only once if setup in one shot in test_timer()
64 * mode. Wait for 3 times the one-shot time to see in test_timer()
69 "error setting up one-shot timer"); in test_timer()
72 zassert_true(status == osOK, "error stopping one-shot timer"); in test_timer()
75 zassert_true(status == osOK, "error deleting one-shot timer"); in test_timer()
|
| /Zephyr-Core-2.7.6/tests/subsys/portability/cmsis_rtos_v2/src/ |
| D | timer.c | 52 /* Create one-shot timer */ in test_timer()
55 zassert_true(id1 != NULL, "error creating one-shot timer"); in test_timer()
68 zassert_true(status == osOK, "error starting one-shot timer"); in test_timer()
72 /* Timer should fire only once if setup in one shot in test_timer()
73 * mode. Wait for 3 times the one-shot time to see in test_timer()
78 "error setting up one-shot timer"); in test_timer()
81 zassert_true(status == osOK, "error stopping one-shot timer"); in test_timer()
84 zassert_true(status == osOK, "error deleting one-shot timer"); in test_timer()
|
| /Zephyr-Core-2.7.6/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-Core-2.7.6/tests/net/lib/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-Core-2.7.6/doc/reference/kernel/other/ |
| D | polling.rst | 6 The polling API is used to wait concurrently for any one of multiple conditions
20 The polling API allows a single thread to wait concurrently for one or more
21 conditions to be fulfilled without actively looking at each one individually.
30 **poll events**, one for each condition.
49 The :c:func:`k_poll` function returns as soon as one of the conditions it
50 is waiting for is fulfilled. It is possible for more than one to be fulfilled
56 Currently, there is only one mode of operation available: the object is not
71 of type :c:struct:`k_poll_event`. Each entry in the array represents one
177 One of the types of events is :c:macro:`K_POLL_TYPE_SIGNAL`: this is a "direct"
179 one thread can wait for.
[all …]
|
| /Zephyr-Core-2.7.6/tests/drivers/i2c/i2c_slave_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 master) 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-Core-2.7.6/subsys/logging/ |
| D | Kconfig.mode | 30 flawlessly in that mode because one log operation can be interrupted
31 by another one in the higher priority context.
41 flawlessly in that mode because one log operation can be interrupted
42 by another one in the higher priority context.
|
| /Zephyr-Core-2.7.6/samples/drivers/led_lp503x/ |
| D | README.rst | 14 led_write_channels syscall) and then to each LED one by one (using the
20 For all the LEDs first (using channel API) and then for each LED one by one:
|
| /Zephyr-Core-2.7.6/drivers/timer/ |
| D | ite_it8xxx2_timer.c | 26 * One shot timer configurations
30 * timer2 only one shot to wake up chip and change pll.
40 * One system (kernel) tick is as how much HW timer counts
64 * so disabled one shot timer interrupt. in timer_5ms_one_shot_isr()
78 /* Initialize interrupt handler of one shot timer */ in timer_5ms_one_shot()
82 /* Set rising edge triggered of one shot timer */ in timer_5ms_one_shot()
85 /* Clear interrupt status of one shot timer */ in timer_5ms_one_shot()
88 /* Set clock source of one shot timer */ in timer_5ms_one_shot()
92 * Set count of one shot timer, in timer_5ms_one_shot()
128 /* Informs kernel that one system tick has elapsed */ in evt_timer_isr()
[all …]
|
| /Zephyr-Core-2.7.6/tests/subsys/shell/shell_history/src/ |
| D | shell_history_test.c | 42 zassert_true(res, "history should contain one entry.\n"); in test_get()
59 * - read line and verify that it is the one that was put.
100 * - get in up direction a line and verify that it's the last one added (3).
187 test_get(false, true, NULL, 0); /* only one entry */ in test_too_long_line_not_stored()
192 /* Test verifies that same line as the previous one is not stored in the
198 * - verify that only one line is in the history.
211 /* only one line stored. */ in test_no_duplicates_in_a_row()
243 test_get(false, true, NULL, 0); /* only one entry */ in test_storing_long_buffers()
247 test_get(false, true, NULL, 0); /* only one entry */ in test_storing_long_buffers()
251 test_get(false, true, NULL, 0); /* only one entry */ in test_storing_long_buffers()
|
| /Zephyr-Core-2.7.6/tests/drivers/regulator/fixed/ |
| D | README.txt | 6 pins be shorted so that changes made to the state of one can be verified
12 select between one that supports asynchronous transitions and an
13 optimized one synchronous transitions. The initial state of the
|
| /Zephyr-Core-2.7.6/dts/arm/nxp/ |
| D | nxp_rt1060.dtsi | 9 /* i.MX rt1060 has two continuous on-chip RAM, one is part of the
11 * configurable (256KB by defaults), the other one is dedicated 512KB
13 * region, we describe them in one 768Kb unique node.
|
| /Zephyr-Core-2.7.6/include/display/ |
| D | mb_display.h | 59 /** Display images sequentially, one at a time. */
117 * @brief Display one or more images on the BBC micro:bit LED display.
119 * This function takes an array of one or more images and renders them
122 * another image being displayed it will be canceled and the new one takes
126 * @param mode One of the MB_DISPLAY_MODE_* options.
143 * will be canceled and the new one takes over.
146 * @param mode One of the MB_DISPLAY_MODE_* options.
|
| /Zephyr-Core-2.7.6/subsys/net/lib/capture/ |
| D | Kconfig | 30 will allocate one net_pkt for network metadata.
45 Number of network capture devices. Usually one is enough but
46 if one needs to send captured data to multiple different devices,
|
| /Zephyr-Core-2.7.6/dts/bindings/test/ |
| D | vnd,gpio-one-cell.yaml | 4 description: Test GPIO node with one cell
6 compatible: "vnd,gpio-one-cell"
|
| /Zephyr-Core-2.7.6/include/drivers/usb/ |
| D | usb_dc.h | 248 * @param[in] ep Endpoint address corresponding to the one
258 * @param[in] ep Endpoint address corresponding to the one
268 * @param[in] ep Endpoint address corresponding to the one
279 * @param[in] ep Endpoint address corresponding to the one
293 * @param[in] ep Endpoint address corresponding to the one
307 * @param[in] ep Endpoint address corresponding to the one
319 * @param[in] ep Endpoint address corresponding to the one
333 * @param[in] ep Endpoint address corresponding to the one
356 * @param[in] ep Endpoint address corresponding to the one
377 * @param[in] ep Endpoint address corresponding to the one
[all …]
|
| /Zephyr-Core-2.7.6/drivers/pwm/ |
| D | Kconfig.nrf5_sw | 14 channels per pin and one GPIOTE config per pin.
17 channels per pin and one GPIOTE config per pin.
|
| /Zephyr-Core-2.7.6/samples/subsys/mgmt/updatehub/ |
| D | overlay-prj.conf.example | 12 #request for updates one to one minute.
|
| /Zephyr-Core-2.7.6/arch/xtensa/core/ |
| D | README-WINDOWS.rst | 10 or 64 "real" registers in hardware, with 16 visible at one time.
51 WINDOWSTART stores a bitmask with one bit per hardware quad (so it's 8
55 stay zero. So there is one set bit in WINDOWSTART corresponding to
66 another call by seeing if there is a one in WINDOWSTART between that
68 handler to spill one frame. Note that a frame might be only four
74 the frame bit to detect how many quads are represented by the one
|
| /Zephyr-Core-2.7.6/tests/drivers/can/stm32/src/ |
| D | main.c | 118 * Test a more adcvanced filter handling. Attach more than one filter at
134 "Filter full even for a single one"); in test_filter_handling()
139 "Filter full when attaching the second one"); in test_filter_handling()
145 "Filter full when overriding the first one"); in test_filter_handling()
155 zassert_equal(ret, -EAGAIN, "There is more than one msg in the queue"); in test_filter_handling()
160 "Filter full when overriding the first one"); in test_filter_handling()
|
| /Zephyr-Core-2.7.6/subsys/bluetooth/controller/ll_sw/ |
| D | lll_df.h | 14 * pointer to first (oldest) one.
18 * returned pointer equals to peeked one.
|
| /Zephyr-Core-2.7.6/doc/security/ |
| D | secure-coding.rst | 40 vulnerability knowledge that at least one of the primary developers
93 than one user or process shall not be shared if not strictly
137 The Zephyr project must have at least one primary developer who knows
161 depend on more than one condition, so that defeating one protection
170 common to more than one user and depended on by all users, e.g.,
195 vulnerability reporting channel (if there is one), can accept commits
197 software. If there is only one developer, that individual is the
200 At least one of the primary developers **must** know of common kinds of
202 as at least one method to counter or mitigate each of them.
229 required to go through. Each change shall be reviewed by at least one
|
