| /Zephyr-latest/subsys/logging/ |
| D | Kconfig.processing | 4 menu "Processing" menu
49 up. Log processing thread ID is provided during log initialization.
54 bool "Use internal thread for log processing"
66 int "Set log processing thread startup delay"
69 Log processing thread starts after requested delay given in
73 int "Set internal log processing thread sleep period"
76 Log processing thread sleeps for requested period given in
80 int "Stack size for the internal log processing thread"
94 Set the internal stack size for log processing thread.
102 processing in the local domain. Higher value increases message processing
[all …]
|
| /Zephyr-latest/samples/userspace/prod_consumer/ |
| D | README.rst | 11 to perform some processing on this data and then write the processed data
44 - Application B processing thread waits on new items in the queue. It
71 I:processing payload #1 complete
75 I:processing payload #2 complete
79 I:processing payload #3 complete
83 I:processing payload #4 complete
87 I:processing payload #5 complete
91 I:processing payload #6 complete
93 I:processing payload #7 complete
95 I:processing payload #8 complete
[all …]
|
| /Zephyr-latest/tests/subsys/logging/log_blocking/ |
| D | REAME.md | 1 # Blocking the Log Processing Thread
11 In the last configuration, the log processing thread will block until space
14 > Warning ⚠️: Blocking the log processing thread is generally not recommended
43 inherently provides back-pressure; output log processing is rate-limited
51 limit in the log processing rate for practical systems. That may be
57 so configured, we minimize the liklihood that the log processing thread will
75 If the rate of output processing is less than the rate of input processing,
77 log processing thread.
79 ## Stalling the Log Processing Thread
84 capacity. Once the core log buffer is full, the log processing thread is
[all …]
|
| /Zephyr-latest/tests/benchmarks/thread_metric/ |
| D | thread_metric_readme.txt | 12 1.1. Basic Processing Test
37 call thread suspend. Eventually the processing will return to the
39 resume call. Once processing returns to the lowest priority thread,
43 1.4. Interrupt Processing Test
49 interrupt handler completes, processing returns to the test
54 1.5. Interrupt Preemption Processing Test
60 1.6. Message Processing Test
67 1.7. Synchronization Processing Test
113 processing capabilities
116 tm_interrupt_processing_test.c No-preemption interrupt processing
[all …]
|
| D | Kconfig | 32 bool "Interrupt processing"
37 The interrupt processing benchmark has a single thread that causes
44 bool "Interrupt processing preemption"
62 bool "Message processing"
64 The message processing benchmark counts the number of times that a
|
| /Zephyr-latest/samples/subsys/zbus/uart_bridge/ |
| D | README.rst | 35 D: START processing channel start_measurement change
36 D: FINISH processing channel start_measurement change
38 D: START processing channel sensor_data change
39 D: FINISH processing channel sensor_data change
48 D: START processing channel start_measurement change
49 D: FINISH processing channel start_measurement change
54 D: START processing channel sensor_data change
55 D: FINISH processing channel sensor_data change
|
| /Zephyr-latest/tests/benchmarks/thread_metric/src/ |
| D | tm_basic_processing_test.c | 16 /** Basic Processing Test */
33 /* This file defines the basic test for determining board processing */
51 * test array to eat up processing bandwidth. The idea is that
80 /* Define the basic processing test initialization. */
93 /* Define the basic processing thread. */
105 /* Clear the basic processing array. */ in tm_basic_processing_thread_0_entry()
112 * Loop through the basic processing array, add the previous in tm_basic_processing_thread_0_entry()
126 /* Increment the basic processing counter. */ in tm_basic_processing_thread_0_entry()
131 /* Define the basic processing reporting function. */
153 printf("**** Thread-Metric Basic Single Thread Processing Test **** Relative Time: " in tm_basic_processing_thread_report()
[all …]
|
| /Zephyr-latest/samples/subsys/zbus/hello_world/ |
| D | README.rst | 41 D: START processing channel acc_data change
43 D: FINISH processing channel acc_data change
45 D: START processing channel acc_data change
47 D: FINISH processing channel acc_data change
|
| /Zephyr-latest/include/zephyr/drivers/i3c/ |
| D | ibi.h | 151 * @brief Queue an IBI work item for future processing.
154 * for future processing.
170 * @brief Queue a target interrupt IBI for future processing.
173 * for future processing.
188 * @brief Queue a hot join IBI for future processing.
191 * for future processing.
203 * @brief Queue a generic callback for future processing.
206 * for future processing.
|
| /Zephyr-latest/samples/subsys/rtio/sensor_batch_processing/ |
| D | sample.yaml | 13 - "(.*)Start processing (.*) samples"
14 - "(.*)Finished processing (.*) samples"
|
| D | README.rst | 2 :name: Sensor batch processing
5 Implement a sensor device using RTIO for asynchronous data processing.
35 submitting for, consuming, and processing the sensor data.
52 I: Start processing 4 samples
68 I: Finished processing 4 samples
|
| /Zephyr-latest/samples/subsys/rtio/sensor_batch_processing/src/ |
| D | main.c | 46 * available to execute a batch processing algorithm, such as in main()
70 /* Here is where we would execute a batch processing algorithm. in main()
74 * queue than we needed for the batch processing algorithm. in main()
76 LOG_INF("Start processing %d samples", M); in main()
81 LOG_INF("Finished processing %d samples", M); in main()
|
| /Zephyr-latest/drivers/flash/ |
| D | flash_stm32wbx.c | 103 * processing has been requested but suspended due to the PESD in write_dword()
122 * processing to protect some latency in critical code in write_dword()
124 * When flash processing is ongoing, the CPU cannot access the in write_dword()
127 * The only way for CPU1 to disallow flash processing is to in write_dword()
134 * Check now if the CPU2 disallows flash processing to in write_dword()
136 * CPU2 does not allow flash processing in write_dword()
240 * processing has been requested but suspended due to the PESD in erase_page()
259 * processing to protect some latency in critical code in erase_page()
261 * When flash processing is ongoing, the CPU cannot access the in erase_page()
264 * The only way for CPU1 to disallow flash processing is to in erase_page()
[all …]
|
| /Zephyr-latest/subsys/mgmt/ec_host_cmd/backends/ |
| D | ec_host_cmd_backend_shi.h | 24 * 5. EC_SHI_PROCESSING - EC starts processing request; AP is clocking in
26 * 6. - - EC finishes processing and sets up response
71 * processing it yet.
75 /* EC has received the entire request from the AP and is processing it. */
93 * by the AP as part of a request packet, or (for old-style ECs) is processing
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.enc424j600 | 22 incoming packet processing.
29 packet processing.
|
| D | Kconfig.lan9250 | 23 incoming packet processing.
30 packet processing.
|
| D | Kconfig.w5500 | 22 incoming packet processing.
30 packet processing.
|
| D | Kconfig.enc28j60 | 23 incoming packet processing.
31 packet processing.
|
| /Zephyr-latest/subsys/rtio/ |
| D | Kconfig.workq | 9 Enable RTIO Work-queues to allow processing synchronous operations
23 int "Number of threads to use for processing work-items"
|
| /Zephyr-latest/tests/cmake/snippets/ |
| D | testcase.yaml | 27 # Test the snippet processing order (1. foo, 2. bar)
32 # Test the snippet processing order (1. bar, 2. foo)
|
| /Zephyr-latest/subsys/net/lib/sockets/ |
| D | Kconfig | 17 int "Default processing priority for sockets"
20 Default processing priority for socket implementations. This defines
21 the order of processing of particular socket implementations when
22 creating a new socket, lower value indicate earlier processing. This
23 allows to for instance prioritize offloaded socket processing during
128 int "Default processing priority for TLS sockets"
131 Processing priority for TLS sockets. Should be lower than
256 int "Default processing priority for offloaded sockets"
259 Processing priority for offloaded sockets.
383 the same priority as the thread processing network events (see
|
| /Zephyr-latest/drivers/fpga/ |
| D | fpga_mpfs.c | 214 /* Once system controller starts processing command The busy bit will in verify_image()
231 * processing command. Since DRI is slow interface, we are waiting in verify_image()
232 * here to make sure System controller has started processing in verify_image()
239 /* Once system controller starts processing command The busy bit will in verify_image()
262 /* Once system controller starts processing command The busy bit will in activate_image()
277 * processing command. Since DRI is slow interface, we are waiting in activate_image()
278 * here to make sure System controller has started processing in activate_image()
285 /* Once system controller starts processing command The busy bit will in activate_image()
345 /* Once system controller starts processing command The busy bit will in mpfs_fpga_get_info()
361 * processing command. Since DRI is slow interface, we are waiting in mpfs_fpga_get_info()
[all …]
|
| /Zephyr-latest/samples/kernel/metairq_dispatch/ |
| D | README.rst | 10 priority level to implement "bottom half" style processing
17 Each message has a random (and non-trivial) amount of processing that
29 * The real time spent processing the message in the worker thread, for
30 comparison with the required processing time. This provides a way
36 latencies and lower processing delays, as expected.
38 * Cooperatively scheduled threads have significantly better processing
|
| /Zephyr-latest/drivers/led/ |
| D | Kconfig.ht16k33 | 33 interrupt processing.
40 processing.
|
| /Zephyr-latest/modules/openthread/platform/ |
| D | platform-zephyr.h | 28 * This function performs alarm driver processing.
42 * This function performs radio driver processing.
50 * This function performs UART driver processing.
|
