Skip to content

Conversation

@mathieuchopstm
Copy link
Contributor

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.

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]>
@sonarqubecloud
Copy link

# Copyright (c) 2025 STMicroelectronics
# SPDX-License-Identifier: Apache-2.0
#
# Kconfig options for STM32 family-wide common code
Copy link
Member

@erwango erwango Nov 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Disambiguate 'common'

Suggested change
# Kconfig options for STM32 family-wide common code
# Kconfig options for STM32 family-wide common/ code

Comment on lines +13 to +14
# `common/Kconfig` declares all Kconfig options used to
# configure the family-wide code found in `common/`.
Copy link
Member

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

Comment on lines +16 to +19
# 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants