-
Notifications
You must be signed in to change notification settings - Fork 8.3k
soc: st: stm32: reorganize family-wide common Kconfig #100218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
soc: st: stm32: reorganize family-wide common Kconfig #100218
Conversation
Split STM32 family-wide common Kconfig in two separate files: a new Kconfig file `soc/st/stm32/common/Kconfig` to hold options that affect the common code found in the same directory, and the existing top-level Kconfig file `soc/st/stm32/Kconfig` which now only holds options used by multiple series but not consumed by the common code - for example, options that are used by SoC-specific code or consumed by the STM32Cube HAL module go in this file. Signed-off-by: Mathieu Choplain <[email protected]>
|
| # Copyright (c) 2025 STMicroelectronics | ||
| # SPDX-License-Identifier: Apache-2.0 | ||
| # | ||
| # Kconfig options for STM32 family-wide common code |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Disambiguate 'common'
| # Kconfig options for STM32 family-wide common code | |
| # Kconfig options for STM32 family-wide common/ code |
| # `common/Kconfig` declares all Kconfig options used to | ||
| # configure the family-wide code found in `common/`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A bit unclear. what about:
Kconfig options used to configure the family-wide code
found in `common/` are made available in common/Konfig
| # However, some Kconfig options are shared by all series but | ||
| # not consumed by common code; instead, SoC-specific code, | ||
| # certain drivers or the STM32Cube HAL module will make use | ||
| # of them. Such Kconfig options are declared here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| # However, some Kconfig options are shared by all series but | |
| # not consumed by common code; instead, SoC-specific code, | |
| # certain drivers or the STM32Cube HAL module will make use | |
| # of them. Such Kconfig options are declared here. | |
| # Kconfig options shared by all series, but not consumed by common code, | |
| # such as SoC-specific code, certain drivers or the STM32Cube HAL module | |
| # are declared below. |



Split STM32 family-wide common Kconfig in two separate files: a new Kconfig file
soc/st/stm32/common/Kconfigto hold options that affect the common code found in the same directory, and the existing top-level Kconfig filesoc/st/stm32/Kconfigwhich now only holds options used by multiple series but not consumed by the common code - for example, options that are used by SoC-specific code or consumed by the STM32Cube HAL module go in this file.