Searched refs:backends (Results 1 – 25 of 58) sorted by relevance
123
| /Zephyr-latest/subsys/ipc/ipc_service/ |
| D | Kconfig | 5 bool "IPC service support multiple backends"
8 users. Ability to work in different backends. The backend
14 rsource "backends/Kconfig"
|
| D | CMakeLists.txt | 5 add_subdirectory(backends)
|
| /Zephyr-latest/subsys/mgmt/ec_host_cmd/ |
| D | CMakeLists.txt | 7 add_subdirectory(backends)
|
| D | Kconfig | 34 avoid duplicating buffers. If multiple backends are used, the size has to be
47 avoid duplicating buffers. If multiple backends are used, the size has to be
110 source "subsys/mgmt/ec_host_cmd/backends/Kconfig"
|
| /Zephyr-latest/subsys/profiling/perf/ |
| D | CMakeLists.txt | 5 add_subdirectory(backends)
|
| D | Kconfig | 23 rsource "backends/Kconfig"
|
| /Zephyr-latest/subsys/logging/ |
| D | Kconfig.template.log_format_config | 36 # all the backends in the Kconfig and their values must match
38 # Example : LOG_BACKEND_XXX_OUTPUT_TEXT should be numbered 0 across all backends
|
| D | CMakeLists.txt | 51 add_subdirectory(backends)
56 # if this is complied before the backends (only with SIZE
|
| D | Kconfig.mode | 25 interrupt).Logger backends must support exclusive access to work
51 bool "No backends"
54 Option indicates that there are no backends intended to be used.
|
| D | Kconfig | 32 rsource "backends/Kconfig"
|
| /Zephyr-latest/modules/hal_nordic/nrfs/ |
| D | CMakeLists.txt | 19 zephyr_include_directories(${CMAKE_CURRENT_SOURCE_DIR}/backends)
42 zephyr_library_sources_ifdef(CONFIG_NRFS_LOCAL_DOMAIN backends/nrfs_backend_ipc_service.c)
|
| D | Kconfig | 130 rsource "backends/Kconfig"
|
| /Zephyr-latest/subsys/modem/ |
| D | CMakeLists.txt | 16 add_subdirectory(backends)
|
| D | Kconfig | 99 rsource "backends/Kconfig"
|
| /Zephyr-latest/subsys/shell/ |
| D | CMakeLists.txt | 4 add_subdirectory(backends)
|
| D | Kconfig.template.shell_log_queue_timeout | 11 other logger backends and must be used with care.
|
| /Zephyr-latest/doc/services/ipc/ipc_service/ |
| D | ipc_service.rst | 164 The requirements needed for implementing backends give flexibility to the IPC
165 service. These allow for the addition of dedicated backends having only a
181 with multiple backends simultaneously, combining the pros and cons of each
187 backends/ipc_service_icmsg.rst
188 backends/ipc_service_icbmsg.rst
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.c_lib_ext | 22 Different shell backends are using their own instance of getopt to
|
| /Zephyr-latest/samples/subsys/shell/shell_module/ |
| D | README.rst | 41 its :ref:`backends <backends>`.
|
| /Zephyr-latest/doc/services/logging/ |
| D | index.rst | 12 processed by active backends.
13 Custom frontend and backends can be used if needed.
20 - Multiple backends supported (up to 9 backends).
21 - Custom frontend support. It can work together with backends.
147 :kconfig:option:`CONFIG_LOG_FRONTEND_ONLY`: No backends are used when messages goes to frontend.
355 backends. Once all backends are notified, all buffered messages are flushed. Since
499 backends.
547 backend. It can also have other backends in parallel.
549 have backends that output logs to the user. It has a cross-domain backend either to
569 to have multiple backends and simultaneously output messages to them. An example of this is shown
[all …]
|
| /Zephyr-latest/tests/subsys/logging/log_blocking/ |
| D | REAME.md | 42 Many log backends, such as UARTs, have a built-in hardware FIFO that
44 based on the baud rate of the UART. Other backends, such as UDP sockets or
95 backends that are unable to recover from stalling the log processing thread.
|
| /Zephyr-latest/doc/services/settings/ |
| D | index.rst | 72 :c:func:`settings_src_register()` for backends that can load data, and/or
73 :c:func:`settings_dst_register()` for backends that can save data. The current
74 implementation allows for multiple source backends but only a single destination
96 Zephyr has three storage backends: a Flash Circular Buffer
119 The FCB and non-volatile storage (NVS) backends both look for a fixed
136 Technically FCB and file backends may store some history of the entities.
|
| /Zephyr-latest/subsys/dsp/ |
| D | Kconfig | 37 bool "Do not use any Zephyr backends for DSP"
|
| /Zephyr-latest/doc/services/debugging/ |
| D | coredump.rst | 8 encountered and prints or stores data according to which backends
18 Here are the options to enable output backends for core dump:
24 backends cannot be enabled. All output is sent to null.
47 and memory content are printed or stored according to which backends
54 1. Get the core dump log from the device depending on enabled backends.
|
| /Zephyr-latest/doc/services/modem/ |
| D | index.rst | 50 attaches to a single modem backend, exposing multiple modem backends,
|
123
