On Thu, Nov 8, 2012 at 9:08 AM, Hiremath, Vaibhav hvaib...@ti.com wrote:
No we do not have 32k_counter block in AM335x.
If you are referring to 32Khz clock availability alone, then yes, we need to
get persistent clock and we use RTC 32Khz clock source for it.
But please note that this is not
On Sun, 11 Nov 2012, Igor Grinberg wrote:
Yep, but the /800 do not get you the 32768...
and that makes the timer suck.
Of course this can be dealt with in the clock subsystem
(I remember Paul said that he will look into that), but it will take time.
It should be possible to implement this
On 11/12/12 21:05, Jon Hunter wrote:
On 11/11/2012 03:16 AM, Igor Grinberg wrote:
On 11/08/12 18:20, Tony Lindgren wrote:
* Igor Grinberg grinb...@compulab.co.il [121107 23:15]:
On 11/07/12 19:33, Tony Lindgren wrote:
I think this should be the default for the timers as that counter
does
On 11/12/12 21:15, Jon Hunter wrote:
On 11/11/2012 05:28 AM, Igor Grinberg wrote:
On 11/08/12 21:16, Jon Hunter wrote:
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is
On 11/13/2012 03:14 AM, Igor Grinberg wrote:
On 11/12/12 21:15, Jon Hunter wrote:
On 11/11/2012 05:28 AM, Igor Grinberg wrote:
On 11/08/12 21:16, Jon Hunter wrote:
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59
On 11/13/12 18:13, Jon Hunter wrote:
On 11/13/2012 03:14 AM, Igor Grinberg wrote:
On 11/12/12 21:15, Jon Hunter wrote:
On 11/11/2012 05:28 AM, Igor Grinberg wrote:
On 11/08/12 21:16, Jon Hunter wrote:
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23,
On Fri, Nov 09, 2012 at 00:46:28, Hunter, Jon wrote:
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no reliable way to determine which source should be used in
On Mon, Nov 12, 2012 at 12:54:59, Igor Grinberg wrote:
On 11/12/12 08:38, Hiremath, Vaibhav wrote:
On Sun, Nov 11, 2012 at 17:05:07, Igor Grinberg wrote:
On 11/08/12 20:34, Jon Hunter wrote:
On 11/08/2012 12:17 PM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
On
Hi Vaibhav,
On 11/12/2012 11:38 AM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:46:28, Hunter, Jon wrote:
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no
On 11/11/2012 03:16 AM, Igor Grinberg wrote:
On 11/08/12 18:20, Tony Lindgren wrote:
* Igor Grinberg grinb...@compulab.co.il [121107 23:15]:
On 11/07/12 19:33, Tony Lindgren wrote:
I think this should be the default for the timers as that counter
does not stop during deeper idle states.
On 11/11/2012 05:28 AM, Igor Grinberg wrote:
On 11/08/12 21:16, Jon Hunter wrote:
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no reliable way to determine which
* Igor Grinberg grinb...@compulab.co.il [12 01:18]:
On 11/08/12 18:20, Tony Lindgren wrote:
I guess what I'm after is just to avoid renaming the existing
timers in the board-*.c files and only rename the ones that
need gp timer only.
This means: get rid of the 32k to gptimer fall
On 11/08/12 18:20, Tony Lindgren wrote:
* Igor Grinberg grinb...@compulab.co.il [121107 23:15]:
On 11/07/12 19:33, Tony Lindgren wrote:
I think this should be the default for the timers as that counter
does not stop during deeper idle states.
Well, it is the default as you can see from the
On 11/08/12 18:16, Jon Hunter wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
On 11/07/12 23:36, Jon Hunter wrote:
Hi Igor,
On 11/07/2012 08:42 AM, Igor Grinberg wrote:
CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way.
Make OMAP2+ timer code independant from the
On 11/08/12 21:16, Jon Hunter wrote:
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no reliable way to determine which source should be used in
runtime
for boards that
On 11/08/12 20:34, Jon Hunter wrote:
On 11/08/2012 12:17 PM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
On 11/08/2012 11:58 AM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
Igor was mentioning a h/w scenario where the 32kHz source is not
present. However,
On Sun, Nov 11, 2012 at 17:05:07, Igor Grinberg wrote:
On 11/08/12 20:34, Jon Hunter wrote:
On 11/08/2012 12:17 PM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
On 11/08/2012 11:58 AM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
Igor was
On Fri, Nov 09, 2012 at 06:25:49, Hunter, Jon wrote:
On 11/08/2012 12:06 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote:
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
[snip]
I think you are
On 11/12/12 08:38, Hiremath, Vaibhav wrote:
On Sun, Nov 11, 2012 at 17:05:07, Igor Grinberg wrote:
On 11/08/12 20:34, Jon Hunter wrote:
On 11/08/2012 12:17 PM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
On 11/08/2012 11:58 AM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon
On 11/07/12 23:36, Jon Hunter wrote:
Hi Igor,
On 11/07/2012 08:42 AM, Igor Grinberg wrote:
CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way.
Make OMAP2+ timer code independant from the CONFIG_OMAP_32K_TIMER
setting.
To remove the dependancy, several conversions/additions
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
On 11/07/12 23:36, Jon Hunter wrote:
Hi Igor,
On 11/07/2012 08:42 AM, Igor Grinberg wrote:
CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way.
Make OMAP2+ timer code independant from the CONFIG_OMAP_32K_TIMER
setting.
To remove
* Igor Grinberg grinb...@compulab.co.il [121107 23:15]:
On 11/07/12 19:33, Tony Lindgren wrote:
I think this should be the default for the timers as that counter
does not stop during deeper idle states.
Well, it is the default as you can see from the patch.
The problem is that for
On Thu, Nov 08, 2012 at 21:46:53, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
On 11/07/12 23:36, Jon Hunter wrote:
Hi Igor,
On 11/07/2012 08:42 AM, Igor Grinberg wrote:
CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way.
Make OMAP2+ timer code
On Thu, Nov 08, 2012 at 21:50:05, Tony Lindgren wrote:
* Igor Grinberg grinb...@compulab.co.il [121107 23:15]:
On 11/07/12 19:33, Tony Lindgren wrote:
I think this should be the default for the timers as that counter
does not stop during deeper idle states.
Well, it is the
On 11/08/2012 11:08 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 21:46:53, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
On 11/07/12 23:36, Jon Hunter wrote:
Hi Igor,
On 11/07/2012 08:42 AM, Igor Grinberg wrote:
CONFIG_OMAP_32K_TIMER is kind of standing on the
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
On 11/08/2012 11:08 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 21:46:53, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
On 11/07/12 23:36, Jon Hunter wrote:
Hi Igor,
On 11/07/2012 08:42 AM, Igor
On Thu, 8 Nov 2012, Jon Hunter wrote:
Igor was mentioning a h/w scenario where the 32kHz source is not
present. However, I am not sure which devices support this and is
applicable too.
Pretty sure Igor is referring to the AM3517/3505. This is very poorly
documented, but can be observed in
On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote:
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
[snip]
I think you are missing the point here. For OMAP devices we have two
main external clock sources which are the 32kHz clock
On 11/08/2012 11:58 AM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
Igor was mentioning a h/w scenario where the 32kHz source is not
present. However, I am not sure which devices support this and is
applicable too.
Pretty sure Igor is referring to the AM3517/3505. This is
On 11/08/2012 12:06 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote:
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
[snip]
I think you are missing the point here. For OMAP devices we have two
main
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
[snip]
I think you are missing the point here. For OMAP devices we have two
main external clock sources which are the 32kHz clock and the sys_clk
(can be a range of frequencies from
On Thu, 8 Nov 2012, Jon Hunter wrote:
On 11/08/2012 11:58 AM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
Igor was mentioning a h/w scenario where the 32kHz source is not
present. However, I am not sure which devices support this and is
applicable too.
Pretty sure
On Thu, Nov 08, 2012 at 23:43:31, Hunter, Jon wrote:
On 11/08/2012 12:06 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote:
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
[snip]
I think you are
On 11/08/2012 12:17 PM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
On 11/08/2012 11:58 AM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
Igor was mentioning a h/w scenario where the 32kHz source is not
present. However, I am not sure which devices support this
On 11/08/2012 12:28 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:43:31, Hunter, Jon wrote:
On 11/08/2012 12:06 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote:
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57,
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no reliable way to determine which source should be used in runtime
for boards that do not have the 32k oscillator wired.
So thinking about this some more and given that we are moving away from
board files, if a board does not
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no reliable way to determine which source should be used in runtime
for boards that do not have the 32k oscillator wired.
So thinking about this some more and given that
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no reliable way to determine which source should be used in runtime
for boards that do not have the 32k oscillator wired.
So
On 11/08/2012 12:06 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote:
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
[snip]
I think you are missing the point here. For OMAP devices we have two
main
CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way.
Make OMAP2+ timer code independant from the CONFIG_OMAP_32K_TIMER
setting.
To remove the dependancy, several conversions/additions had to be done:
1) Timer structures and initialization functions are named by the platform
name
* Igor Grinberg grinb...@compulab.co.il [121107 06:44]:
CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way.
Make OMAP2+ timer code independant from the CONFIG_OMAP_32K_TIMER
setting.
To remove the dependancy, several conversions/additions had to be done:
1) Timer structures
Hi Igor,
On 11/07/2012 08:42 AM, Igor Grinberg wrote:
CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way.
Make OMAP2+ timer code independant from the CONFIG_OMAP_32K_TIMER
setting.
To remove the dependancy, several conversions/additions had to be done:
1) Timer structures and
On 11/07/12 19:33, Tony Lindgren wrote:
* Igor Grinberg grinb...@compulab.co.il [121107 06:44]:
CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way.
Make OMAP2+ timer code independant from the CONFIG_OMAP_32K_TIMER
setting.
To remove the dependancy, several
43 matches
Mail list logo
