diff options
author | Michal Simek <michal.simek@xilinx.com> | 2018-07-13 18:00:13 +0300 |
---|---|---|
committer | Michal Simek <michal.simek@xilinx.com> | 2018-07-19 11:49:55 +0300 |
commit | cae39ae365ed98b7cd0805fcb57ca4ee280b5ebe (patch) | |
tree | 417bc42b9fac7a09e97fa30439da142fadf28e94 /drivers/sysreset/Kconfig | |
parent | 0d832b322109e76953bc58e4d2723d2c73dfb604 (diff) | |
download | u-boot-cae39ae365ed98b7cd0805fcb57ca4ee280b5ebe.tar.xz |
sysreset: Add support for Microblaze soft reset jump
Microblaze is storing reset vector at address 0x0.
It means soft reset can be done by just jumping to this address.
This code was in platform code but sysreset interface is providing
enough capabilities to have more options how to reset the system. It can
go from gpio reset through watchdog reset till soft reset.
The driver has not compatible string because this is cpu specific and DM
core is not able to detect compatible string in DT root that's why this
driver will be instantiated from platform code by calling
device_bind_driver(gd->dm_root, "mb_soft_reset", "reset_soft",
NULL);
It should be bind as the last reset method to ensure that hw reset is
called before this.
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
Diffstat (limited to 'drivers/sysreset/Kconfig')
-rw-r--r-- | drivers/sysreset/Kconfig | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/drivers/sysreset/Kconfig b/drivers/sysreset/Kconfig index cec612ed50..f2524c18b7 100644 --- a/drivers/sysreset/Kconfig +++ b/drivers/sysreset/Kconfig @@ -23,6 +23,12 @@ config SYSRESET_GPIO example on Microblaze where reset logic can be controlled via GPIO pin which triggers cpu reset. +config SYSRESET_MICROBLAZE + bool "Enable support for Microblaze soft reset" + depends on MICROBLAZE + help + This is soft reset on Microblaze which does jump to 0x0 address. + config SYSRESET_PSCI bool "Enable support for PSCI System Reset" depends on ARM_PSCI_FW |