On Mon, Sep 10, 2012 at 6:17 PM, Benoit Cousson <b-cous...@ti.com> wrote:
>
> 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.shilim...@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.
>
is "local_timer" name fine then?
> > + compatible = "arm,armv7-timer";
> > + interrupts = <1 14 0x304>;
>
> Could you add some comment, because these hexa value are a little bit
> hard to understand.
>
OK. Will add some comments.
> > + 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.
>
Its inside MPU and Cp15 control based. No OCP node.
> Silly question: Don't we have one arch-timer per CPU?
>
It is per CPU just like A9 TWD
Regards
santosh
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
