linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource: arch_timer: Fix code to use physical timers when requested
Date: Wed, 27 Aug 2014 14:19:21 -0700	[thread overview]
Message-ID: <CAOesGMjK65Rc-K0fyFUUJLw6huLT82E-nqJwZO4PqhgopF96Ow@mail.gmail.com> (raw)
In-Reply-To: <1409173419-13076-1-git-send-email-sonnyrao@chromium.org>

On Wed, Aug 27, 2014 at 2:03 PM, Sonny Rao <sonnyrao@chromium.org> wrote:
> This is a bug fix for using physical arch timers when
> the arch_timer_use_virtual boolean is false.  It restores the
> arch_counter_get_cntpct() function after removal in
>
> 0d651e4e "clocksource: arch_timer: use virtual counters"
>
> and completes the implementation of memory mapped access for physical
> timers, so if a system is trying to use physical timers, it will
> function properly.
>
> Signed-off-by: Sonny Rao <sonnyrao@chromium.org>

Acked-by: Olof Johansson <olof@lixom.net>

This should have a:

Fixes: 0d651e4e65e9 ("clocksource: arch_timer: use virtual counters")

tag too, and possibly cc stable?


-Olof

  reply	other threads:[~2014-08-27 21:19 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 21:03 [PATCH] clocksource: arch_timer: Fix code to use physical timers when requested Sonny Rao
2014-08-27 21:19 ` Olof Johansson [this message]
2014-08-27 21:27   ` Sonny Rao
2014-08-27 22:26     ` Stephen Boyd
2014-08-27 22:33       ` Olof Johansson
2014-08-28  0:56         ` Stephen Boyd
2014-08-28  2:58           ` Olof Johansson
2014-08-28  3:33             ` Doug Anderson
2014-08-28  9:35               ` Mark Rutland
2014-08-28 17:09                 ` Christopher Covington
2014-08-28 18:04                   ` Mark Rutland
2014-08-29  0:10                 ` Sonny Rao
2014-08-29 10:04                   ` Mark Rutland
2014-09-04 17:01                     ` Sonny Rao
2014-09-04 17:47                       ` Mark Rutland
2014-09-04 17:48                       ` Lorenzo Pieralisi
2014-09-05 22:11                 ` Doug Anderson
2014-09-08 13:54                   ` Catalin Marinas
2014-09-10 17:17                     ` Doug Anderson
2014-09-10 17:34                       ` Will Deacon
2014-09-10 18:09                         ` Doug Anderson
2014-09-10 18:46                           ` Will Deacon
2014-09-10 19:50                             ` Doug Anderson
2014-09-11  9:57                               ` Will Deacon
2014-09-11 15:54                                 ` Doug Anderson
2014-09-10 14:58                   ` Christopher Covington
2014-09-10 15:47                     ` Catalin Marinas
2014-09-10 15:55                     ` Mark Rutland
2014-09-10 16:39                       ` Olof Johansson
2014-09-10 17:19                       ` Doug Anderson
2014-08-28  9:23 ` Marc Zyngier
2014-09-10 17:27 ` Mark Rutland
2014-09-10 17:52   ` Doug Anderson
2014-09-10 18:05     ` Sonny Rao
2014-09-10 18:35     ` Doug Anderson

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=CAOesGMjK65Rc-K0fyFUUJLw6huLT82E-nqJwZO4PqhgopF96Ow@mail.gmail.com \
    --to=olof@lixom.net \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).