[U-Boot] [PATCH 07/14] ARM: AM43xx: Select clk source for Timer2

[Lokesh Vutla <lokeshvutla@ti.com>]

Hi Vaibhav,
On Friday 08 November 2013 02:31 AM, Vaibhav Bedia wrote:
> Hi Lokesh,
> 
> On Thu, Nov 7, 2013 at 8:43 AM, Lokesh Vutla <lokeshvutla@ti.com> wrote:
>> Hi Vaibhav,
>> On Wednesday 06 November 2013 06:10 PM, Vaibhav Bedia wrote:
>>> On Mon, Nov 4, 2013 at 11:20 PM, Lokesh Vutla <lokeshvutla@ti.com> wrote:
>>>> Selecting the Master osc clk as Timer2 clock source.
>>>
>>> I obviously missed the first round of patches for AM43xx here. Why is
>>> timer2 being used here? Don't we use the synctimer and timer1 in the kernel?
>> In u-boot there is already code present to handle timer2 in
>> arch/arm/cpu/armv7/omap-common/timer.c(Registers offsets are different for timer1 and timer2) . Trying to reuse the same here.
>> This is how it is done in am335x also.
>> Correct me if I am wrong.
> 
> On AM335x that timer is used in U-Boot in the delay loop
> and later gets used in the kernel as a system timer. On
> AM437x it might be a good idea to use synctimer since it
> has some stabilization period requirements and that's
> going to affect the kernel boot eventually.
OK, Correct me if I am wrong.
On AM437X also this timer is used in U-Boot in delay loop only.
Is there any documentation or any requirement saying that the synctimer needs
some stabilization period? (AFAIK and discussed with Sekhar and Afzal, there is no such requirement.)
If there is any such requirement for stabilization, then I should not use such timer in delay loop(So use time2 :) ).
Should just enable the timer and leave it for stabilization.
(There was a special case for RTC clock stabilization and was agreed to enable RTC in U-Boot)
 Let me know if I am not clear..:)

Thanks and regards,
Lokesh

> 
> Regards,
> Vaibhav
>