michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/drivers/flash/Kconfig.stm32_qspi

43 lines
1.3 KiB
Text
Raw Permalink Normal View History

drivers/flash: stm32: Add qspi-nor flash-controller Add support for DMA based STM32 QSPI NOR flash controller. Driver configures both NOR flash and also QSPI hardware block. Reuses existing jesd216 library. QSPI hardware block handling is done through the use of Cube HAL API. This requires the use of HAL interface also for DMA besides zephyr DMA driver. Zephyr DMA driver is used only for IRQ routing while HAL driver handles the IP block. To achieve this it is required to: -Configure both Cube and Zephyr drivers at init. -Inform Zephyr driver that current channel handling will be done by another instance and only a limited configuration should be done. For this last part, a unused parameter is overridden in order to transmit the information. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org> Signed-off-by: Piotr Mienkowski <piotr.mienkowski@gmail.com>
2021-01-12 09:33:02 +01:00
# STM32 Quad SPI flash driver configuration options
# Copyright (c) 2020 Piotr Mienkowski
# Copyright (c) 2020 Linaro Limited
# SPDX-License-Identifier: Apache-2.0
drivers : flash: replace dt_nodelabel_has_prop()in qspi Replace dt_nodelabel_has_prop() with dt_compat_any_has_prop() in Kconfig.stm32_qspi Signed-off-by: Khaoula Bidani <khaoula.bidani-ext@st.com>
2025-02-03 11:25:51 +01:00
DT_STM32_QUADSPI_HAS_DMA := $(dt_compat_any_has_prop,$(DT_COMPAT_ST_STM32_QSPI),dmas)
drivers/flash: stm32: Add qspi-nor flash-controller Add support for DMA based STM32 QSPI NOR flash controller. Driver configures both NOR flash and also QSPI hardware block. Reuses existing jesd216 library. QSPI hardware block handling is done through the use of Cube HAL API. This requires the use of HAL interface also for DMA besides zephyr DMA driver. Zephyr DMA driver is used only for IRQ routing while HAL driver handles the IP block. To achieve this it is required to: -Configure both Cube and Zephyr drivers at init. -Inform Zephyr driver that current channel handling will be done by another instance and only a limited configuration should be done. For this last part, a unused parameter is overridden in order to transmit the information. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org> Signed-off-by: Piotr Mienkowski <piotr.mienkowski@gmail.com>
2021-01-12 09:33:02 +01:00
drivers: flash: stm32: add "generic read/write" ex op to QSPI driver Some external flash modules have extra commands to support, for example, reading/writing an OTP zone. Given that the commands are highly specific and difficult to generalize, we add two ex ops that can be used to transmit a custom command (in the form of a full QSPI_CommandTypeDef) and then read or write a user-provided buffer. Signed-off-by: Federico Di Gregorio <fog@dndg.it>
2025-06-04 10:52:29 +02:00
menuconfig FLASH_STM32_QSPI
drivers/flash: stm32: Add qspi-nor flash-controller Add support for DMA based STM32 QSPI NOR flash controller. Driver configures both NOR flash and also QSPI hardware block. Reuses existing jesd216 library. QSPI hardware block handling is done through the use of Cube HAL API. This requires the use of HAL interface also for DMA besides zephyr DMA driver. Zephyr DMA driver is used only for IRQ routing while HAL driver handles the IP block. To achieve this it is required to: -Configure both Cube and Zephyr drivers at init. -Inform Zephyr driver that current channel handling will be done by another instance and only a limited configuration should be done. For this last part, a unused parameter is overridden in order to transmit the information. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org> Signed-off-by: Piotr Mienkowski <piotr.mienkowski@gmail.com>
2021-01-12 09:33:02 +01:00
bool "STM32 Quad SPI Flash driver"
drivers: flash: Update drivers to use devicetree Kconfig symbol Update flash drivers to use DT_HAS_<compat>_ENABLED Kconfig symbol to expose the driver and enable it by default based on devicetree. We remove 'depend on' Kconfig for symbols that would be implied by the devicetree node existing. Signed-off-by: Kumar Gala <galak@kernel.org>
2022-07-22 01:53:16 -05:00
default y
depends on DT_HAS_ST_STM32_QSPI_NOR_ENABLED
drivers/flash: stm32: Add qspi-nor flash-controller Add support for DMA based STM32 QSPI NOR flash controller. Driver configures both NOR flash and also QSPI hardware block. Reuses existing jesd216 library. QSPI hardware block handling is done through the use of Cube HAL API. This requires the use of HAL interface also for DMA besides zephyr DMA driver. Zephyr DMA driver is used only for IRQ routing while HAL driver handles the IP block. To achieve this it is required to: -Configure both Cube and Zephyr drivers at init. -Inform Zephyr driver that current channel handling will be done by another instance and only a limited configuration should be done. For this last part, a unused parameter is overridden in order to transmit the information. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org> Signed-off-by: Piotr Mienkowski <piotr.mienkowski@gmail.com>
2021-01-12 09:33:02 +01:00
select USE_STM32_HAL_QSPI
kconfig: stm32: Select CONFIG_USE_STM32_HAL_MDMA when QSPI is used The stm32 HAL code for qspi (SHA1: 5c8275071ec1cf160bfe8c18bbd93): stm32cube/stm32h7xx/drivers/src/stm32h7xx_hal_qspi.c implicitly depends on the stm32h7xx_hal_mdma.c driver as it uses unconditionally 'HAL_MDMA_Abort_IT()' function. To avoid build breaks - no matter if QSPI IP block works with DMA or interrupts - the CONFIG_USE_STM32_HAL_MDMA shall be defined. Signed-off-by: Lukasz Majewski <lukma@denx.de>
2021-12-02 16:08:25 +01:00
select USE_STM32_HAL_MDMA if SOC_SERIES_STM32H7X
drivers/flash: stm32: Add qspi-nor flash-controller Add support for DMA based STM32 QSPI NOR flash controller. Driver configures both NOR flash and also QSPI hardware block. Reuses existing jesd216 library. QSPI hardware block handling is done through the use of Cube HAL API. This requires the use of HAL interface also for DMA besides zephyr DMA driver. Zephyr DMA driver is used only for IRQ routing while HAL driver handles the IP block. To achieve this it is required to: -Configure both Cube and Zephyr drivers at init. -Inform Zephyr driver that current channel handling will be done by another instance and only a limited configuration should be done. For this last part, a unused parameter is overridden in order to transmit the information. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org> Signed-off-by: Piotr Mienkowski <piotr.mienkowski@gmail.com>
2021-01-12 09:33:02 +01:00
select FLASH_HAS_DRIVER_ENABLED
select FLASH_JESD216
select FLASH_HAS_PAGE_LAYOUT
drivers/flash: Add explict erase capability with proper values Add explicit_erase capability and set proper value to it, depending on type of a device. Select FLASH_HAS_EXPLICIT_ERASE by devices that have program-erase characteristics and FLASH_HAS_NO_EXPLICIT_ERASE, where needed. Signed-off-by: Dominik Ermel <dominik.ermel@nordicsemi.no>
2024-02-02 13:46:29 +00:00
select FLASH_HAS_EXPLICIT_ERASE
drivers: stm32: Select PINCTRL when required Select PINCTRL subsystem by drivers which require it. Prevent the need from enabling this symbol at board or soc level. Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
2024-08-29 16:04:49 +02:00
select PINCTRL
drivers/flash: flash_stm32_qspi: Set DMA as optional In order to ease reuse on other series, set DMA as optional and use IT if no DMA channel is specified in the qspi node. Tested on disco_l475_iot1 Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2021-01-07 10:21:47 +01:00
select DMA if $(DT_STM32_QUADSPI_HAS_DMA)
select USE_STM32_HAL_DMA if $(DT_STM32_QUADSPI_HAS_DMA)
drivers/flash: stm32: Add qspi-nor flash-controller Add support for DMA based STM32 QSPI NOR flash controller. Driver configures both NOR flash and also QSPI hardware block. Reuses existing jesd216 library. QSPI hardware block handling is done through the use of Cube HAL API. This requires the use of HAL interface also for DMA besides zephyr DMA driver. Zephyr DMA driver is used only for IRQ routing while HAL driver handles the IP block. To achieve this it is required to: -Configure both Cube and Zephyr drivers at init. -Inform Zephyr driver that current channel handling will be done by another instance and only a limited configuration should be done. For this last part, a unused parameter is overridden in order to transmit the information. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org> Signed-off-by: Piotr Mienkowski <piotr.mienkowski@gmail.com>
2021-01-12 09:33:02 +01:00
help
Enable QSPI-NOR support on the STM32 family of processors.
drivers: flash: stm32: add "generic read/write" ex op to QSPI driver Some external flash modules have extra commands to support, for example, reading/writing an OTP zone. Given that the commands are highly specific and difficult to generalize, we add two ex ops that can be used to transmit a custom command (in the form of a full QSPI_CommandTypeDef) and then read or write a user-provided buffer. Signed-off-by: Federico Di Gregorio <fog@dndg.it>
2025-06-04 10:52:29 +02:00
if FLASH_STM32_QSPI
config FLASH_STM32_QSPI_GENERIC_READ
bool "Generic read command extended operation"
select FLASH_HAS_EX_OP
help
Enables flash extended operation that can be used to transmit
a custom command and read the result to a user-provided buffer.
config FLASH_STM32_QSPI_GENERIC_WRITE
bool "Generic write command extended operation"
select FLASH_HAS_EX_OP
help
Enables flash extended operation that can be used to transmit
a custom command and write data taken from a user-provided
buffer.
endif # FLASH_STM32_QSPI
Copy permalink