diff options
| author | maxims@google.com <maxims@google.com> | 2017-01-18 13:44:55 -0800 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2017-01-28 14:04:27 -0500 |
| commit | 4697abea62a3b02c9c346b94d7eae2e4a1c6cfd0 (patch) | |
| tree | 0d21d52e0c75d0efe43fe37fed81d7256a14ff73 /drivers/timer/Kconfig | |
| parent | cd7b634413ea25838185db2faffc313d4d571fa9 (diff) | |
| download | u-boot-imx-4697abea62a3b02c9c346b94d7eae2e4a1c6cfd0.zip u-boot-imx-4697abea62a3b02c9c346b94d7eae2e4a1c6cfd0.tar.gz u-boot-imx-4697abea62a3b02c9c346b94d7eae2e4a1c6cfd0.tar.bz2 | |
aspeed: Add drivers common to all Aspeed SoCs
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 <sjg@chromium.org>
Diffstat (limited to 'drivers/timer/Kconfig')
| -rw-r--r-- | drivers/timer/Kconfig | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/drivers/timer/Kconfig b/drivers/timer/Kconfig index cb18f12..cd38a6d 100644 --- a/drivers/timer/Kconfig +++ b/drivers/timer/Kconfig @@ -46,4 +46,16 @@ config OMAP_TIMER help Select this to enable an timer for Omap devices. +config AST_TIMER + bool "Aspeed ast2400/ast2500 timer support" + depends on TIMER + default y if ARCH_ASPEED + help + Select this to enable timer for Aspeed ast2400/ast2500 devices. + This is a simple sys timer driver, it is compatible with lib/time.c, + but does not support any interrupts. Even though SoC has 8 hardware + counters, they are all treated as a single device by this driver. + This is mostly because they all share several registers which + makes it difficult to completely separate them. + endmenu |