On Tue, Mar 13, 2012 at 17:07:16, Ming Lei wrote:
> Hi,
>
> On Tue, Jan 24, 2012 at 7:38 AM, Kevin Hilman wrote:
> > Vaibhav Hiremath writes:
> >
> >> OMAP device has 32k-sync timer which is currently used as a
> >> clocksource in the kernel (omap2plus_defconfig).
> >> The current implementation
On Mon, Mar 19, 2012 at 7:11 PM, Hiremath, Vaibhav wrote:
>
> I think you made very good point here. With the above patch, we are almost
> missing the capability of registering dmtimer as a clocksource for OMAP.
> It will always use 32k-counter, and never fall back to dmtimer.
>
> Then the only o
On Monday 19 March 2012 05:14 PM, Ming Lei wrote:
> On Mon, Mar 19, 2012 at 7:11 PM, Hiremath, Vaibhav wrote:
>>
>> I think you made very good point here. With the above patch, we are almost
>> missing the capability of registering dmtimer as a clocksource for OMAP.
>> It will always use 32k-coun
On Mon, Mar 19, 2012 at 17:14:30, Ming Lei wrote:
> On Mon, Mar 19, 2012 at 7:11 PM, Hiremath, Vaibhav wrote:
> >
> > I think you made very good point here. With the above patch, we are almost
> > missing the capability of registering dmtimer as a clocksource for OMAP.
> > It will always use 32k-
On Mon, Mar 19, 2012 at 17:45:32, Shilimkar, Santosh wrote:
> On Monday 19 March 2012 05:14 PM, Ming Lei wrote:
> > On Mon, Mar 19, 2012 at 7:11 PM, Hiremath, Vaibhav wrote:
> >>
> >> I think you made very good point here. With the above patch, we are almost
> >> missing the capability of registe
On Wed, Mar 21, 2012 at 5:12 PM, Hiremath, Vaibhav wrote:
> On Mon, Mar 19, 2012 at 17:45:32, Shilimkar, Santosh wrote:
>> On Monday 19 March 2012 05:14 PM, Ming Lei wrote:
>> > On Mon, Mar 19, 2012 at 7:11 PM, Hiremath, Vaibhav wrote:
>> >>
>> >> I think you made very good point here. With the a
On Wed, Mar 21, 2012 at 7:29 PM, Hiremath, Vaibhav wrote:
> On Mon, Mar 19, 2012 at 17:14:30, Ming Lei wrote:
>> On Mon, Mar 19, 2012 at 7:11 PM, Hiremath, Vaibhav wrote:
>> >
>> > I think you made very good point here. With the above patch, we are almost
>> > missing the capability of registeri
On Wed, Mar 21, 2012 at 19:30:01, Shilimkar, Santosh wrote:
> On Wed, Mar 21, 2012 at 5:12 PM, Hiremath, Vaibhav wrote:
> > On Mon, Mar 19, 2012 at 17:45:32, Shilimkar, Santosh wrote:
> >> On Monday 19 March 2012 05:14 PM, Ming Lei wrote:
> >> > On Mon, Mar 19, 2012 at 7:11 PM, Hiremath, Vaibhav
On Wed, Mar 28, 2012 at 7:46 PM, Hiremath, Vaibhav wrote:
> On Wed, Mar 21, 2012 at 19:30:01, Shilimkar, Santosh wrote:
>> On Wed, Mar 21, 2012 at 5:12 PM, Hiremath, Vaibhav wrote:
>> > On Mon, Mar 19, 2012 at 17:45:32, Shilimkar, Santosh wrote:
>> >> On Monday 19 March 2012 05:14 PM, Ming Lei wr
On Wed, Mar 28, 2012 at 19:50:02, Shilimkar, Santosh wrote:
> On Wed, Mar 28, 2012 at 7:46 PM, Hiremath, Vaibhav wrote:
> > On Wed, Mar 21, 2012 at 19:30:01, Shilimkar, Santosh wrote:
> >> On Wed, Mar 21, 2012 at 5:12 PM, Hiremath, Vaibhav wrote:
> >> > On Mon, Mar 19, 2012 at 17:45:32, Shilimkar
On Wed, Mar 28, 2012 at 8:07 PM, Hiremath, Vaibhav wrote:
> On Wed, Mar 28, 2012 at 19:50:02, Shilimkar, Santosh wrote:
>> On Wed, Mar 28, 2012 at 7:46 PM, Hiremath, Vaibhav wrote:
>> > On Wed, Mar 21, 2012 at 19:30:01, Shilimkar, Santosh wrote:
>> >> On Wed, Mar 21, 2012 at 5:12 PM, Hiremath, Va
On Wed, Mar 28, 2012 at 20:19:07, Shilimkar, Santosh wrote:
> On Wed, Mar 28, 2012 at 8:07 PM, Hiremath, Vaibhav wrote:
> > On Wed, Mar 28, 2012 at 19:50:02, Shilimkar, Santosh wrote:
> >> On Wed, Mar 28, 2012 at 7:46 PM, Hiremath, Vaibhav wrote:
> >> > On Wed, Mar 21, 2012 at 19:30:01, Shilimkar
On Fri, Mar 23, 2012 at 13:50:25, Ming Lei wrote:
> On Wed, Mar 21, 2012 at 7:29 PM, Hiremath, Vaibhav wrote:
> > On Mon, Mar 19, 2012 at 17:14:30, Ming Lei wrote:
> >> On Mon, Mar 19, 2012 at 7:11 PM, Hiremath, Vaibhav wrote:
> >> >
> >> > I think you made very good point here. With the above pa
On Fri, Mar 30, 2012 at 12:04 PM, Hiremath, Vaibhav wrote:
> On Wed, Mar 28, 2012 at 20:19:07, Shilimkar, Santosh wrote:
>> On Wed, Mar 28, 2012 at 8:07 PM, Hiremath, Vaibhav wrote:
>> > On Wed, Mar 28, 2012 at 19:50:02, Shilimkar, Santosh wrote:
>> >> On Wed, Mar 28, 2012 at 7:46 PM, Hiremath, V
On Fri, Mar 30, 2012 at 13:11:35, Shilimkar, Santosh wrote:
> On Fri, Mar 30, 2012 at 12:04 PM, Hiremath, Vaibhav wrote:
> > On Wed, Mar 28, 2012 at 20:19:07, Shilimkar, Santosh wrote:
> >> On Wed, Mar 28, 2012 at 8:07 PM, Hiremath, Vaibhav wrote:
> >> > On Wed, Mar 28, 2012 at 19:50:02, Shilimka
On Friday 30 March 2012 02:02 PM, Hiremath, Vaibhav wrote:
> On Fri, Mar 30, 2012 at 13:11:35, Shilimkar, Santosh wrote:
>> On Fri, Mar 30, 2012 at 12:04 PM, Hiremath, Vaibhav wrote:
>>> On Wed, Mar 28, 2012 at 20:19:07, Shilimkar, Santosh wrote:
On Wed, Mar 28, 2012 at 8:07 PM, Hiremath, Vai
On Fri, Mar 30, 2012 at 14:08:20, Shilimkar, Santosh wrote:
> On Friday 30 March 2012 02:02 PM, Hiremath, Vaibhav wrote:
> > On Fri, Mar 30, 2012 at 13:11:35, Shilimkar, Santosh wrote:
> >> On Fri, Mar 30, 2012 at 12:04 PM, Hiremath, Vaibhav
> >> wrote:
> >>> On Wed, Mar 28, 2012 at 20:19:07, Shi
On Fri, Mar 30, 2012 at 2:42 PM, Hiremath, Vaibhav wrote:
> On Fri, Mar 30, 2012 at 14:08:20, Shilimkar, Santosh wrote:
>> On Friday 30 March 2012 02:02 PM, Hiremath, Vaibhav wrote:
>> > On Fri, Mar 30, 2012 at 13:11:35, Shilimkar, Santosh wrote:
[]
>> >
>> > With this patch, will you be abl
On Fri, Mar 30, 2012 at 14:50:02, Shilimkar, Santosh wrote:
> On Fri, Mar 30, 2012 at 2:42 PM, Hiremath, Vaibhav wrote:
> > On Fri, Mar 30, 2012 at 14:08:20, Shilimkar, Santosh wrote:
> >> On Friday 30 March 2012 02:02 PM, Hiremath, Vaibhav wrote:
> >> > On Fri, Mar 30, 2012 at 13:11:35, Shilimkar
On Fri, Mar 30, 2012 at 2:58 PM, Hiremath, Vaibhav wrote:
> On Fri, Mar 30, 2012 at 14:50:02, Shilimkar, Santosh wrote:
>> On Fri, Mar 30, 2012 at 2:42 PM, Hiremath, Vaibhav wrote:
>> > On Fri, Mar 30, 2012 at 14:08:20, Shilimkar, Santosh wrote:
>> >> On Friday 30 March 2012 02:02 PM, Hiremath, V
On Fri, Mar 30, 2012 at 15:12:19, Shilimkar, Santosh wrote:
> On Fri, Mar 30, 2012 at 2:58 PM, Hiremath, Vaibhav wrote:
> > On Fri, Mar 30, 2012 at 14:50:02, Shilimkar, Santosh wrote:
> >> On Fri, Mar 30, 2012 at 2:42 PM, Hiremath, Vaibhav wrote:
> >> > On Fri, Mar 30, 2012 at 14:08:20, Shilimkar
On Friday 30 March 2012 04:59 PM, Hiremath, Vaibhav wrote:
> On Fri, Mar 30, 2012 at 15:12:19, Shilimkar, Santosh wrote:
>> On Fri, Mar 30, 2012 at 2:58 PM, Hiremath, Vaibhav wrote:
>>> On Fri, Mar 30, 2012 at 14:50:02, Shilimkar, Santosh wrote:
On Fri, Mar 30, 2012 at 2:42 PM, Hiremath, Vaib
On Fri, Mar 30, 2012 at 5:20 PM, Shilimkar, Santosh
>
>> After Ming Lie's comment, the point that I came to my mind was,
>> certainly there will be resolution difference between these two clocksources,
>> if gptimer2 is sourced from sys_ck (26Mhz).
>>
> GPTIMER2 with sysclock is not an option. GP
On Sat, Mar 31, 2012 at 7:00 AM, Ming Lei wrote:
> On Fri, Mar 30, 2012 at 5:20 PM, Shilimkar, Santosh
>>
>>> After Ming Lie's comment, the point that I came to my mind was,
>>> certainly there will be resolution difference between these two
>>> clocksources,
>>> if gptimer2 is sourced from sys
On Sat, Mar 31, 2012 at 2:30 PM, Shilimkar, Santosh
> Since you need to recompile the kernel, you can very much tweak the
> clocksource to use GPTIMER with sysl clock. Support for that is still
> in place.
With current kernel, running 'make menuconfig' can do it, but after applying
Hiremath's patc
On Sat, Mar 31, 2012 at 2:09 PM, Ming Lei wrote:
> On Sat, Mar 31, 2012 at 2:30 PM, Shilimkar, Santosh
>> Since you need to recompile the kernel, you can very much tweak the
>> clocksource to use GPTIMER with sysl clock. Support for that is still
>> in place.
>
> With current kernel, running 'make
On Sun, Apr 1, 2012 at 3:10 AM, Shilimkar, Santosh
wrote:
> On Sat, Mar 31, 2012 at 2:09 PM, Ming Lei wrote:
>> On Sat, Mar 31, 2012 at 2:30 PM, Shilimkar, Santosh
>>> Since you need to recompile the kernel, you can very much tweak the
>>> clocksource to use GPTIMER with sysl clock. Support for t
On Sun, Apr 1, 2012 at 7:09 AM, Ming Lei wrote:
> On Sun, Apr 1, 2012 at 3:10 AM, Shilimkar, Santosh
> wrote:
>> On Sat, Mar 31, 2012 at 2:09 PM, Ming Lei wrote:
>>> On Sat, Mar 31, 2012 at 2:30 PM, Shilimkar, Santosh
Since you need to recompile the kernel, you can very much tweak the
"Shilimkar, Santosh" writes:
[...]
> I don't personally like to add features which hardly anybody use and
> fundamentally broken with full kernel.
Let's keep sane defaults, but not make it unreasonable to tweak eaither.
I suggest what has already been mentioned.
Register both timers, but have
On Tue, Apr 3, 2012 at 12:05 AM, Kevin Hilman wrote:
> "Shilimkar, Santosh" writes:
>
> [...]
>
>> I don't personally like to add features which hardly anybody use and
>> fundamentally broken with full kernel.
>
> Let's keep sane defaults, but not make it unreasonable to tweak eaither.
>
Exactly.
On Tue, Apr 03, 2012 at 00:05:38, Hilman, Kevin wrote:
> "Shilimkar, Santosh" writes:
>
> [...]
>
> > I don't personally like to add features which hardly anybody use and
> > fundamentally broken with full kernel.
>
> Let's keep sane defaults, but not make it unreasonable to tweak eaither.
>
>
On Tue, Apr 3, 2012 at 9:05 PM, Hiremath, Vaibhav wrote:
> On Tue, Apr 03, 2012 at 00:05:38, Hilman, Kevin wrote:
>> "Shilimkar, Santosh" writes:
>>
>> [...]
>>
>> > I don't personally like to add features which hardly anybody use and
>> > fundamentally broken with full kernel.
>>
>> Let's keep s
On Wed, Apr 04, 2012 at 14:34:09, Shilimkar, Santosh wrote:
> On Tue, Apr 3, 2012 at 9:05 PM, Hiremath, Vaibhav wrote:
> > On Tue, Apr 03, 2012 at 00:05:38, Hilman, Kevin wrote:
> >> "Shilimkar, Santosh" writes:
> >>
> >> [...]
> >>
> >> > I don't personally like to add features which hardly anyb
On Wed, Apr 04, 2012 at 16:09:51, Hiremath, Vaibhav wrote:
> On Wed, Apr 04, 2012 at 14:34:09, Shilimkar, Santosh wrote:
> > On Tue, Apr 3, 2012 at 9:05 PM, Hiremath, Vaibhav wrote:
> > > On Tue, Apr 03, 2012 at 00:05:38, Hilman, Kevin wrote:
> > >> "Shilimkar, Santosh" writes:
> > >>
> > >> [...
On Thu, Apr 05, 2012 at 09:36:00AM +, Hiremath, Vaibhav wrote:
> There seems to be limitation for ARM architecture, it is restricted by
> sched_clock implementation present in "arch/arm/kernel/sched_clock.c".
> Natively, clocksource framework does support change in rate/frequency for
> register
On Thu, Apr 05, 2012 at 15:22:21, Russell King - ARM Linux wrote:
> On Thu, Apr 05, 2012 at 09:36:00AM +, Hiremath, Vaibhav wrote:
> > There seems to be limitation for ARM architecture, it is restricted by
> > sched_clock implementation present in "arch/arm/kernel/sched_clock.c".
> > Natively,
On Thursday 05 April 2012 04:01 PM, Hiremath, Vaibhav wrote:
> On Thu, Apr 05, 2012 at 15:22:21, Russell King - ARM Linux wrote:
>> On Thu, Apr 05, 2012 at 09:36:00AM +, Hiremath, Vaibhav wrote:
>>> There seems to be limitation for ARM architecture, it is restricted by
>>> sched_clock implement
"Hiremath, Vaibhav" writes:
> On Thu, Apr 05, 2012 at 15:22:21, Russell King - ARM Linux wrote:
>> On Thu, Apr 05, 2012 at 09:36:00AM +, Hiremath, Vaibhav wrote:
>> > There seems to be limitation for ARM architecture, it is restricted by
>> > sched_clock implementation present in "arch/arm/ke
On Fri, Apr 06, 2012 at 03:03:01, Hilman, Kevin wrote:
> "Hiremath, Vaibhav" writes:
>
> > On Thu, Apr 05, 2012 at 15:22:21, Russell King - ARM Linux wrote:
> >> On Thu, Apr 05, 2012 at 09:36:00AM +, Hiremath, Vaibhav wrote:
> >> > There seems to be limitation for ARM architecture, it is rest
* Hiremath, Vaibhav [120405 22:25]:
> On Fri, Apr 06, 2012 at 03:03:01, Hilman, Kevin wrote:
> >
> > What we need is only one-time selection at boot based on presence (or
> > not) of various timers. IOW, we still only ever need to call
> > setup_sched_clock() once based on which HW timers are av
"Hiremath, Vaibhav" writes:
[...]
> I liked Santosh's idea in using command line argument "clocksource=" and
> make decision based on this. I have implemented it and tried it on both
> OMAP3EVM and beaglebone and it works great.
>
> I have introduced something like this in mach-omap2/timer.c,
>
On Fri, Apr 06, 2012 at 23:34:52, Tony Lindgren wrote:
> * Hiremath, Vaibhav [120405 22:25]:
> > On Fri, Apr 06, 2012 at 03:03:01, Hilman, Kevin wrote:
> > >
> > > What we need is only one-time selection at boot based on presence (or
> > > not) of various timers. IOW, we still only ever need to
On Sat, Apr 07, 2012 at 02:48:47, Hilman, Kevin wrote:
> "Hiremath, Vaibhav" writes:
>
> [...]
>
> > I liked Santosh's idea in using command line argument "clocksource=" and
> > make decision based on this. I have implemented it and tried it on both
> > OMAP3EVM and beaglebone and it works grea
Hi Vaibhav,
On 04/09/2012 01:19 AM, Hiremath, Vaibhav wrote:
[...]
Let me summarize it here again,
Currently, the timer code is using config option CONFIG_OMAP_32K_TIMER,
to choose between 32ksync counter and gptimer; it is compile time option.
If user wants to use gptimer for HR ticks, he mu
On Tue, Apr 10, 2012 at 01:48:22, Hunter, Jon wrote:
> Hi Vaibhav,
>
> On 04/09/2012 01:19 AM, Hiremath, Vaibhav wrote:
>
> [...]
>
> > Let me summarize it here again,
> >
> > Currently, the timer code is using config option CONFIG_OMAP_32K_TIMER,
> > to choose between 32ksync counter and gptime
On Mon, Apr 09, 2012 at 03:18:22PM -0500, Jon Hunter wrote:
> True, but we would always want to use the 32k timer if CONFIG_PM is
> specified. So what I am saying is that if a device has a 32ksync timer
> and CONFIG_PM is defined, we always want to use the 32ksync timer and a
> gptimer should
On Tuesday 10 April 2012 02:14 PM, Russell King - ARM Linux wrote:
> On Mon, Apr 09, 2012 at 03:18:22PM -0500, Jon Hunter wrote:
>> True, but we would always want to use the 32k timer if CONFIG_PM is
>> specified. So what I am saying is that if a device has a 32ksync timer
>> and CONFIG_PM is d
On Tue, Apr 10, 2012 at 02:27:36PM +0530, Santosh Shilimkar wrote:
> On Tuesday 10 April 2012 02:14 PM, Russell King - ARM Linux wrote:
> > On Mon, Apr 09, 2012 at 03:18:22PM -0500, Jon Hunter wrote:
> >> True, but we would always want to use the 32k timer if CONFIG_PM is
> >> specified. So what
On Tue, Apr 10, 2012 at 2:59 PM, Russell King - ARM Linux
wrote:
> On Tue, Apr 10, 2012 at 02:27:36PM +0530, Santosh Shilimkar wrote:
>> On Tuesday 10 April 2012 02:14 PM, Russell King - ARM Linux wrote:
>> > On Mon, Apr 09, 2012 at 03:18:22PM -0500, Jon Hunter wrote:
>> >> True, but we would alwa
On 04/10/2012 04:51 AM, Shilimkar, Santosh wrote:
On Tue, Apr 10, 2012 at 2:59 PM, Russell King - ARM Linux
wrote:
On Tue, Apr 10, 2012 at 02:27:36PM +0530, Santosh Shilimkar wrote:
On Tuesday 10 April 2012 02:14 PM, Russell King - ARM Linux wrote:
On Mon, Apr 09, 2012 at 03:18:22PM -0500,
On Tue, Apr 10, 2012 at 5:51 PM, Shilimkar, Santosh
wrote:
> On Tue, Apr 10, 2012 at 2:59 PM, Russell King - ARM Linux
> wrote:
>> On Tue, Apr 10, 2012 at 02:27:36PM +0530, Santosh Shilimkar wrote:
>>> On Tuesday 10 April 2012 02:14 PM, Russell King - ARM Linux wrote:
>>> > On Mon, Apr 09, 2012 a
On Wed, Apr 11, 2012 at 6:30 AM, Ming Lei wrote:
> On Tue, Apr 10, 2012 at 5:51 PM, Shilimkar, Santosh
> wrote:
>> On Tue, Apr 10, 2012 at 2:59 PM, Russell King - ARM Linux
>> wrote:
>>> On Tue, Apr 10, 2012 at 02:27:36PM +0530, Santosh Shilimkar wrote:
On Tuesday 10 April 2012 02:14 PM, Ru
Vaibhav Hiremath writes:
> OMAP device has 32k-sync timer which is currently used as a
> clocksource in the kernel (omap2plus_defconfig).
> The current implementation uses compile time selection between
> gp-timer and 32k-sync timer, which breaks multi-omap build for
> the devices like AM33xx, wh
On Tue, Jan 24, 2012 at 05:08:50, Hilman, Kevin wrote:
> Vaibhav Hiremath writes:
>
> > OMAP device has 32k-sync timer which is currently used as a
> > clocksource in the kernel (omap2plus_defconfig).
> > The current implementation uses compile time selection between
> > gp-timer and 32k-sync tim
"Hiremath, Vaibhav" writes:
> On Tue, Jan 24, 2012 at 05:08:50, Hilman, Kevin wrote:
>> Vaibhav Hiremath writes:
>>
>> > OMAP device has 32k-sync timer which is currently used as a
>> > clocksource in the kernel (omap2plus_defconfig).
>> > The current implementation uses compile time selection
On Tue, Jan 24, 2012 at 23:17:56, Hilman, Kevin wrote:
> "Hiremath, Vaibhav" writes:
>
> > On Tue, Jan 24, 2012 at 05:08:50, Hilman, Kevin wrote:
> >> Vaibhav Hiremath writes:
> >>
> >> > OMAP device has 32k-sync timer which is currently used as a
> >> > clocksource in the kernel (omap2plus_def
Hi,
* Vaibhav Hiremath [120119 06:01]:
> OMAP device has 32k-sync timer which is currently used as a
> clocksource in the kernel (omap2plus_defconfig).
> The current implementation uses compile time selection between
> gp-timer and 32k-sync timer, which breaks multi-omap build for
> the devices l
On Tue, Mar 06, 2012 at 04:25:30, Tony Lindgren wrote:
> Hi,
>
> * Vaibhav Hiremath [120119 06:01]:
> > OMAP device has 32k-sync timer which is currently used as a
> > clocksource in the kernel (omap2plus_defconfig).
> > The current implementation uses compile time selection between
> > gp-timer
On Tue, Mar 06, 2012 at 04:25:30, Tony Lindgren wrote:
> Hi,
>
> * Vaibhav Hiremath [120119 06:01]:
> > OMAP device has 32k-sync timer which is currently used as a
> > clocksource in the kernel (omap2plus_defconfig).
> > The current implementation uses compile time selection between
> > gp-timer
On Fri, Mar 09, 2012 at 05:58:00PM +, Hiremath, Vaibhav wrote:
> On Tue, Mar 06, 2012 at 04:25:30, Tony Lindgren wrote:
> > Hi,
> >
> > * Vaibhav Hiremath [120119 06:01]:
> > > OMAP device has 32k-sync timer which is currently used as a
> > > clocksource in the kernel (omap2plus_defconfig).
>
On Mon, Mar 12, 2012 at 15:09:24, Balbi, Felipe wrote:
> On Fri, Mar 09, 2012 at 05:58:00PM +, Hiremath, Vaibhav wrote:
> > On Tue, Mar 06, 2012 at 04:25:30, Tony Lindgren wrote:
> > > Hi,
> > >
> > > * Vaibhav Hiremath [120119 06:01]:
> > > > OMAP device has 32k-sync timer which is currently
Hi,
On Mon, Mar 12, 2012 at 09:48:20AM +, Hiremath, Vaibhav wrote:
> On Mon, Mar 12, 2012 at 15:09:24, Balbi, Felipe wrote:
> > On Fri, Mar 09, 2012 at 05:58:00PM +, Hiremath, Vaibhav wrote:
> > > On Tue, Mar 06, 2012 at 04:25:30, Tony Lindgren wrote:
> > > > Hi,
> > > >
> > > > * Vaibhav
On Mon, Mar 12, 2012 at 15:47:58, Balbi, Felipe wrote:
> Hi,
>
> On Mon, Mar 12, 2012 at 09:48:20AM +, Hiremath, Vaibhav wrote:
> > On Mon, Mar 12, 2012 at 15:09:24, Balbi, Felipe wrote:
> > > On Fri, Mar 09, 2012 at 05:58:00PM +, Hiremath, Vaibhav wrote:
> > > > On Tue, Mar 06, 2012 at 04
Hi,
On Tue, Jan 24, 2012 at 7:38 AM, Kevin Hilman wrote:
> Vaibhav Hiremath writes:
>
>> OMAP device has 32k-sync timer which is currently used as a
>> clocksource in the kernel (omap2plus_defconfig).
>> The current implementation uses compile time selection between
>> gp-timer and 32k-sync time
64 matches
Mail list logo