OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/spi/Kconfig.stm32

34 lines
844 B
Plaintext
Raw Normal View History

kconfig: Clean up header comments and make them consistent Use this short header style in all Kconfig files: # <description> # <copyright> # <license> ... Also change all <description>s from # Kconfig[.extension] - Foo-related options to just # Foo-related options It's clear enough that it's about Kconfig. The <description> cleanup was done with this command, along with some manual cleanup (big letter at the start, etc.) git ls-files '*Kconfig*' | \ xargs sed -i -E '1 s/#\s*Kconfig[\w.-]*\s*-\s*/# /' Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 20:45:29 +08:00
# STM32 SPI driver configuration options
drivers/spi: Cleanup the Kconfig files Split QMSI relevant part into its own file. Some config where using prompt, some not: normalizing it by removing the prompt keyword where relevant. Reducing the file by using if/endif when relevant. However, it still not fully clean default: cfg and default baudrate should disappear. There is no default configuration to apply as long as the controller is not configured to run from any part using spi API. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2017-06-21 15:16:25 +08:00
# Copyright (c) 2015-2016 Intel Corporation
# SPDX-License-Identifier: Apache-2.0
menuconfig SPI_STM32
bool "STM32 MCU SPI controller driver"
kconfig: drivers: spi: Remove duplicated dependencies The two redundant SPI dependencies are from 'source'ing a file within an 'if SPI' and then adding another 'depends on SPI' within it. 'if FOO' is just shorthand for adding depends on FOO to each item within the 'if'. There are no "conditional includes" in Kconfig, so 'if FOO' has no special meaning around a source. Conditional includes wouldn't be possible, because an if condition could include (directly or indirectly) forward references to symbols not defined yet. Tip: When adding a symbol, check its dependencies in the menuconfig ('ninja menuconfig', then / to jump to the symbol). The menuconfig also shows how the file with the symbol got included, so if you see duplicated dependencies, it's easy to hunt down where they come from. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-07 13:55:22 +08:00
depends on SOC_FAMILY_STM32
drivers/spi: Cleanup the Kconfig files Split QMSI relevant part into its own file. Some config where using prompt, some not: normalizing it by removing the prompt keyword where relevant. Reducing the file by using if/endif when relevant. However, it still not fully clean default: cfg and default baudrate should disappear. There is no default configuration to apply as long as the controller is not configured to run from any part using spi API. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2017-06-21 15:16:25 +08:00
select USE_STM32_LL_SPI
help
Enable SPI support on the STM32 family of processors.
if SPI_STM32
config SPI_STM32_HAS_FIFO
bool
drivers: spi: spi_ll_stm32: Add support for STM32MP1x SoC Add SPI driver support for STM32MP1x SoC. Signed-off-by: Yaël Boutreux <yael.boutreux@st.com> Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@st.com> Signed-off-by: Alexandre Torgue <alexandre.torgue@st.com>
2019-08-02 13:53:07 +08:00
depends on (SOC_SERIES_STM32L4X || SOC_SERIES_STM32F0X || \
SOC_SERIES_STM32F3X || SOC_SERIES_STM32F7X || SOC_SERIES_STM32MP1X || \
drivers: spi: Add STM32G4X SPI support Add SPI driver support for STM32G4X SoC series. Signed-off-by: Richard Osterloh <richard.osterloh@gmail.com>
2019-09-04 16:45:03 +08:00
SOC_SERIES_STM32WBX || SOC_SERIES_STM32G4X)
drivers/spi: Cleanup the Kconfig files Split QMSI relevant part into its own file. Some config where using prompt, some not: normalizing it by removing the prompt keyword where relevant. Reducing the file by using if/endif when relevant. However, it still not fully clean default: cfg and default baudrate should disappear. There is no default configuration to apply as long as the controller is not configured to run from any part using spi API. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2017-06-21 15:16:25 +08:00
default y
config SPI_STM32_INTERRUPT
bool "STM32 MCU SPI Interrupt Support"
help
Enable Interrupt support for the SPI Driver of STM32 family.
drivers: spi: spi_ll_stm32: Add config to manage slave select Allow the user to use software slave select instead of the hardware pin, in order to free the related GPIO and avoid unwanted SS triggering on the hardware pin. The default SS is still the hardware pin. Signed-off-by: Yaël Boutreux <yael.boutreux@st.com> Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@st.com> Signed-off-by: Alexandre Torgue <alexandre.torgue@st.com>
2019-07-24 14:23:52 +08:00
config SPI_STM32_USE_HW_SS
bool "STM32 Hardware Slave Select support"
default y
help
Use Slave Select pin instead of software Slave Select.
drivers/spi: Cleanup the Kconfig files Split QMSI relevant part into its own file. Some config where using prompt, some not: normalizing it by removing the prompt keyword where relevant. Reducing the file by using if/endif when relevant. However, it still not fully clean default: cfg and default baudrate should disappear. There is no default configuration to apply as long as the controller is not configured to run from any part using spi API. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2017-06-21 15:16:25 +08:00
endif # SPI_STM32