Home
last modified time | relevance | path

Searched full:frontend (Results 1 – 25 of 26) sorted by relevance

12

/Zephyr-Core-3.6.0/tests/subsys/logging/log_api/
Dtestcase.yaml91 logging.frontend.dbg:
97 logging.frontend.dbg.rt_filtering:
104 logging.frontend:
109 logging.frontend.rt_filtering:
115 logging.frontend.immediate:
120 logging.frontend.immediate_override_level:
146 logging.frontend.only:
151 logging.frontend.only.rt_filtering:
157 logging.frontend.no_backends:
243 logging.frontend.dbg_cpp:
[all …]
/Zephyr-Core-3.6.0/subsys/logging/
DKconfig.mode43 bool "Frontend"
45 When enabled, logs are redirected to a custom frontend which is the
57 bool "Frontend optimized API"
59 When enabled, frontend implements functions which are optimized versions
DKconfig.frontends7 bool "UART dictionary frontend"
14 Frontend sends data in binary dictionary mode.
Dlog_cmds.c14 #define FRONTEND_NAME frontend
15 #define FRONTEND_STR STRINGIFY(frontend)
317 shell_warn(sh, "Not supported for frontend"); in log_halt()
349 shell_warn(sh, "Not supported for frontend"); in log_go()
481 "Frontend control", NULL),
Dlog_msg.c60 /* If only frontend is used and log got here it means that it was accepted. */ in frontend_runtime_filtering()
130 /* If frontend does not support optimized API prepare data for in z_impl_z_log_msg_simple_create_0()
169 /* If frontend does not support optimized API prepare data for in z_impl_z_log_msg_simple_create_1()
209 /* If frontend does not support optimized API prepare data for in z_impl_z_log_msg_simple_create_2()
/Zephyr-Core-3.6.0/include/zephyr/drivers/can/
Dcan_sja1000.h9 * @brief API for NXP SJA1000 (and compatible) CAN controller frontend drivers.
120 * @param _custom Pointer to custom driver frontend configuration structure
121 * @param _read_reg Driver frontend SJA100 register read function
122 * @param _write_reg Driver frontend SJA100 register write function
143 * @param _custom Pointer to custom driver frontend configuration structure
144 * @param _read_reg Driver frontend SJA100 register read function
145 * @param _write_reg Driver frontend SJA100 register write function
179 * @param _custom Pointer to custom driver frontend data structure
Dcan_mcan.h1184 * This macro allows a Bosch M_CAN driver frontend using a fixed Message RAM configuration to limit
1188 * Frontend drivers supporting dynamic Message RAM configuration should use @ref
1296 * @param _custom Pointer to custom driver frontend configuration structure
1339 * @param _custom Pointer to custom driver frontend configuration structure
1349 * @param _custom Pointer to custom driver frontend data structure
/Zephyr-Core-3.6.0/samples/subsys/logging/dictionary/
DREADME.rst15 filtering of the logging messages for the frontend (in the same way as it is done for backends).
16 See ``log frontend`` set of commands and use ``log_rt_demo`` command to test the filtering.
19 the UART dictionary based frontend).
/Zephyr-Core-3.6.0/drivers/gpio/
DKconfig.ads114s0x14 The ADS114S0x is a multi-channel analog frontend (AFE).
DKconfig.lmp90xxx15 frontend (AFE).
/Zephyr-Core-3.6.0/drivers/adc/
DKconfig.lmp90xxx20 frontend (AFE).
/Zephyr-Core-3.6.0/include/zephyr/logging/
Dlog_ctrl.h159 * @param backend Backend instance. NULL for all backends (and frontend).
172 * @brief Get source filter for the frontend.
182 * @brief Set filter on given source for the frontend.
Dlog_frontend.h11 /** @brief Initialize frontend.
Dlog_core.h385 /** @brief Slot reserved for the frontend. Last slot is used. */
/Zephyr-Core-3.6.0/doc/services/logging/
Dindex.rst11 developers. Messages are passed through a frontend and are then
13 Custom frontend and backends can be used if needed.
21 - Custom frontend support. It can work together with backends.
74 Logger's default frontend is designed to be thread safe and minimizes time needed
141 :kconfig:option:`CONFIG_LOG_FRONTEND`: Direct logs to a custom frontend.
143 :kconfig:option:`CONFIG_LOG_FRONTEND_ONLY`: No backends are used when messages goes to frontend.
378 - Frontend
385 Default Frontend
388 Default frontend is engaged when the logging API is called in a source of logging (e.g.
391 message. Since the logging API can be called in an interrupt, the frontend is optimized
[all …]
/Zephyr-Core-3.6.0/tests/subsys/logging/log_api/src/
Dmain.c281 /* Validate levels before changing for backend2 and frontend */ in ZTEST()
320 /* WRN message expected on backends and frontend */ in ZTEST()
456 * frontend validate number of arguments and values.
846 IS_ENABLED(CONFIG_LOG_FRONTEND_ONLY) ? "Frontend only" : in log_api_suite_setup()
848 PRINT("\t Frontend: %s\n", in log_api_suite_setup()
/Zephyr-Core-3.6.0/subsys/bluetooth/controller/ll_sw/
Dull_internal.h94 * @brief RX FIFO macro frontend
/Zephyr-Core-3.6.0/boards/xtensa/xt-sim/doc/
Dindex.rst18 :alt: Xtensa Xplorer (Eclipse base frontend for xt-sim)
/Zephyr-Core-3.6.0/cmake/modules/
Dkconfig.cmake157 # Allow out-of-tree users to add their own Kconfig python frontend
/Zephyr-Core-3.6.0/doc/develop/debug/
Dindex.rst138 (Data Display Debugger)`, a graphical frontend for GDB. The following command
/Zephyr-Core-3.6.0/doc/releases/
Drelease-notes-3.6.rst1037 …* Extended logging frontend API to optionally implement dedicated functions for optimized messages.
1040 * Added support for runtime message filtering for the logging frontend.
Drelease-notes-2.2.rst326 * TI LMP90100 Sensor Analog Frontend (AFE) Evaluation Board (EVB)
Drelease-notes-2.4.rst1859 * :github:`3165` - xtensa: switch to clang-based frontend
/Zephyr-Core-3.6.0/scripts/
Dspelling.txt713 fronend||frontend
/Zephyr-Core-3.6.0/scripts/ci/
Dcheck_compliance.py989 # files that don't end in .py as well. python-magic is a frontend

12