diff options
author | Simon Glass <sjg@chromium.org> | 2015-06-24 00:39:13 +0300 |
---|---|---|
committer | Simon Glass <sjg@chromium.org> | 2015-07-22 02:39:29 +0300 |
commit | f9917454d55caf3dafa41b27d8d8274716433a4c (patch) | |
tree | 81f7c0e4cb2a9c3e04eab94ef17da21f2de1192f /drivers/misc/Makefile | |
parent | 92a655c326b22de58dcd5371ca1a62fdc57f8e04 (diff) | |
download | u-boot-f9917454d55caf3dafa41b27d8d8274716433a4c.tar.xz |
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/Makefile')
-rw-r--r-- | drivers/misc/Makefile | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/misc/Makefile b/drivers/misc/Makefile index 120babc4b5..5da5178737 100644 --- a/drivers/misc/Makefile +++ b/drivers/misc/Makefile @@ -32,3 +32,4 @@ obj-$(CONFIG_TWL4030_LED) += twl4030_led.o obj-$(CONFIG_FSL_IFC) += fsl_ifc.o obj-$(CONFIG_FSL_SEC_MON) += fsl_sec_mon.o obj-$(CONFIG_PCA9551_LED) += pca9551_led.o +obj-$(CONFIG_RESET) += reset-uclass.o |