OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/subsys/logging/Kconfig.template.log_format...

46 lines
1.4 KiB
Plaintext
Raw Normal View History

logging: Add support to backends to switch log format at runtime. Adding mechanism to all the backends to switch the logging formats at runtime while leveraging the function pointer table based upon the Kconfigs which also cleans up the logging backend design. Also demonstrate the working API with the changes to syst sample. Clean up Kconfig for backends and add a standard template to generate the Kconfigs for logging formats to be used by all backends. Signed-off-by: Aastha Grover <aastha.grover@intel.com>
2022-02-02 05:03:08 +08:00
# Copyright (c) 2022 Intel Corporation.
# SPDX-License-Identifier: Apache-2.0
choice "LOG_BACKEND_$(backend)_OUTPUT"
prompt "Backend Output Mode"
default LOG_BACKEND_$(backend)_OUTPUT_TEXT
config LOG_BACKEND_$(backend)_OUTPUT_TEXT
bool "Text"
logging: Fix LOG_OUTPUT dependency When CONFIG_LOG_OUTPUT is set, it indicates that logging strings are formatted by the application (using log_output module). It is not needed when backend works in the dictionary mode. So far LOG_OUTPUT was set also when dictionary mode was used and that prevented removing of the logging strings from binary which is an important feature of the dictionary logging. Signed-off-by: Krzysztof Chruściński <krzysztof.chruscinski@nordicsemi.no>
2024-10-07 21:41:12 +08:00
select LOG_OUTPUT
logging: Add support to backends to switch log format at runtime. Adding mechanism to all the backends to switch the logging formats at runtime while leveraging the function pointer table based upon the Kconfigs which also cleans up the logging backend design. Also demonstrate the working API with the changes to syst sample. Clean up Kconfig for backends and add a standard template to generate the Kconfigs for logging formats to be used by all backends. Signed-off-by: Aastha Grover <aastha.grover@intel.com>
2022-02-02 05:03:08 +08:00
help
Output in text.
config LOG_BACKEND_$(backend)_OUTPUT_SYST
bool "MIPI SyS-T"
depends on LOG_MIPI_SYST_ENABLE
help
When enabled backend is used to output syst format logs.
config LOG_BACKEND_$(backend)_OUTPUT_DICTIONARY
bool "Dictionary"
select LOG_DICTIONARY_SUPPORT
logging: Use strings stripping for dictionary backends Enabled by default strings stripping for dictionary based backends. Signed-off-by: Krzysztof Chruściński <krzysztof.chruscinski@nordicsemi.no>
2024-01-12 15:13:45 +08:00
imply LOG_FMT_SECTION
logging: dictionary: keep string section if always runtime If logging packages need to be created at runtime, the format strings need to be in memory for the packaging code to know what to be packed. So prevent stripping the logging string section if CONFIG_LOG_ALWAYS_RUNTIME is enabled. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2024-05-18 04:12:51 +08:00
imply LOG_FMT_SECTION_STRIP if !LOG_ALWAYS_RUNTIME
logging: Add support to backends to switch log format at runtime. Adding mechanism to all the backends to switch the logging formats at runtime while leveraging the function pointer table based upon the Kconfigs which also cleans up the logging backend design. Also demonstrate the working API with the changes to syst sample. Clean up Kconfig for backends and add a standard template to generate the Kconfigs for logging formats to be used by all backends. Signed-off-by: Aastha Grover <aastha.grover@intel.com>
2022-02-02 05:03:08 +08:00
help
Backend is in dictionary-based logging output mode.
logging: enable setting custom logging output func To enable custom formatting of the log output while still using existing backend, this commit adds the `log_output_custom` feature. To use, register a commit with `log_custom_output_msg_set` then set the log backend format set using `log_backend_format_set` with `LOG_OUTPUT_CUSTOM` Signed-off-by: Lucas Denefle <lucas.denefle@converge.io>
2022-09-01 20:49:35 +08:00
config LOG_BACKEND_$(backend)_OUTPUT_CUSTOM
bool "Extern"
help
Custom formatting function can be set externally.
logging: Add support to backends to switch log format at runtime. Adding mechanism to all the backends to switch the logging formats at runtime while leveraging the function pointer table based upon the Kconfigs which also cleans up the logging backend design. Also demonstrate the working API with the changes to syst sample. Clean up Kconfig for backends and add a standard template to generate the Kconfigs for logging formats to be used by all backends. Signed-off-by: Aastha Grover <aastha.grover@intel.com>
2022-02-02 05:03:08 +08:00
endchoice
# The numbering of the format types should be consistent across
# all the backends in the Kconfig and their values must match
# LOG_OUTPUT_XXX type in C files.
# Example : LOG_BACKEND_XXX_OUTPUT_TEXT should be numbered 0 across all backends
# and should match the value of LOG_OUTPUT_TEXT defined in log_output.h
config LOG_BACKEND_$(backend)_OUTPUT_DEFAULT
int
default 0 if LOG_BACKEND_$(backend)_OUTPUT_TEXT
default 1 if LOG_BACKEND_$(backend)_OUTPUT_SYST
default 2 if LOG_BACKEND_$(backend)_OUTPUT_DICTIONARY
logging: enable setting custom logging output func To enable custom formatting of the log output while still using existing backend, this commit adds the `log_output_custom` feature. To use, register a commit with `log_custom_output_msg_set` then set the log backend format set using `log_backend_format_set` with `LOG_OUTPUT_CUSTOM` Signed-off-by: Lucas Denefle <lucas.denefle@converge.io>
2022-09-01 20:49:35 +08:00
default 3 if LOG_BACKEND_$(backend)_OUTPUT_CUSTOM