From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Anatol Pomozov <anatol.pomozov@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Russell King <linux@arm.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Mark Rutland <mark.rutland@arm.com>,
John Stultz <john.stultz@linaro.org>
Subject: Re: [PATCH] timekeeping: Move persistent clock registration code from ARM to kernel
Date: Fri, 09 Jan 2015 14:30:14 +0100 [thread overview]
Message-ID: <54AFD7E6.5040607@linaro.org> (raw)
In-Reply-To: <CAOMFOmV5=tes6Ak1eUKb2qircp8ba6jt6v-bg66Kp_-jYk9m2w@mail.gmail.com>
On 11/15/2014 01:51 AM, Anatol Pomozov wrote:
> Hi
>
> On Fri, Nov 14, 2014 at 4:18 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
>> On Fri, 14 Nov 2014, Anatol Pomozov wrote:
>>> On Thu, Nov 13, 2014 at 2:46 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
>>>> On Mon, 10 Nov 2014, Anatol Pomozov wrote:
>>>>> On Mon, Nov 10, 2014 at 1:53 AM, Thierry Reding
>>>>> <thierry.reding@gmail.com> 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.
>>>>
>>>> That's why you should test/compile your stuff on latest greatest and
>>>> not on a year old conglomorate of unknown provenance. :)
>>>
>>> Unfortunately it is not possible to test this patch with upstream.
>>> There is no ARM64 bit support for Tegra yet. I am trying to
>>> cleanup/upstream my ChromeOS patches and this clock patch in
>>> particular makes one small step towards this goal. Also Thierry
>>> mentioned that he works on full ARM64 Tegra support and it is really
>>> exciting!
>>
>> Everything is exciting, but it does not change the fact, that this
>> patch cannot work on current upstream.
>
> Could you please be more specific what exactly does not work? Are you
> talking about delay timer? But my patch does not touch any delay timer
> code. I can compile tegra_timer for ARM. And this code is not usable
> on arm64 anyway because whole Tegra is not ported yet. Somebody should
> make additional changes to upstream tegra20_timer.c code. I might try
> to do it later when Tegra will be ported.
>
>>> So what I suppose to do with my patch? If it does not work could
>>> anyone provide patch that removes ARM arch dependency from
>>> tegra20_timer.c?
>>
>> Huch? You want other people to solve your problems?
>
> This is not the point. I provided patch that fixes the issue. Other
> people said that they have ideas how to do it different (and better)
> way. So I am asking to share these ideas represented as a patch.
I think your issue is solved [1] ... for the moment.
Thanks
-- Daniel
[1] https://lkml.org/lkml/2015/1/9/264
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2015-01-09 13:30 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
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 [this message]
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=54AFD7E6.5040607@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=anatol.pomozov@gmail.com \
--cc=john.stultz@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=thierry.reding@gmail.com \
--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 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.