From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Sricharan R <r.sricharan@ti.com>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
nm@ti.com, Rajendra Nayak <rnayak@ti.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH V5] ARM: OMAP5/DRA7: realtime_counter: Configure CNTFRQ register
Date: Fri, 11 Oct 2013 20:37:05 -0400 [thread overview]
Message-ID: <525899B1.7040206@ti.com> (raw)
In-Reply-To: <20131012003433.GJ29913@atomide.com>
On Friday 11 October 2013 08:34 PM, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [131010 10:23]:
>> * Santosh Shilimkar <santosh.shilimkar@ti.com> [131010 06:20]:
>>> On Thursday 10 October 2013 03:43 AM, Sricharan R wrote:
>>>> From: R Sricharan <r.sricharan@ti.com>
>>>>
>>>> The realtime counter called master counter, produces the count
>>>> used by the private timer peripherals in the MPU_CLUSTER. The
>>>> CNTFRQ per cpu register is used to denote the frequency of the counter.
>>>> Currently the frequency value is passed from the
>>>> DT file, but this is not scalable when we have other non-DT guest
>>>> OS. This register must be set to the right value by the
>>>> secure rom code. Setting this register helps in propagating the right
>>>> frequency value across OSes.
>>>>
>>>> More discussions and the reason for adding this in a non-DT
>>>> way can be seen from below.
>>>> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg93832.html
>>>>
>>>> So configuring this secure register for all the cpus here.
>>>>
>>>> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
>>>> Cc: Nishanth Menon <nm@ti.com>
>>>> Cc: Rajendra Nayak <rnayak@ti.com>
>>>> Cc: Marc Zyngier <marc.zyngier@arm.com>
>>>> Cc: Mark Rutland <mark.rutland@arm.com>
>>>> Cc: Tony Lindgren <tony@atomide.com>
>>>> Tested-by: Nishanth Menon <nm@ti.com>
>>>> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>>>> Signed-off-by: Sricharan R <r.sricharan@ti.com>
>>>> ---
>>>> [V5] Removed the use of extern variable in omap-smp.c
>>>> as per suggestion from Santosh Shilimkar <santosh.shilimkar@ti.com>
>>>>
>>> Thanks for the updates Sricharan. Looks fine now.
>>>
>>> Tony, Can you apply this version if you are fine with it.
>>
>> Yes thanks looks good to me now. Applying into omap-for-v3.13/soc.
>
> Grr, had to apply the following fix on top of this for some configs.
>
Looks like Sricharan missed some builds. Sorry for the trouble Tony.
>
> 8< ---------------------------
>
> From: Tony Lindgren <tony@atomide.com>
> Date: Fri, 11 Oct 2013 17:28:04 -0700
> Subject: [PATCH] ARM: OMAP2+: Fix build error for realtime counter init if not enabled
>
> Otherwise we can get an error with some configs:
>
> arch/arm/mach-omap2/timer.c:73: undefined reference to `omap_smc1'
>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
>
Looks fine to me. Thanks
Regards,
Santosh
prev parent reply other threads:[~2013-10-12 0:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 7:43 [PATCH V5] ARM: OMAP5/DRA7: realtime_counter: Configure CNTFRQ register Sricharan R
2013-10-10 13:12 ` Santosh Shilimkar
2013-10-10 17:15 ` Tony Lindgren
2013-10-12 0:34 ` Tony Lindgren
2013-10-12 0:37 ` Santosh Shilimkar [this message]
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=525899B1.7040206@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=r.sricharan@ti.com \
--cc=rnayak@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 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).