From: Thierry Reding <thierry.reding@gmail.com>
To: Anatol Pomozov <anatol.pomozov@gmail.com>
Cc: swarren@wwwdotorg.org, daniel.lezcano@linaro.org,
linux@arm.linux.org.uk, tglx@linutronix.de,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
tony@atomide.com, mark.rutland@arm.com
Subject: Re: [PATCH] timekeeping: Move persistent clock registration code from ARM to kernel
Date: Mon, 10 Nov 2014 10:53:26 +0100 [thread overview]
Message-ID: <20141110095325.GC12126@ulmo> (raw)
In-Reply-To: <1415388855-35074-1-git-send-email-anatol.pomozov@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
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
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-10 9:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 19:34 [PATCH] timekeeping: Move persistent clock registration code from ARM to kernel Anatol Pomozov
2014-11-07 19:42 ` Anatol Pomozov
2014-11-10 9:53 ` Thierry Reding [this message]
2014-11-10 19:26 ` Anatol Pomozov
2014-11-13 22:46 ` Thomas Gleixner
2014-11-13 23:21 ` John Stultz
2014-11-14 0:26 ` Thomas Gleixner
2015-01-09 9:43 ` Thierry Reding
2015-01-09 19:18 ` John Stultz
2014-11-14 22:03 ` Anatol Pomozov
2014-11-15 0:18 ` Thomas Gleixner
2014-11-15 0:51 ` Anatol Pomozov
2014-11-15 1:09 ` Thomas Gleixner
2014-11-15 1:38 ` Thomas Gleixner
2015-01-09 9:49 ` Thierry Reding
2015-01-09 13:59 ` Mark Rutland
2015-01-09 14:09 ` Thierry Reding
2015-01-09 19:48 ` Paul Walmsley
2015-01-09 13:30 ` Daniel Lezcano
2014-11-15 1:07 ` Stephen Warren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141110095325.GC12126@ulmo \
--to=thierry.reding@gmail.com \
--cc=anatol.pomozov@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=swarren@wwwdotorg.org \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox