On 23 June 2015 at 15:39, Simon Glass sjg@chromium.org wrote:
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
Changes in v3: None Changes in v2: None
drivers/misc/Kconfig | 9 +++++++ drivers/misc/Makefile | 1 + drivers/misc/reset-uclass.c | 62 +++++++++++++++++++++++++++++++++++++++++++++ include/dm/uclass-id.h | 1 + include/reset.h | 62 +++++++++++++++++++++++++++++++++++++++++++++ 5 files changed, 135 insertions(+) create mode 100644 drivers/misc/reset-uclass.c create mode 100644 include/reset.h
Applied to u-boot-dm.