Searched refs:processing (Results 1 – 25 of 245) sorted by relevance
12345678910
| /Zephyr-4.2.1/subsys/logging/ |
| D | Kconfig.processing | 48 up. Log processing thread ID is provided during log initialization.
53 bool "Use internal thread for log processing"
65 int "Set log processing thread startup delay"
68 Log processing thread starts after requested delay given in
72 int "Set internal log processing thread sleep period"
75 Log processing thread sleeps for requested period given in
79 int "Stack size for the internal log processing thread"
93 Set the internal stack size for log processing thread.
101 processing in the local domain. Higher value increases message processing
109 Set a custom value for the log processing thread.
[all …]
|
| /Zephyr-4.2.1/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-4.2.1/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-4.2.1/tests/subsys/logging/log_blocking/ |
| D | REAME.md | 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.
84 capacity. Once the core log buffer is full, the log processing thread is
91 correctly _even when the log processing thread is blocking_ in order to
95 backends that are unable to recover from stalling the log processing thread.
|
| /Zephyr-4.2.1/samples/subsys/rtio/sensor_batch_processing/ |
| D | README.rst | 2 :name: Sensor batch processing
5 Implement a sensor device using RTIO for asynchronous data processing.
33 submitting for, consuming, and processing the sensor data.
50 I: Start processing 4 samples
66 I: Finished processing 4 samples
|
| /Zephyr-4.2.1/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-4.2.1/tests/benchmarks/thread_metric/ |
| D | Kconfig | 30 bool "Interrupt processing"
35 The interrupt processing benchmark has a single thread that causes
42 bool "Interrupt processing preemption"
60 bool "Message processing"
62 The message processing benchmark counts the number of times that a
|
| D | thread_metric_readme.txt | 37 call thread suspend. Eventually the processing will return to the
39 resume call. Once processing returns to the lowest priority thread,
49 interrupt handler completes, processing returns to the test
113 processing capabilities
116 tm_interrupt_processing_test.c No-preemption interrupt processing
118 tm_interrupt_preemption_processing_test.c Interrupt preemption processing
120 tm_message_processing_test.c Message exchange processing test
121 tm_synchronization_processing_test.c Semaphore get/put processing test
246 processing in the reporting thread is insignificant.
|
| /Zephyr-4.2.1/subsys/rtio/ |
| D | Kconfig.workq | 8 Enable RTIO Work-queues to allow processing synchronous operations
22 int "Number of threads to use for processing work-items"
|
| /Zephyr-4.2.1/drivers/ethernet/ |
| D | Kconfig.enc424j600 | 22 incoming packet processing.
29 packet processing.
|
| D | Kconfig.lan9250 | 23 incoming packet processing.
30 packet processing.
|
| D | Kconfig.enc28j60 | 23 incoming packet processing.
31 packet processing.
|
| D | Kconfig.w5500 | 22 incoming packet processing.
30 packet processing.
|
| /Zephyr-4.2.1/drivers/i2s/ |
| D | Kconfig.esp32 | 35 int "ESP32 I2S empty TX queue processing deferral time"
38 Allowed deferral time for processing an empty tx queue in milliseconds
|
| /Zephyr-4.2.1/samples/modules/cmsis_dsp/ |
| D | cmsis_dsp.rst | 5 These samples demonstrate how to use the CMSIS-DSP module to perform signal processing operations
|
| /Zephyr-4.2.1/share/sysbuild/images/ |
| D | CMakeLists.txt | 6 # it is available while processing the remaining images.
32 # Done processing modules, clear SYSBUILD_CURRENT_MODULE_DIR and SYSBUILD_CURRENT_CMAKE_DIR.
|
| /Zephyr-4.2.1/doc/connectivity/networking/api/ |
| D | net_stats.rst | 22 application wants to collect statistics for further processing. The network
30 These statistics can then be transferred to application for processing.
|
| /Zephyr-4.2.1/include/zephyr/linker/ |
| D | llext-sections.ld | 29 * Zephyr ELF for post-processing, but it is not included in the final binary.
31 * NOTE: This section MUST start at address 0, as the post-processing scripts
|
| /Zephyr-4.2.1/drivers/led/ |
| D | Kconfig.ht16k33 | 33 interrupt processing.
40 processing.
|
| /Zephyr-4.2.1/subsys/mgmt/mcumgr/grp/zephyr_basic/ |
| D | Kconfig | 7 Enables MCUmgr to processing of Zephyr specific groups.
|
| /Zephyr-4.2.1/tests/cmake/snippets/ |
| D | Kconfig | 33 Test the snippet processing order (1. foo, 2. bar)
38 Test the snippet processing order (1. bar, 2. foo)
|
| /Zephyr-4.2.1/boards/renesas/rcar_salvator_xs/doc/ |
| D | index.rst | 20 * video processing units;
21 * sound processing units;
|
| /Zephyr-4.2.1/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-4.2.1/samples/subsys/zbus/remote_mock/ |
| D | README.rst | 43 D: START processing channel start_measurement change
47 D: FINISH processing channel start_measurement change
48 D: START processing channel sensor_data change
52 D: FINISH processing channel sensor_data change
|
| /Zephyr-4.2.1/boards/amd/versalnet_apu/doc/ |
| D | index.rst | 5 This configuration provides support for the APU(A78), ARM processing unit on AMD
10 This processing unit is based on an ARM Cortex-A78 CPU, it also enables the following devices:
|
12345678910
