summaryrefslogtreecommitdiff
path: root/drivers/misc/Kconfig
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2015-06-23 15:39:13 -0600
committerSimon Glass <sjg@chromium.org>2015-07-21 17:39:29 -0600
commitf9917454d55caf3dafa41b27d8d8274716433a4c (patch)
tree81f7c0e4cb2a9c3e04eab94ef17da21f2de1192f /drivers/misc/Kconfig
parent92a655c326b22de58dcd5371ca1a62fdc57f8e04 (diff)
downloadu-boot-f9917454d55caf3dafa41b27d8d8274716433a4c.tar.gz
u-boot-f9917454d55caf3dafa41b27d8d8274716433a4c.tar.bz2
u-boot-f9917454d55caf3dafa41b27d8d8274716433a4c.zip
dm: Add a system reset uclass
It is common for system reset to be available at multiple levels in modern hardware. For example, an SoC may provide a reset option, and a board may provide its own reset for reasons of security or thoroughness. It is useful to be able to model this hardware without hard-coding the behaviour in the SoC or board. Also there is a distinction sometimes between resetting just the CPU (leaving GPIO state alone) and resetting all the PMICs, just cutting power. To achieve this, add a simple system reset uclass. It allows multiple devices to provide reset functionality and provides a way to walk through them, requesting a particular reset type until is it provided. Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'drivers/misc/Kconfig')
-rw-r--r--drivers/misc/Kconfig9
1 files changed, 9 insertions, 0 deletions
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index 64b07a3015..3b7f76ab78 100644
--- a/drivers/misc/Kconfig
+++ b/drivers/misc/Kconfig
@@ -73,3 +73,12 @@ config PCA9551_I2C_ADDR
default 0x60
help
The I2C address of the PCA9551 LED controller.
+
+config RESET
+ bool "Enable support for reset drivers"
+ depends on DM
+ help
+ Enable reset drivers which can be used to reset the CPU or board.
+ Each driver can provide a reset method which will be called to
+ effect a reset. The uclass will try all available drivers when
+ reset_walk() is called.