From: sboyd@codeaurora.org (Stephen Boyd)
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 17:56:27 -0700 [thread overview]
Message-ID: <53FE7E3B.1010500@codeaurora.org> (raw)
In-Reply-To: <CAOesGMhTivDzJFuxONggcJ6N5UvZopKa=+tv9PoPX593cpnm0A@mail.gmail.com>
On 08/27/14 15:33, Olof Johansson wrote:
> On Wed, Aug 27, 2014 at 3:26 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>
>> Is there any reason why the virtual counter can't be read? Maybe we're
>> the hyp and we need to make sure we don't use the virtual timer so that
>> the guest can use it, but that doesn't have any effect on the usage of
>> the virtual counter for the clocksource.
> There are several cases where virtual is unusable -- in particular it
> might not have been configured properly (i.e. the phys/virt offset is
> at a bad value).
>
Any specifics? It would be nice to say so in the commit text so that
others using such devices know they need this patch. I'm guessing the
firmware can't be fixed?
In this particular case is there actually a virtual interrupt but we've
explicitly removed it from the DT so that the driver can be forced into
using the physical counter? Or are we getting saved by the hyp check?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-08-28 0:56 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
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 [this message]
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=53FE7E3B.1010500@codeaurora.org \
--to=sboyd@codeaurora.org \
--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).