OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/arch/arm/soc/st_stm32/stm32f1/Kconfig.defconfig.series

30 lines
429 B
Plaintext
Raw Normal View History

kconfig: untangle ordering and dependencies There are two major issues with the kconfig: () Some of the config options have incorrect dependencies inside help under menuconfig. For example, CONFIG_GPIO depends on BOARD_GALILEO. () Since the SoC and board specific kconfig files are parsed first, the help screen would say, for example, CONFIG_SPI is defined at arch/arm/soc/fsl_frdm_k64f/Kconfig. This is incorrect because the actual config is defined in drivers/spi/Kconfig. These cause great confusion to users of menuconfig/xconfig. To fix these, the SoC and board defaults are now to be parsed last. Note that the position swapping of defaults in this patch is due to the fact the the default parsed last will be used. And, spi_test is broken due to the fact that it requires CONFIG_SPI_INTEL_PORT_1, but never enables it anywhere. This is bypassed for now. Origin: refactored and edited from existing files Change-Id: I2a4b1ae5be4d27e68c960aa47d91ef350f2d500f Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2016-03-26 05:30:50 +08:00
# Kconfig - ST Microelectronics STM32F1 MCU line
st_stm32/stm32f1: introduce STM32F1x SoC family The patch introduces a new family of SoCs based on STMicroelectronics' STM32 MCU line. The patch introduces a basic arch/arm/soc layout along with configuration of 2 MCUs from STM32F1 series: STM32F103VE and STM32F103RB. The patch assumes that other MCUs from STM32 family will be included under arch/arm/soc/st_stm32 tree, to achieve the following layout: arch/ arm/ soc/ st_stm32/ stm32f0/ stm32f1/ stm32f2/ ... stm32l0/ Most of the configuration within a single MCU family (ex. STM32F1) is shared, however individual MCUs differ with respect to SRAM size, flash size or the number of available peripherals. The patch assumes that per MCU line Kconfig.soc.family file should introduce basic setup for given series. This can be further tuned by per MCU files, with Kconfig.soc.stm32f103rb and Kconfig.soc.stm32f103ve as examples. Each family defines a configuration option, ex. CONFIG_STM32F10X, while individual MCUs define a corresponding per MCU config options, ex. CONFIG_STM32F103VE. From the menuconfig perspective, the user is presented with a family selection under General Platform Configuration/SoC Selection. A specific MCU model can be selected by accessing General Platform Configuration/STM32F1x MCU Selection, with the default entry being selected by the board configuration. Change-Id: I22e4defd4a08ed1b2e2cad0e214b34f565e08831 Origin: Original Signed-off-by: Maciej Borzecki <maciek.borzecki@gmail.com>
2016-03-03 22:32:21 +08:00
#
# Copyright (c) 2016 Open-RnD Sp. z o.o.
#
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-19 09:01:01 +08:00
# SPDX-License-Identifier: Apache-2.0
st_stm32/stm32f1: introduce STM32F1x SoC family The patch introduces a new family of SoCs based on STMicroelectronics' STM32 MCU line. The patch introduces a basic arch/arm/soc layout along with configuration of 2 MCUs from STM32F1 series: STM32F103VE and STM32F103RB. The patch assumes that other MCUs from STM32 family will be included under arch/arm/soc/st_stm32 tree, to achieve the following layout: arch/ arm/ soc/ st_stm32/ stm32f0/ stm32f1/ stm32f2/ ... stm32l0/ Most of the configuration within a single MCU family (ex. STM32F1) is shared, however individual MCUs differ with respect to SRAM size, flash size or the number of available peripherals. The patch assumes that per MCU line Kconfig.soc.family file should introduce basic setup for given series. This can be further tuned by per MCU files, with Kconfig.soc.stm32f103rb and Kconfig.soc.stm32f103ve as examples. Each family defines a configuration option, ex. CONFIG_STM32F10X, while individual MCUs define a corresponding per MCU config options, ex. CONFIG_STM32F103VE. From the menuconfig perspective, the user is presented with a family selection under General Platform Configuration/SoC Selection. A specific MCU model can be selected by accessing General Platform Configuration/STM32F1x MCU Selection, with the default entry being selected by the board configuration. Change-Id: I22e4defd4a08ed1b2e2cad0e214b34f565e08831 Origin: Original Signed-off-by: Maciej Borzecki <maciek.borzecki@gmail.com>
2016-03-03 22:32:21 +08:00
#
stm32: rename SOC_STM32F1X -> SOC_SERIES_STM32F1X Use SOC_SERIES_* for naming SoCs with similar features and architectures with the goal of code reuse. The Series in the config variable should avoid name collisions and clearly denote the relationships within an SoC family. Change-Id: I7a98542f96b5d5dc3acc23782c4d45f98cceb599 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-04-03 10:40:26 +08:00
if SOC_SERIES_STM32F1X
st_stm32/stm32f1: introduce STM32F1x SoC family The patch introduces a new family of SoCs based on STMicroelectronics' STM32 MCU line. The patch introduces a basic arch/arm/soc layout along with configuration of 2 MCUs from STM32F1 series: STM32F103VE and STM32F103RB. The patch assumes that other MCUs from STM32 family will be included under arch/arm/soc/st_stm32 tree, to achieve the following layout: arch/ arm/ soc/ st_stm32/ stm32f0/ stm32f1/ stm32f2/ ... stm32l0/ Most of the configuration within a single MCU family (ex. STM32F1) is shared, however individual MCUs differ with respect to SRAM size, flash size or the number of available peripherals. The patch assumes that per MCU line Kconfig.soc.family file should introduce basic setup for given series. This can be further tuned by per MCU files, with Kconfig.soc.stm32f103rb and Kconfig.soc.stm32f103ve as examples. Each family defines a configuration option, ex. CONFIG_STM32F10X, while individual MCUs define a corresponding per MCU config options, ex. CONFIG_STM32F103VE. From the menuconfig perspective, the user is presented with a family selection under General Platform Configuration/SoC Selection. A specific MCU model can be selected by accessing General Platform Configuration/STM32F1x MCU Selection, with the default entry being selected by the board configuration. Change-Id: I22e4defd4a08ed1b2e2cad0e214b34f565e08831 Origin: Original Signed-off-by: Maciej Borzecki <maciek.borzecki@gmail.com>
2016-03-03 22:32:21 +08:00
Kconfig: Switch to improved globbing statements A design flaw of 'gsource' is that there's no way to require at least one file to match the glob pattern. This could lead to silent errors. Switch to a new design, where a plain 'source' is globbing and requires at least one file to match. A separate 'osource' (optional source) statement is available for cases where it's okay for a pattern (or plain filename) to not match any files. 'orsource' combines 'osource' and 'rsource' (relative source). This commit search-replaces 'gsource' with 'source', but backwards compatibility with 'gsource' is still maintained by making it an alias for 'osource' (and by making 'grsource' an alias for 'orsource'). The three Kconfig files arch/{nios2,posix,xtensa}/Kconfig source arch/{nios2,posix,xtensa}/soc/*/Kconfig, which doesn't match any files. Use 'osource' for those. The soc/*/Kconfig files seem to be for additional SoC-specific symbols, only none exist yet on those ARCHes. Also use 'osource' for the source of $ENV_VAR_BOARD_DIR/Kconfig in boards/Kconfig, which doesn't exist for all boards. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 13:20:30 +08:00
source "arch/arm/soc/st_stm32/stm32f1/Kconfig.defconfig.stm32f1*"
st_stm32/stm32f1: introduce STM32F1x SoC family The patch introduces a new family of SoCs based on STMicroelectronics' STM32 MCU line. The patch introduces a basic arch/arm/soc layout along with configuration of 2 MCUs from STM32F1 series: STM32F103VE and STM32F103RB. The patch assumes that other MCUs from STM32 family will be included under arch/arm/soc/st_stm32 tree, to achieve the following layout: arch/ arm/ soc/ st_stm32/ stm32f0/ stm32f1/ stm32f2/ ... stm32l0/ Most of the configuration within a single MCU family (ex. STM32F1) is shared, however individual MCUs differ with respect to SRAM size, flash size or the number of available peripherals. The patch assumes that per MCU line Kconfig.soc.family file should introduce basic setup for given series. This can be further tuned by per MCU files, with Kconfig.soc.stm32f103rb and Kconfig.soc.stm32f103ve as examples. Each family defines a configuration option, ex. CONFIG_STM32F10X, while individual MCUs define a corresponding per MCU config options, ex. CONFIG_STM32F103VE. From the menuconfig perspective, the user is presented with a family selection under General Platform Configuration/SoC Selection. A specific MCU model can be selected by accessing General Platform Configuration/STM32F1x MCU Selection, with the default entry being selected by the board configuration. Change-Id: I22e4defd4a08ed1b2e2cad0e214b34f565e08831 Origin: Original Signed-off-by: Maciej Borzecki <maciek.borzecki@gmail.com>
2016-03-03 22:32:21 +08:00
stm32: reorganise soc directory and use family/series Use SoC family/series and reoganise the structure to follow new hierarchy. Change-Id: I8637f1487a8287a6614ce6636cd018cf342fec95 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-04-03 11:36:02 +08:00
config SOC_SERIES
soc: defconfig.series: Consistently quote string defaults In preparation for introducing a warning. Unquoted string defaults work through a quirk of Kconfig (undefined symbols get their name as their string value), but look confusing. It's done inconsistently now too. Suggested by Kumar Gala. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-05-26 03:09:37 +08:00
default "stm32f1"
st_stm32/stm32f1: introduce STM32F1x SoC family The patch introduces a new family of SoCs based on STMicroelectronics' STM32 MCU line. The patch introduces a basic arch/arm/soc layout along with configuration of 2 MCUs from STM32F1 series: STM32F103VE and STM32F103RB. The patch assumes that other MCUs from STM32 family will be included under arch/arm/soc/st_stm32 tree, to achieve the following layout: arch/ arm/ soc/ st_stm32/ stm32f0/ stm32f1/ stm32f2/ ... stm32l0/ Most of the configuration within a single MCU family (ex. STM32F1) is shared, however individual MCUs differ with respect to SRAM size, flash size or the number of available peripherals. The patch assumes that per MCU line Kconfig.soc.family file should introduce basic setup for given series. This can be further tuned by per MCU files, with Kconfig.soc.stm32f103rb and Kconfig.soc.stm32f103ve as examples. Each family defines a configuration option, ex. CONFIG_STM32F10X, while individual MCUs define a corresponding per MCU config options, ex. CONFIG_STM32F103VE. From the menuconfig perspective, the user is presented with a family selection under General Platform Configuration/SoC Selection. A specific MCU model can be selected by accessing General Platform Configuration/STM32F1x MCU Selection, with the default entry being selected by the board configuration. Change-Id: I22e4defd4a08ed1b2e2cad0e214b34f565e08831 Origin: Original Signed-off-by: Maciej Borzecki <maciek.borzecki@gmail.com>
2016-03-03 22:32:21 +08:00
boards: stm32f1: Clean up driver generic flags Clean up driver generic flags from boards' _defconfig files Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2017-12-29 03:31:02 +08:00
if GPIO_STM32
soc/stm32f1: Enable IWDG_STM32 dependent on WATCHDOG The STM32F1 range all have the independent watchdog, enable the driver by default if CONFIG_WATCHDOG is enabled. Change-Id: I3869884dc51c56194367b46007c87f6cee699689 Signed-off-by: Marcus Shawcroft <marcus.shawcroft@arm.com>
2016-10-26 19:54:22 +08:00
boards: stm32f1: Clean up driver generic flags Clean up driver generic flags from boards' _defconfig files Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2017-12-29 03:31:02 +08:00
config GPIO_STM32_PORTD
default y
endif # GPIO_STM32
drivers/i2c: Cleanup Kconfig Move driver specific to dedicated file when relevant (i.e.: more than 1-2 options), use if/endif also. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2018-02-28 18:27:46 +08:00
if I2C_STM32
boards: stm32f1: Clean up driver generic flags Clean up driver generic flags from boards' _defconfig files Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2017-12-29 03:31:02 +08:00
drivers/i2c: Cleanup Kconfig Move driver specific to dedicated file when relevant (i.e.: more than 1-2 options), use if/endif also. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2018-02-28 18:27:46 +08:00
config I2C_STM32_V1
soc/stm32f1: Enable IWDG_STM32 dependent on WATCHDOG The STM32F1 range all have the independent watchdog, enable the driver by default if CONFIG_WATCHDOG is enabled. Change-Id: I3869884dc51c56194367b46007c87f6cee699689 Signed-off-by: Marcus Shawcroft <marcus.shawcroft@arm.com>
2016-10-26 19:54:22 +08:00
def_bool y
drivers/i2c: Cleanup Kconfig Move driver specific to dedicated file when relevant (i.e.: more than 1-2 options), use if/endif also. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2018-02-28 18:27:46 +08:00
endif # I2C_STM32
soc/stm32f1: Enable IWDG_STM32 dependent on WATCHDOG The STM32F1 range all have the independent watchdog, enable the driver by default if CONFIG_WATCHDOG is enabled. Change-Id: I3869884dc51c56194367b46007c87f6cee699689 Signed-off-by: Marcus Shawcroft <marcus.shawcroft@arm.com>
2016-10-26 19:54:22 +08:00
stm32: rename SOC_STM32F1X -> SOC_SERIES_STM32F1X Use SOC_SERIES_* for naming SoCs with similar features and architectures with the goal of code reuse. The Series in the config variable should avoid name collisions and clearly denote the relationships within an SoC family. Change-Id: I7a98542f96b5d5dc3acc23782c4d45f98cceb599 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-04-03 10:40:26 +08:00
endif # SOC_SERIES_STM32F1X