From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lokesh Vutla <lokeshvutla@ti.com>
Date: Thu, 7 Nov 2013 19:13:32 +0530
Subject: [U-Boot] [PATCH 07/14] ARM: AM43xx: Select clk source for Timer2
In-Reply-To: <CANacCWy2DtQhSoeF2VYuOBW-vV7RuHyRd2YMyRGeyZA85bf9=g@mail.gmail.com>
References: <1383625260-22294-1-git-send-email-lokeshvutla@ti.com>
	<1383625260-22294-8-git-send-email-lokeshvutla@ti.com>
	<CANacCWy2DtQhSoeF2VYuOBW-vV7RuHyRd2YMyRGeyZA85bf9=g@mail.gmail.com>
Message-ID: <527B9904.9020100@ti.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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.

Thanks and regards,
Lokesh
> 
> Regards,
> Vaibhav
>