From: Benoit Cousson <b-cousson@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.orig, tony@atomide.com
Subject: Re: [PATCH 2/2] ARM: OMAP5: Enable arch timer support
Date: Mon, 10 Sep 2012 14:47:33 +0200 [thread overview]
Message-ID: <504DE165.4000208@ti.com> (raw)
In-Reply-To: <1344856045-15134-3-git-send-email-santosh.shilimkar@ti.com>
Hi Santosh,
On 08/13/2012 01:07 PM, Santosh Shilimkar wrote:
> Enable Cortex A15 generic timer support for OMAP5 based SOCs.
> The CPU local timers run on the free running real time counter clock.
>
> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> ---
> arch/arm/boot/dts/omap5.dtsi | 6 ++++++
> arch/arm/mach-omap2/Kconfig | 1 +
> arch/arm/mach-omap2/timer.c | 7 +++++++
> 3 files changed, 14 insertions(+)
>
> diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
> index 57e5270..9686056 100644
> --- a/arch/arm/boot/dts/omap5.dtsi
> +++ b/arch/arm/boot/dts/omap5.dtsi
> @@ -73,6 +73,12 @@
> <0x48212000 0x1000>;
> };
>
> + arch-timer {
arch-timer is the ARM specific name, so I guess here it should be named
with the generic timer name.
> + compatible = "arm,armv7-timer";
> + interrupts = <1 14 0x304>;
Could you add some comment, because these hexa value are a little bit
hard to understand.
> + clock-frequency = <6140000>;
> + };
> +
That node does not even have a base address?
If this is located inside the MPU, it should not be in the OCP node.
Silly question: Don't we have one arch-timer per CPU?
Regards,
Benoit
> gpio1: gpio@4ae10000 {
> compatible = "ti,omap4-gpio";
> ti,hwmods = "gpio1";
> diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
> index 2120f90..53fb77c 100644
> --- a/arch/arm/mach-omap2/Kconfig
> +++ b/arch/arm/mach-omap2/Kconfig
> @@ -73,6 +73,7 @@ config SOC_OMAP5
> select ARM_GIC
> select HAVE_SMP
> select SOC_HAS_REALTIME_COUNTER
> + select ARM_ARCH_TIMER
>
> comment "OMAP Core Type"
> depends on ARCH_OMAP2
> diff --git a/arch/arm/mach-omap2/timer.c b/arch/arm/mach-omap2/timer.c
> index 9b17e6c..f74dbb2 100644
> --- a/arch/arm/mach-omap2/timer.c
> +++ b/arch/arm/mach-omap2/timer.c
> @@ -41,6 +41,7 @@
> #include <plat/dmtimer.h>
> #include <asm/smp_twd.h>
> #include <asm/sched_clock.h>
> +#include <asm/arch_timer.h>
> #include "common.h"
> #include <plat/omap_hwmod.h>
> #include <plat/omap_device.h>
> @@ -480,9 +481,15 @@ OMAP_SYS_TIMER(4)
> #ifdef CONFIG_SOC_OMAP5
> static void __init omap5_timer_init(void)
> {
> + int err;
> +
> omap2_gp_clockevent_init(1, OMAP4_CLKEV_SOURCE);
> omap2_clocksource_init(2, OMAP4_MPU_SOURCE);
> realtime_counter_init();
> +
> + err = arch_timer_of_register();
> + if (err)
> + pr_err("%s: arch_timer_register failed %d\n", __func__, err);
> }
> OMAP_SYS_TIMER(5)
> #endif
>
next prev parent reply other threads:[~2012-09-10 12:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 11:07 [PATCH 0/2] ARM: OMAP5: Enable local timer support Santosh Shilimkar
2012-08-13 11:07 ` [PATCH 1/2] ARM: OMAP: Add initialisation for the real-time counter Santosh Shilimkar
2012-08-13 17:35 ` Vaibhav Hiremath
2012-08-14 6:16 ` Shilimkar, Santosh
2012-08-14 6:22 ` Hiremath, Vaibhav
2012-08-17 8:47 ` Shilimkar, Santosh
2012-08-13 11:07 ` [PATCH 2/2] ARM: OMAP5: Enable arch timer support Santosh Shilimkar
2012-09-10 11:45 ` Shilimkar, Santosh
2012-09-10 12:47 ` Benoit Cousson [this message]
2012-09-10 13:01 ` Shilimkar, Santosh
2012-09-10 13:14 ` Benoit Cousson
2012-09-10 13:39 ` Shilimkar, Santosh
2012-09-11 9:29 ` Shilimkar, Santosh
2012-09-13 8:56 ` Benoit Cousson
2012-09-13 9:00 ` Shilimkar, Santosh
2012-09-13 9:27 ` Benoit Cousson
2012-09-13 10:00 ` Shilimkar, Santosh
2012-09-13 10:05 ` Shilimkar, Santosh
2012-09-17 21:38 ` Tony Lindgren
2012-09-17 21:39 ` Tony Lindgren
2012-09-18 6:06 ` Shilimkar, Santosh
2012-09-18 17:53 ` Tony Lindgren
2012-09-19 7:57 ` Shilimkar, Santosh
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=504DE165.4000208@ti.com \
--to=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.orig \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.