summaryrefslogtreecommitdiff
path: root/drivers/bootcount/Kconfig
diff options
context:
space:
mode:
authorAlex Kiernan <alex.kiernan@gmail.com>2018-02-16 15:50:42 +0000
committerTom Rini <trini@konsulko.com>2018-02-24 08:43:39 -0500
commitff5410d34b1ce3fa3785ecfd785704cfccc30938 (patch)
treea40a247a37aa48af77766ae49ecced298c187247 /drivers/bootcount/Kconfig
parent04c96ed2a6820ba2aee978826f96d464386b8cab (diff)
downloadu-boot-ff5410d34b1ce3fa3785ecfd785704cfccc30938.tar.gz
u-boot-ff5410d34b1ce3fa3785ecfd785704cfccc30938.tar.bz2
u-boot-ff5410d34b1ce3fa3785ecfd785704cfccc30938.zip
Convert CONFIG_BOOTCOUNT_RAM to Kconfig
This converts the following to Kconfig: CONFIG_BOOTCOUNT_RAM Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com> Reviewed-by: Lukasz Majewski <lukma@denx.de>
Diffstat (limited to 'drivers/bootcount/Kconfig')
-rw-r--r--drivers/bootcount/Kconfig6
1 files changed, 6 insertions, 0 deletions
diff --git a/drivers/bootcount/Kconfig b/drivers/bootcount/Kconfig
index 40a07555af..eabfd132ad 100644
--- a/drivers/bootcount/Kconfig
+++ b/drivers/bootcount/Kconfig
@@ -40,6 +40,12 @@ config BOOTCOUNT_ENV
So the Userspace Application must set the "upgrade_available"
and "bootcount" variable to 0, if a boot was successfully.
+config BOOTCOUNT_RAM
+ bool "Boot counter in RAM"
+ help
+ Store the bootcount in DRAM protected against against bit errors
+ due to short power loss or holding a system in RESET.
+
endchoice
config SYS_BOOTCOUNT_SINGLEWORD