aboutsummaryrefslogtreecommitdiff
path: root/drivers/mtd
diff options
context:
space:
mode:
authorTom Rini <trini@konsulko.com>2022-07-23 13:05:00 -0400
committerTom Rini <trini@konsulko.com>2022-08-04 16:18:47 -0400
commit5d68d2f41df5099f890052756f14f5a810f34312 (patch)
tree2481188e8c651c8da0acb1890fad4a670bb3e1a0 /drivers/mtd
parent90e9b3d3353300bc65fbd7f400228926ee61b30c (diff)
downloadu-boot-5d68d2f41df5099f890052756f14f5a810f34312.zip
u-boot-5d68d2f41df5099f890052756f14f5a810f34312.tar.gz
u-boot-5d68d2f41df5099f890052756f14f5a810f34312.tar.bz2
Convert CONFIG_SYS_FLASH_ERASE_TOUT et al to Kconfig
This converts the following to Kconfig: CONFIG_SYS_FLASH_ERASE_TOUT CONFIG_SYS_FLASH_LOCK_TOUT CONFIG_SYS_FLASH_UNLOCK_TOUT CONFIG_SYS_FLASH_WRITE_TOUT In practice, for two m68k platforms we move to hard-coding with a comment the timeout values, rather than try and make convoluted Kconfig logic. We add options for the write and erase options to the pic32 flash driver, as this driver does make use of them. Everywhere else these are unreferenced values. Signed-off-by: Tom Rini <trini@konsulko.com>
Diffstat (limited to 'drivers/mtd')
-rw-r--r--drivers/mtd/Kconfig12
1 files changed, 12 insertions, 0 deletions
diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig
index 985cc01..e28ff04 100644
--- a/drivers/mtd/Kconfig
+++ b/drivers/mtd/Kconfig
@@ -157,6 +157,18 @@ config FLASH_PIC32
This enables access to Microchip PIC32 internal non-CFI flash
chips through PIC32 Non-Volatile-Memory Controller.
+config SYS_FLASH_ERASE_TOUT
+ int "Timeout in ms for performing an erase operation on the flash"
+ depends on FLASH_PIC32
+ help
+ Timeout for Flash erase operations (in ms)
+
+config SYS_FLASH_WRITE_TOUT
+ int "Timeout in ms for performing a write operation on the flash"
+ depends on FLASH_PIC32
+ help
+ Timeout for Flash write operations (in ms)
+
config RENESAS_RPC_HF
bool "Renesas RCar Gen3 RPC HyperFlash driver"
depends on RCAR_GEN3 && DM_MTD