Hi
On Fri, 9 Jan 2015, Thierry Reding wrote:
> On Fri, Jan 09, 2015 at 01:59:07PM +, Mark Rutland wrote:
> > On Fri, Jan 09, 2015 at 09:49:14AM +, Thierry Reding wrote:
> >
> > > As I understand it the architected timer will be turned off along with
> > > the rest of the CPU complex on Te
On Fri, Jan 9, 2015 at 1:43 AM, Thierry Reding wrote:
> On Thu, Nov 13, 2014 at 03:21:22PM -0800, John Stultz wrote:
>> On Thu, Nov 13, 2014 at 2:46 PM, Thomas Gleixner wrote:
>> > On Mon, 10 Nov 2014, Anatol Pomozov wrote:
>> >> On Mon, Nov 10, 2014 at 1:53 AM, Thierry Reding
>> >> wrote:
>> >>
On Fri, Jan 09, 2015 at 01:59:07PM +, Mark Rutland wrote:
> On Fri, Jan 09, 2015 at 09:49:14AM +, Thierry Reding wrote:
> > On Sat, Nov 15, 2014 at 02:38:00AM +0100, Thomas Gleixner wrote:
> > > On Sat, 15 Nov 2014, Thomas Gleixner wrote:
> > > > On Fri, 14 Nov 2014, Anatol Pomozov wrote:
>
On Fri, Jan 09, 2015 at 09:49:14AM +, Thierry Reding wrote:
> On Sat, Nov 15, 2014 at 02:38:00AM +0100, Thomas Gleixner wrote:
> > On Sat, 15 Nov 2014, Thomas Gleixner wrote:
> > > On Fri, 14 Nov 2014, Anatol Pomozov wrote:
> > > > On Fri, Nov 14, 2014 at 4:18 PM, Thomas Gleixner
> > > > wrot
On 11/15/2014 01:51 AM, Anatol Pomozov wrote:
Hi
On Fri, Nov 14, 2014 at 4:18 PM, Thomas Gleixner wrote:
On Fri, 14 Nov 2014, Anatol Pomozov wrote:
On Thu, Nov 13, 2014 at 2:46 PM, Thomas Gleixner wrote:
On Mon, 10 Nov 2014, Anatol Pomozov wrote:
On Mon, Nov 10, 2014 at 1:53 AM, Thierry Re
On Sat, Nov 15, 2014 at 02:38:00AM +0100, Thomas Gleixner wrote:
> On Sat, 15 Nov 2014, Thomas Gleixner wrote:
> > On Fri, 14 Nov 2014, Anatol Pomozov wrote:
> > > On Fri, Nov 14, 2014 at 4:18 PM, Thomas Gleixner
> > > wrote:
> > > >> So what I suppose to do with my patch? If it does not work cou
On Thu, Nov 13, 2014 at 03:21:22PM -0800, John Stultz wrote:
> On Thu, Nov 13, 2014 at 2:46 PM, Thomas Gleixner wrote:
> > On Mon, 10 Nov 2014, Anatol Pomozov wrote:
> >> On Mon, Nov 10, 2014 at 1:53 AM, Thierry Reding
> >> wrote:
> >> > On Fri, Nov 07, 2014 at 11:34:15AM -0800, Anatol Pomozov wr
On Sat, 15 Nov 2014, Thomas Gleixner wrote:
> On Fri, 14 Nov 2014, Anatol Pomozov wrote:
> > On Fri, Nov 14, 2014 at 4:18 PM, Thomas Gleixner wrote:
> > >> So what I suppose to do with my patch? If it does not work could
> > >> anyone provide patch that removes ARM arch dependency from
> > >> tegr
On Fri, 14 Nov 2014, Anatol Pomozov wrote:
> On Fri, Nov 14, 2014 at 4:18 PM, Thomas Gleixner wrote:
> >> 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 so
On 11/14/2014 03:03 PM, Anatol Pomozov wrote:
Hi
On Thu, Nov 13, 2014 at 2:46 PM, Thomas Gleixner wrote:
On Mon, 10 Nov 2014, Anatol Pomozov wrote:
On Mon, Nov 10, 2014 at 1:53 AM, Thierry Reding
wrote:
On Fri, Nov 07, 2014 at 11:34:15AM -0800, Anatol Pomozov wrote:
ARM timekeeping functio
Hi
On Fri, Nov 14, 2014 at 4:18 PM, Thomas Gleixner wrote:
> On Fri, 14 Nov 2014, Anatol Pomozov wrote:
>> On Thu, Nov 13, 2014 at 2:46 PM, Thomas Gleixner wrote:
>> > On Mon, 10 Nov 2014, Anatol Pomozov wrote:
>> >> On Mon, Nov 10, 2014 at 1:53 AM, Thierry Reding
>> >> wrote:
>> >> > On Fri, N
On Fri, 14 Nov 2014, Anatol Pomozov wrote:
> On Thu, Nov 13, 2014 at 2:46 PM, Thomas Gleixner wrote:
> > On Mon, 10 Nov 2014, Anatol Pomozov wrote:
> >> On Mon, Nov 10, 2014 at 1:53 AM, Thierry Reding
> >> wrote:
> >> > On Fri, Nov 07, 2014 at 11:34:15AM -0800, Anatol Pomozov wrote:
> >> >> ARM t
Hi
On Thu, Nov 13, 2014 at 2:46 PM, Thomas Gleixner wrote:
> On Mon, 10 Nov 2014, Anatol Pomozov wrote:
>> On Mon, Nov 10, 2014 at 1:53 AM, Thierry Reding
>> wrote:
>> > On Fri, Nov 07, 2014 at 11:34:15AM -0800, Anatol Pomozov wrote:
>> >> ARM timekeeping functionality allows to register persist
On Thu, 13 Nov 2014, John Stultz wrote:
> On Thu, Nov 13, 2014 at 2:46 PM, Thomas Gleixner wrote:
> > Aside of that I really wonder why we need that persistent_clock stuff
> > at all. We already have mechanisms to register persistent clocks AKA
> > RTCs after the early boot process and update the
On Thu, Nov 13, 2014 at 2:46 PM, Thomas Gleixner wrote:
> On Mon, 10 Nov 2014, Anatol Pomozov wrote:
>> On Mon, Nov 10, 2014 at 1:53 AM, Thierry Reding
>> wrote:
>> > On Fri, Nov 07, 2014 at 11:34:15AM -0800, Anatol Pomozov wrote:
>> >> ARM timekeeping functionality allows to register persistent/
On Mon, 10 Nov 2014, Anatol Pomozov wrote:
> On Mon, Nov 10, 2014 at 1:53 AM, Thierry Reding
> 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-independen
Hi
On Mon, Nov 10, 2014 at 1:53 AM, Thierry Reding
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.
>>
>
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 compa
Hi
This patch opens possibility for further timekeeping cleanup:
read_persistent_clock() is defined as a weak and expected that
architecture implement it. The users of this function need to check
return value. If it is equal zero then persistent clock is not
provided. It looks hacky. It makes code
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
20 matches
Mail list logo
