From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Anatol Pomozov <anatol.pomozov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org,
daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org
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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- 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 --]
WARNING: multiple messages have this Message-ID (diff)
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: 36+ 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:34 ` Anatol Pomozov
[not found] ` <1415388855-35074-1-git-send-email-anatol.pomozov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-07 19:42 ` Anatol Pomozov
2014-11-07 19:42 ` Anatol Pomozov
2014-11-10 9:53 ` Thierry Reding [this message]
2014-11-10 9:53 ` Thierry Reding
2014-11-10 19:26 ` Anatol Pomozov
[not found] ` <CAOMFOmXpAm5iKCLFyorTW+n9YmgZMmrDGGe736tJX8C6BYQv-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-13 22:46 ` Thomas Gleixner
2014-11-13 22:46 ` Thomas Gleixner
2014-11-13 23:21 ` John Stultz
2014-11-13 23:21 ` John Stultz
[not found] ` <CALAqxLXYVLXZafNH_ag3WDFHkhMe5t23zLbvg7Sq+4_rTfy+Kw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-14 0:26 ` Thomas Gleixner
2014-11-14 0:26 ` Thomas Gleixner
2015-01-09 9:43 ` Thierry Reding
2015-01-09 19:18 ` John Stultz
2015-01-09 19:18 ` John Stultz
2014-11-14 22:03 ` Anatol Pomozov
2014-11-14 22:03 ` Anatol Pomozov
[not found] ` <CAOMFOmVziftM=pWGG-L9J-E6AHYAK7k9bmBcpS1adPboLciX9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-15 0:18 ` Thomas Gleixner
2014-11-15 0:18 ` Thomas Gleixner
2014-11-15 0:51 ` Anatol Pomozov
2014-11-15 0:51 ` Anatol Pomozov
[not found] ` <CAOMFOmV5=tes6Ak1eUKb2qircp8ba6jt6v-bg66Kp_-jYk9m2w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-15 1:09 ` Thomas Gleixner
2014-11-15 1:09 ` Thomas Gleixner
2014-11-15 1:38 ` Thomas Gleixner
2014-11-15 1:38 ` Thomas Gleixner
2015-01-09 9:49 ` Thierry Reding
2015-01-09 9:49 ` Thierry Reding
2015-01-09 13:59 ` Mark Rutland
2015-01-09 13:59 ` Mark Rutland
2015-01-09 14:09 ` Thierry Reding
[not found] ` <20150109140902.GA7526-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>
2015-01-09 19:48 ` Paul Walmsley
2015-01-09 19:48 ` Paul Walmsley
2015-01-09 13:30 ` Daniel Lezcano
2014-11-15 1:07 ` Stephen Warren
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-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=anatol.pomozov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.