08 May, 2017
1 commit
-
This change switches all existing users of ast2500 Watchdog to Driver
Model based Watchdog driver.To perform system reset Sysreset Driver uses first Watchdog device found
via uclass_first_device call. Since the system is going to be reset
anyway it does not make much difference which watchdog is used.Instead of using Watchdog to reset itself, SDRAM driver now uses Reset
driver to do that.These were the only users of the old Watchdog API, so that API is
removed.This all is done in one change to avoid having to maintain dual API for
watchdog in between.Signed-off-by: Maxim Sloyko
Reviewed-by: Simon Glass
29 Jan, 2017
1 commit
-
Add support for Watchdog Timer, which is compatible with AST2400 and
AST2500 watchdogs. There is no uclass for Watchdog yet, so the driver
does not follow the driver model. It also uses fixed clock, so no clock
driver is needed.Add support for timer for Aspeed ast2400/ast2500 devices.
The driver actually controls several devices, but because all devices
share the same Control Register, it is somewhat difficult to completely
decouple them. Since only one timer is needed at the moment, this should
be OK. The timer uses fixed clock, so does not rely on a clock driver.Add sysreset driver, which uses watchdog timer to do resets and particular
watchdog device to use is hardcoded (0)
Reviewed-by: Simon Glass