soc: st: stm32: build warning for STM32_ENABLE_DEBUG_SLEEP_STOP
#87193
+7
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a warning in the build system if both
CONFIG_PM
andSTM32_ENABLE_DEBUG_SLEEP_STOP
are enabled at the same time. The first is likely only enabled if the SoC is intended to be driven into low power states to save power, while the later prevents the SoC from being as low power as it can be.The sneaky select on
CONFIG_USE_SEGGER_RTT
cost me a day of my life chasing down clock configurations :)zephyr/modules/segger/Kconfig
Lines 12 to 15 in d6c59f0