linux-kernel - Re: [PATCH] timekeeping: Move persistent clock registration code from ARM to kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20141110095325.GC12126@ulmo>
Date:	Mon, 10 Nov 2014 10:53:26 +0100
From:	Thierry Reding <thierry.reding@...il.com>
To:	Anatol Pomozov <anatol.pomozov@...il.com>
Cc:	swarren@...dotorg.org, daniel.lezcano@...aro.org,
	linux@....linux.org.uk, tglx@...utronix.de,
	linux-kernel@...r.kernel.org, linux-tegra@...r.kernel.org,
	tony@...mide.com, mark.rutland@....com
Subject: Re: [PATCH] timekeeping: Move persistent clock registration code
 from ARM to kernel

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.

Thierry

Content of type "application/pgp-signature" skipped