summaryrefslogtreecommitdiff
path: root/drivers/sysreset/Makefile
diff options
context:
space:
mode:
authorMichal Simek <michal.simek@xilinx.com>2018-07-13 17:00:13 +0200
committerMichal Simek <michal.simek@xilinx.com>2018-07-19 10:49:55 +0200
commitcae39ae365ed98b7cd0805fcb57ca4ee280b5ebe (patch)
tree417bc42b9fac7a09e97fa30439da142fadf28e94 /drivers/sysreset/Makefile
parent0d832b322109e76953bc58e4d2723d2c73dfb604 (diff)
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/Makefile')
-rw-r--r--drivers/sysreset/Makefile1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/sysreset/Makefile b/drivers/sysreset/Makefile
index ca533cfefa..223a0716f0 100644
--- a/drivers/sysreset/Makefile
+++ b/drivers/sysreset/Makefile
@@ -4,6 +4,7 @@
obj-$(CONFIG_SYSRESET) += sysreset-uclass.o
obj-$(CONFIG_SYSRESET_GPIO) += sysreset_gpio.o
+obj-$(CONFIG_SYSRESET_MICROBLAZE) += sysreset_microblaze.o
obj-$(CONFIG_SYSRESET_PSCI) += sysreset_psci.o
obj-$(CONFIG_SYSRESET_SYSCON) += sysreset_syscon.o
obj-$(CONFIG_SYSRESET_WATCHDOG) += sysreset_watchdog.o