:orphan: .. title:: CONFIG_SOC_FLASH_RV32M1 .. kconfig:: CONFIG_SOC_FLASH_RV32M1 CONFIG_SOC_FLASH_RV32M1 ####################### *RV32M1 flash shim driver* Type: ``bool`` Help ==== .. code-block:: none Enables the RV32M1 flash shim driver. WARNING: This driver will disable the system interrupts for the duration of the flash erase/write operations. This will have an impact on the overall system performance - whether this is acceptable or not will depend on the use case. Direct dependencies =================== (\ :kconfig:`FLASH ` && \ :kconfig:`SOC_OPENISA_RV32M1_RISCV32 `) || (\ :kconfig:`FLASH ` && \ :kconfig:`SOC_OPENISA_RV32M1_RISCV32 `) || (\ :kconfig:`HAS_RV32M1_FTFX ` && \ :kconfig:`FLASH `) *(Includes any dependencies from ifs and menus.)* Defaults ======== - y - y Symbols selected by this symbol =============================== - \ :kconfig:`FLASH_HAS_PAGE_LAYOUT ` - \ :kconfig:`FLASH_HAS_DRIVER_ENABLED ` Kconfig definitions =================== At ``/riscv/openisa_rv32m1/Kconfig.defconfig:150`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:25`` → ``/kconfig/Kconfig.soc.defconfig:1`` Menu path: (Top) .. code-block:: kconfig config SOC_FLASH_RV32M1 bool default y depends on FLASH && SOC_OPENISA_RV32M1_RISCV32 ---- At ``/riscv/openisa_rv32m1/Kconfig.defconfig:150`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:27`` Menu path: (Top) .. code-block:: kconfig config SOC_FLASH_RV32M1 bool default y depends on FLASH && SOC_OPENISA_RV32M1_RISCV32 ---- At ``/flash/Kconfig.rv32m1:4`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:42`` → ``/Kconfig:62`` → ``/flash/Kconfig:91`` Menu path: (Top) → Device Drivers → Flash hardware support .. code-block:: kconfig config SOC_FLASH_RV32M1 bool "RV32M1 flash shim driver" select FLASH_HAS_PAGE_LAYOUT select FLASH_HAS_DRIVER_ENABLED depends on HAS_RV32M1_FTFX && FLASH help Enables the RV32M1 flash shim driver. WARNING: This driver will disable the system interrupts for the duration of the flash erase/write operations. This will have an impact on the overall system performance - whether this is acceptable or not will depend on the use case. *(The 'depends on' condition includes propagated dependencies from ifs and menus.)*