On Wed, Apr 11, 2012 at 6:30 AM, Ming Lei tom.leim...@gmail.com wrote:
On Tue, Apr 10, 2012 at 5:51 PM, Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
On Tue, Apr 10, 2012 at 2:59 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Tue, Apr 10, 2012 at 02:27:36PM +0530, Santosh
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
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 I am
On Tue, Apr 10, 2012 at 2:59 PM, Russell King - ARM Linux
li...@arm.linux.org.uk 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
On 04/10/2012 04:51 AM, Shilimkar, Santosh wrote:
On Tue, Apr 10, 2012 at 2:59 PM, Russell King - ARM Linux
li...@arm.linux.org.uk 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,
On Tue, Apr 10, 2012 at 5:51 PM, Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
On Tue, Apr 10, 2012 at 2:59 PM, Russell King - ARM Linux
li...@arm.linux.org.uk 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
On Fri, Apr 06, 2012 at 23:34:52, Tony Lindgren wrote:
* Hiremath, Vaibhav hvaib...@ti.com [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
On Sat, Apr 07, 2012 at 02:48:47, Hilman, Kevin wrote:
Hiremath, Vaibhav hvaib...@ti.com 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
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
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 gptimer; it is
* Hiremath, Vaibhav hvaib...@ti.com [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
Hiremath, Vaibhav hvaib...@ti.com 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
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 hvaib...@ti.com wrote:
On Tue, Apr 03, 2012 at 00:05:38, Hilman, Kevin wrote:
Shilimkar, Santosh
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
registered
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 implementation
Hiremath, Vaibhav hvaib...@ti.com 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
On Fri, Apr 06, 2012 at 03:03:01, Hilman, Kevin wrote:
Hiremath, Vaibhav hvaib...@ti.com 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
On Tue, Apr 3, 2012 at 9:05 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Tue, Apr 03, 2012 at 00:05:38, Hilman, Kevin wrote:
Shilimkar, Santosh santosh.shilim...@ti.com writes:
[...]
I don't personally like to add features which hardly anybody use and
fundamentally broken with full
On Wed, Apr 04, 2012 at 14:34:09, Shilimkar, Santosh wrote:
On Tue, Apr 3, 2012 at 9:05 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Tue, Apr 03, 2012 at 00:05:38, Hilman, Kevin wrote:
Shilimkar, Santosh santosh.shilim...@ti.com writes:
[...]
I don't personally like to add
On Tue, Apr 03, 2012 at 00:05:38, Hilman, Kevin wrote:
Shilimkar, Santosh santosh.shilim...@ti.com 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
On Tue, Apr 3, 2012 at 12:05 AM, Kevin Hilman khil...@ti.com wrote:
Shilimkar, Santosh santosh.shilim...@ti.com 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
On Sat, Mar 31, 2012 at 7:00 AM, Ming Lei tom.leim...@gmail.com wrote:
On Fri, Mar 30, 2012 at 5:20 PM, Shilimkar, Santosh santosh.shilim...@ti.com
After Ming Lie's comment, the point that I came to my mind was,
certainly there will be resolution difference between these two
clocksources,
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
On Sat, Mar 31, 2012 at 2:09 PM, Ming Lei tom.leim...@gmail.com 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,
On Sun, Apr 1, 2012 at 3:10 AM, Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
On Sat, Mar 31, 2012 at 2:09 PM, Ming Lei tom.leim...@gmail.com 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
On Sun, Apr 1, 2012 at 7:09 AM, Ming Lei tom.leim...@gmail.com wrote:
On Sun, Apr 1, 2012 at 3:10 AM, Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
On Sat, Mar 31, 2012 at 2:09 PM, Ming Lei tom.leim...@gmail.com wrote:
On Sat, Mar 31, 2012 at 2:30 PM, Shilimkar, Santosh
Since you need to
On Wed, Mar 28, 2012 at 20:19:07, Shilimkar, Santosh wrote:
On Wed, Mar 28, 2012 at 8:07 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Wed, Mar 28, 2012 at 19:50:02, Shilimkar, Santosh wrote:
On Wed, Mar 28, 2012 at 7:46 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Wed, Mar 21, 2012
On Fri, Mar 30, 2012 at 12:04 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Wed, Mar 28, 2012 at 20:19:07, Shilimkar, Santosh wrote:
On Wed, Mar 28, 2012 at 8:07 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Wed, Mar 28, 2012 at 19:50:02, Shilimkar, Santosh wrote:
On Wed, Mar 28, 2012 at
On Fri, Mar 30, 2012 at 13:11:35, Shilimkar, Santosh wrote:
On Fri, Mar 30, 2012 at 12:04 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Wed, Mar 28, 2012 at 20:19:07, Shilimkar, Santosh wrote:
On Wed, Mar 28, 2012 at 8:07 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Wed, Mar 28, 2012
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 hvaib...@ti.com wrote:
On Wed, Mar 28, 2012 at 20:19:07, Shilimkar, Santosh wrote:
On Wed, Mar 28, 2012 at 8:07 PM,
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 hvaib...@ti.com
wrote:
On Wed, Mar 28, 2012 at 20:19:07,
On Fri, Mar 30, 2012 at 2:42 PM, Hiremath, Vaibhav hvaib...@ti.com 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
On Fri, Mar 30, 2012 at 14:50:02, Shilimkar, Santosh wrote:
On Fri, Mar 30, 2012 at 2:42 PM, Hiremath, Vaibhav hvaib...@ti.com 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,
On Fri, Mar 30, 2012 at 2:58 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Fri, Mar 30, 2012 at 14:50:02, Shilimkar, Santosh wrote:
On Fri, Mar 30, 2012 at 2:42 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Fri, Mar 30, 2012 at 14:08:20, Shilimkar, Santosh wrote:
On Friday 30 March 2012
On Fri, Mar 30, 2012 at 15:12:19, Shilimkar, Santosh wrote:
On Fri, Mar 30, 2012 at 2:58 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Fri, Mar 30, 2012 at 14:50:02, Shilimkar, Santosh wrote:
On Fri, Mar 30, 2012 at 2:42 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Fri, Mar 30, 2012
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 hvaib...@ti.com wrote:
On Fri, Mar 30, 2012 at 14:50:02, Shilimkar, Santosh wrote:
On Fri, Mar 30, 2012 at 2:42 PM,
On Fri, Mar 30, 2012 at 5:20 PM, Shilimkar, Santosh santosh.shilim...@ti.com
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
On Wed, Mar 21, 2012 at 19:30:01, Shilimkar, Santosh wrote:
On Wed, Mar 21, 2012 at 5:12 PM, Hiremath, Vaibhav hvaib...@ti.com 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,
On Wed, Mar 28, 2012 at 7:46 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Wed, Mar 21, 2012 at 19:30:01, Shilimkar, Santosh wrote:
On Wed, Mar 21, 2012 at 5:12 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Mon, Mar 19, 2012 at 17:45:32, Shilimkar, Santosh wrote:
On Monday 19 March 2012
On Wed, Mar 28, 2012 at 19:50:02, Shilimkar, Santosh wrote:
On Wed, Mar 28, 2012 at 7:46 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Wed, Mar 21, 2012 at 19:30:01, Shilimkar, Santosh wrote:
On Wed, Mar 21, 2012 at 5:12 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Mon, Mar 19, 2012
On Wed, Mar 28, 2012 at 8:07 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Wed, Mar 28, 2012 at 19:50:02, Shilimkar, Santosh wrote:
On Wed, Mar 28, 2012 at 7:46 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Wed, Mar 21, 2012 at 19:30:01, Shilimkar, Santosh wrote:
On Wed, Mar 21, 2012 at
On Wed, Mar 21, 2012 at 7:29 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Mon, Mar 19, 2012 at 17:14:30, Ming Lei wrote:
On Mon, Mar 19, 2012 at 7:11 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
I think you made very good point here. With the above patch, we are almost
missing the
On Mon, Mar 19, 2012 at 17:14:30, Ming Lei wrote:
On Mon, Mar 19, 2012 at 7:11 PM, Hiremath, Vaibhav hvaib...@ti.com 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
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 hvaib...@ti.com wrote:
I think you made very good point here. With the above patch, we are almost
missing the capability of
On Wed, Mar 21, 2012 at 5:12 PM, Hiremath, Vaibhav hvaib...@ti.com 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 hvaib...@ti.com wrote:
I think you made very good point
On Tue, Mar 13, 2012 at 17:07:16, Ming Lei wrote:
Hi,
On Tue, Jan 24, 2012 at 7:38 AM, Kevin Hilman khil...@ti.com wrote:
Vaibhav Hiremath hvaib...@ti.com writes:
OMAP device has 32k-sync timer which is currently used as a
clocksource in the kernel (omap2plus_defconfig).
The current
On Mon, Mar 19, 2012 at 7:11 PM, Hiremath, Vaibhav hvaib...@ti.com 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
On Monday 19 March 2012 05:14 PM, Ming Lei wrote:
On Mon, Mar 19, 2012 at 7:11 PM, Hiremath, Vaibhav hvaib...@ti.com 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
Hi,
On Tue, Jan 24, 2012 at 7:38 AM, Kevin Hilman khil...@ti.com wrote:
Vaibhav Hiremath hvaib...@ti.com 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
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 hvaib...@ti.com [120119 06:01]:
OMAP device has 32k-sync timer which is currently used as a
clocksource in the kernel
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 hvaib...@ti.com [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 Hiremath
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:25:30,
On Tue, Mar 06, 2012 at 04:25:30, Tony Lindgren wrote:
Hi,
* Vaibhav Hiremath hvaib...@ti.com [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
On Tue, Mar 06, 2012 at 04:25:30, Tony Lindgren wrote:
Hi,
* Vaibhav Hiremath hvaib...@ti.com [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
Hi,
* Vaibhav Hiremath hvaib...@ti.com [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
On Tue, Jan 24, 2012 at 23:17:56, Hilman, Kevin wrote:
Hiremath, Vaibhav hvaib...@ti.com writes:
On Tue, Jan 24, 2012 at 05:08:50, Hilman, Kevin wrote:
Vaibhav Hiremath hvaib...@ti.com writes:
OMAP device has 32k-sync timer which is currently used as a
clocksource in the kernel
On Tue, Jan 24, 2012 at 05:08:50, Hilman, Kevin wrote:
Vaibhav Hiremath hvaib...@ti.com 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
Hiremath, Vaibhav hvaib...@ti.com writes:
On Tue, Jan 24, 2012 at 05:08:50, Hilman, Kevin wrote:
Vaibhav Hiremath hvaib...@ti.com writes:
OMAP device has 32k-sync timer which is currently used as a
clocksource in the kernel (omap2plus_defconfig).
The current implementation uses compile
Vaibhav Hiremath hvaib...@ti.com 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
62 matches
Mail list logo
