Hi On Mon, Nov 10, 2014 at 1:53 AM, Thierry Reding <thierry.reding@xxxxxxxxx> wrote: > On Fri, Nov 07, 2014 at 11:34:15AM -0800, Anatol Pomozov wrote: >> ARM timekeeping functionality allows to register persistent/boot clock dynamically. >> This code is arch-independent and can be useful on other plaforms as well. >> >> As a byproduct of this change, tegra20_timer becomes ARM64 compatible. >> >> Tested: backported the change to chromeos-3.14 kernel ran on tegra 64bit >> board, made sure high-resolution clock works. > > Using this on an upstream kernel doesn't work, though, because 64-bit > ARM doesn't implement struct delay_timer which the driver needs since > v3.17. > > But I suppose the delay timer infrastructure could be moved into the > core similar to the persistent and boot clock as this patch does. Thanks. It makes sense, I will send it in a separate patch, once this one will be reviewed. On our kernel I haven't seen this issue as we still use 3.14. In fact none of arch/arm/lib/delay.c code seems ARM32 related. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
