From: Sudeep.KarkadaNagesha@arm.com (Sudeep KarkadaNagesha)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/5] ARM/ARM64: arch_timer: add macros for bits in control register
Date: Tue, 27 Aug 2013 16:19:04 +0100 [thread overview]
Message-ID: <521CC368.6050307@arm.com> (raw)
In-Reply-To: <20130827145250.GE27164@darko.cambridge.arm.com>
On 27/08/13 15:52, Catalin Marinas wrote:
> On Tue, Aug 27, 2013 at 12:37:38PM +0100, Sudeep KarkadaNagesha wrote:
>> On 27/08/13 12:21, Catalin Marinas wrote:
>>> On Fri, Aug 23, 2013 at 05:19:05PM +0100, Sudeep KarkadaNagesha wrote:
>>>> From: Sudeep KarkadaNagesha <sudeep.karkadanagesha@arm.com>
>>>>
>>>> Add macros to describe the bitfields in the ARM architected timer
>>>> control register to make code easy to understand.
>>>>
>>>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>>>> Reviewed-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
>>>> Reviewed-by: Will Deacon <will.deacon@arm.com>
>>>> Signed-off-by: Sudeep KarkadaNagesha <sudeep.karkadanagesha@arm.com>
>>>> ---
>>>> arch/arm/include/asm/arch_timer.h | 9 +++++++--
>>>> arch/arm64/include/asm/arch_timer.h | 12 ++++++++----
>>>> include/clocksource/arm_arch_timer.h | 8 ++++++++
>>>> 3 files changed, 23 insertions(+), 6 deletions(-)
>>>>
>>>> diff --git a/arch/arm/include/asm/arch_timer.h b/arch/arm/include/asm/arch_timer.h
>>>> index e406d57..9ef74da 100644
>>>> --- a/arch/arm/include/asm/arch_timer.h
>>>> +++ b/arch/arm/include/asm/arch_timer.h
>>>> @@ -95,8 +95,13 @@ static inline void arch_counter_set_user_access(void)
>>>>
>>>> asm volatile("mrc p15, 0, %0, c14, c1, 0" : "=r" (cntkctl));
>>>>
>>>> - /* disable user access to everything */
>>>> - cntkctl &= ~((3 << 8) | (7 << 0));
>>>> + /* Disable user access to both physical/virtual counters/timers. */
>>>> + /* Also disable virtual event stream */
>>>> + cntkctl &= ~(ARCH_TIMER_USR_PT_ACCESS_EN
>>>> + | ARCH_TIMER_USR_VT_ACCESS_EN
>>>> + | ARCH_TIMER_VIRT_EVT_EN
>>>> + | ARCH_TIMER_USR_VCT_ACCESS_EN
>>>> + | ARCH_TIMER_USR_PCT_ACCESS_EN);
>>>>
>>>> asm volatile("mcr p15, 0, %0, c14, c1, 0" : : "r" (cntkctl));
>>>> }
>>>> diff --git a/arch/arm64/include/asm/arch_timer.h b/arch/arm64/include/asm/arch_timer.h
>>>> index 98abd47..00b09d0 100644
>>>> --- a/arch/arm64/include/asm/arch_timer.h
>>>> +++ b/arch/arm64/include/asm/arch_timer.h
>>>> @@ -101,12 +101,16 @@ static inline void arch_counter_set_user_access(void)
>>>> {
>>>> u32 cntkctl;
>>>>
>>>> - /* Disable user access to the timers and the physical counter. */
>>>> asm volatile("mrs %0, cntkctl_el1" : "=r" (cntkctl));
>>>> - cntkctl &= ~((3 << 8) | (1 << 0));
>>>>
>>>> - /* Enable user access to the virtual counter and frequency. */
>>>> - cntkctl |= (1 << 1);
>>>> + /* Disable user access to the timers and the physical counter. */
>>>> + cntkctl &= ~(ARCH_TIMER_USR_PT_ACCESS_EN
>>>> + | ARCH_TIMER_USR_VT_ACCESS_EN
>>>> + | ARCH_TIMER_USR_PCT_ACCESS_EN);
>>>> +
>>>> + /* Enable user access to the virtual counter. */
>>>> + cntkctl |= ARCH_TIMER_USR_VCT_ACCESS_EN;
>>>> +
>>>> asm volatile("msr cntkctl_el1, %0" : : "r" (cntkctl));
>>>
>>> For consistency with arm, I think we should also disable the event
>>> stream explicitly here.
>>>
>> Yes it's done. In PATCH 3/5, a new function arch_timer_evtstrm_config is
>> added which is always called(PATCH 4/5). It's either enabled or disabled
>> explicitly based on config option for event stream.
>
> OK, just that in this patch arm and arm64 had different settings with
> regards to the event stream.
>
Yes correct but that's how it is currently. This patch is not modifying
anything functional, just adding macros.
> BTW, can we not avoid clearing the event stream via the
> arch_timer_evtstrm_config(false) and always assume the default as
> disabled? Do you ever go back into low power mode with event stream
> disabled and come back with it enabled?
>
Yes that can be done. But since the cold/warm reset involves other
firmware which can modify that bit, IMO it would be better to do it
explicitly as CONFIG_ARM_ARCH_TIMER_EVTSTREAM=n has to ensure its
disabled. Though I don't have a strong opinion on this, the reason for
my inclination towards explicit disable is because of platform firmware.
e.g. on V2P_CA15_A7/TC2 bootmon/secure firmware enables this bit based
on some settings in board.txt
I can remove as it's disabled on reset(ARM ARM says its reset value is
0) but with the assumption that other firmware don't modify that bit.
Regards,
Sudeep
next prev parent reply other threads:[~2013-08-27 15:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 16:19 [PATCH v4 0/5] ARM/ARM64 architected timer updates Sudeep KarkadaNagesha
2013-08-23 16:19 ` [PATCH v4 1/5] ARM/ARM64: arch_timer: add macros for bits in control register Sudeep KarkadaNagesha
2013-08-27 11:21 ` Catalin Marinas
2013-08-27 11:37 ` Sudeep KarkadaNagesha
2013-08-27 14:52 ` Catalin Marinas
2013-08-27 15:19 ` Sudeep KarkadaNagesha [this message]
2013-08-27 16:53 ` Catalin Marinas
2013-08-27 17:16 ` Sudeep KarkadaNagesha
2013-08-23 16:19 ` [PATCH v4 2/5] ARM: arch_timer: add support to configure and enable event stream Sudeep KarkadaNagesha
2013-08-23 16:19 ` [PATCH v4 3/5] ARM64: " Sudeep KarkadaNagesha
2013-08-27 11:19 ` Catalin Marinas
2013-08-27 11:31 ` Sudeep KarkadaNagesha
2013-08-23 16:19 ` [PATCH v4 4/5] drivers: clocksource: add support for ARM architected timer " Sudeep KarkadaNagesha
2013-08-23 16:19 ` [PATCH v4 5/5] drivers: clocksource: add CPU PM notifier for ARM architected timer Sudeep KarkadaNagesha
2013-08-27 11:22 ` [PATCH v4 0/5] ARM/ARM64 architected timer updates Catalin Marinas
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=521CC368.6050307@arm.com \
--to=sudeep.karkadanagesha@arm.com \
--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).