On 20/03/15 11:47, Thierry Reding wrote:
> From: Thierry Reding <tred...@nvidia.com>
>
> Some SoCs come with a custom timer interface, so allow them to use that
> instead.
>
> Cc: Albert Aribaud <albert.u.b...@aribaud.net>
> Cc: Marc Zyngier <marc.zyng...@arm.com>
> Signed-off-by: Thierry Reding <tred...@nvidia.com>
> ---
> arch/arm/cpu/armv8/generic_timer.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm/cpu/armv8/generic_timer.c
> b/arch/arm/cpu/armv8/generic_timer.c
> index 223b95e210ed..ab8573fc7cef 100644
> --- a/arch/arm/cpu/armv8/generic_timer.c
> +++ b/arch/arm/cpu/armv8/generic_timer.c
> @@ -9,6 +9,7 @@
> #include <command.h>
> #include <asm/system.h>
>
> +#ifndef CONFIG_SYS_TIMER_COUNTER
> /*
> * Generic timer implementation of get_tbclk()
> */
> @@ -29,3 +30,4 @@ unsigned long timer_read_counter(void)
> asm volatile("mrs %0, cntpct_el0" : "=r" (cntpct));
> return cntpct;
> }
> +#endif
>
Does it mean that in this case, the generic timers are not in a working
state? For ARMv8, it would make a lot more sense to make sure that the
basic CPU stuff is actually in a working state, and avoid the madness
that we have on ARMv7...
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
