Searched full:backends (Results 1 – 25 of 97) sorted by relevance
1234
5 bool "IPC service support multiple backends"8 users. Ability to work in different backends. The backend14 rsource "backends/Kconfig"
5 add_subdirectory(backends)
10 debug.coredump.backends.logging:15 debug.coredump.backends.flash:27 debug.coredump.backends.other:
13 modem.backends.uart.async:17 modem.backends.uart.isr:
25 interrupt).Logger backends must support exclusive access to work51 bool "No backends"54 Option indicates that there are no backends intended to be used.
36 # all the backends in the Kconfig and their values must match38 # Example : LOG_BACKEND_XXX_OUTPUT_TEXT should be numbered 0 across all backends
51 add_subdirectory(backends)56 # if this is complied before the backends (only with SIZE
161 Backends subsection164 The requirements needed for implementing backends give flexibility to the IPC165 service. These allow for the addition of dedicated backends having only a181 with multiple backends simultaneously, combining the pros and cons of each187 backends/ipc_service_icmsg.rst188 backends/ipc_service_icbmsg.rst
34 adequately chosen. On storage backends with uniform erase-blocks it35 should be at least the erase-block-size, on storage backends with
35 * @brief Get number of backends.37 * @return Number of backends.
34 avoid duplicating buffers. If multiple backends are used, the size has to be47 avoid duplicating buffers. If multiple backends are used, the size has to be110 source "subsys/mgmt/ec_host_cmd/backends/Kconfig"
7 add_subdirectory(backends)
105 /* Test is using two backends which are configured to be autostarted but have111 * both backends are initialized so both receives the message.119 /* Other backends should not be enabled. */ in ZTEST()133 /* Backends are not yet active. */ in ZTEST()
6 # different backends
19 zephyr_include_directories(${CMAKE_CURRENT_SOURCE_DIR}/backends)42 zephyr_library_sources_ifdef(CONFIG_NRFS_LOCAL_DOMAIN backends/nrfs_backend_ipc_service.c)
23 rsource "backends/Kconfig"
67 Backends section in Settings70 Backends are meant to load and save data to/from setting handlers, and72 :c:func:`settings_src_register()` for backends that can load data, and/or73 :c:func:`settings_dst_register()` for backends that can save data. The current74 implementation allows for multiple source backends but only a single destination93 Zephyr Storage Backends96 Zephyr has three storage backends: a Flash Circular Buffer119 The FCB and non-volatile storage (NVS) backends both look for a fixed136 Technically FCB and file backends may store some history of the entities.
5 modem.backends.tty:
4 # Needed for boards that enable RTT backends for logging
15 # Disable all potential other default backends
18 # Disable all potential default backends
4 add_subdirectory(backends)
4 menu "Backends" menu
16 add_subdirectory(backends)
