From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: arch timer: implement read_current_timer and get_cycles
Date: Mon, 25 Jun 2012 14:39:04 -0700 [thread overview]
Message-ID: <4FE8DA78.5070804@codeaurora.org> (raw)
In-Reply-To: <1340377774-17173-2-git-send-email-will.deacon@arm.com>
On 06/22/12 08:09, Will Deacon wrote:
> This patch implements read_current_timer using the architected timers
> when they are selected via CONFIG_ARM_ARCH_TIMER. If they are detected
> not to be usable at runtime, we return -ENXIO to the caller.
>
> Furthermore, if read_current_timer is exported then we can implement
> get_cycles in terms of it for use as both an entropy source and for
> implementing __udelay and friends.
Neat.
> diff --git a/arch/arm/include/asm/timex.h b/arch/arm/include/asm/timex.h
> index 3be8de3..ce11944 100644
> --- a/arch/arm/include/asm/timex.h
> +++ b/arch/arm/include/asm/timex.h
> @@ -12,13 +12,15 @@
> #ifndef _ASMARM_TIMEX_H
> #define _ASMARM_TIMEX_H
>
> +#include <asm/arch_timer.h>
This seems to cause compilation failures if you aren't building with
architected timers enabled.
In file included from arch/arm/include/asm/timex.h:15,
from include/linux/timex.h:174,
from include/linux/sched.h:57,
from arch/arm/kernel/asm-offsets.c:13:
arch/arm/include/asm/arch_timer.h: In function 'arch_timer_of_register':
arch/arm/include/asm/arch_timer.h:11: error: 'ENXIO' undeclared (first use in this function)
> #include <mach/timex.h>
>
> typedef unsigned long cycles_t;
>
> -static inline cycles_t get_cycles (void)
> -{
> - return 0;
> -}
> +#ifdef ARCH_HAS_READ_CURRENT_TIMER
> +#define get_cycles() ({ cycles_t c; read_current_timer(&c) ? 0 : c; })
> +#else
> +#define get_cycles() (0)
> +#endif
>
> #endif
> diff --git a/arch/arm/kernel/arch_timer.c b/arch/arm/kernel/arch_timer.c
> index dd58035..dbbeec4 100644
> --- a/arch/arm/kernel/arch_timer.c
> +++ b/arch/arm/kernel/arch_timer.c
> @@ -223,6 +223,14 @@ static cycle_t arch_counter_read(struct clocksource *cs)
> return arch_counter_get_cntpct();
> }
>
> +int read_current_timer(unsigned long *timer_val)
> +{
> + if (!arch_timer_rate)
> + return -ENXIO;
Shouldn't this be returning 0? Otherwise get_cycles() up there will
evaluate to -ENXIO?
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2012-06-25 21:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 15:09 [PATCH 0/2] Use architected timers for delay loop Will Deacon
2012-06-22 15:09 ` [PATCH 1/2] ARM: arch timer: implement read_current_timer and get_cycles Will Deacon
2012-06-25 21:39 ` Stephen Boyd [this message]
2012-06-26 10:37 ` Will Deacon
2012-06-26 17:44 ` Stephen Boyd
2012-06-22 15:09 ` [PATCH 2/2] ARM: delay: allow timer-based delay implementation to be selected Will Deacon
2012-06-25 21:39 ` Stephen Boyd
2012-06-26 10:49 ` Will Deacon
2012-06-26 15:54 ` Will Deacon
2012-06-26 16:00 ` Rob Herring
2012-06-26 16:28 ` Will Deacon
2012-06-27 2:07 ` Stephen Boyd
2012-06-27 9:41 ` Will Deacon
2012-06-22 22:26 ` [PATCH 0/2] Use architected timers for delay loop Russell King - ARM Linux
2012-06-25 10:03 ` Will Deacon
2012-06-25 21:38 ` Stephen Boyd
2012-06-26 10:35 ` Will Deacon
2012-06-26 17:42 ` Stephen Boyd
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=4FE8DA78.5070804@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).