Hi Tony,
On 08/30/2012 03:14 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [120816 08:05]:
On 08/15/2012 04:11 AM, Vaibhav Hiremath wrote:
Did we get conclude on this? I haven't got anything further on this
thread, this may block baseport support for the new devices in omap2
* Jon Hunter jon-hun...@ti.com [120907 13:27]:
Hi Tony,
On 08/30/2012 03:14 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [120816 08:05]:
On 08/15/2012 04:11 AM, Vaibhav Hiremath wrote:
Did we get conclude on this? I haven't got anything further on this
thread, this may
On 09/07/2012 03:56 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [120907 13:27]:
Hi Tony,
On 08/30/2012 03:14 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [120816 08:05]:
On 08/15/2012 04:11 AM, Vaibhav Hiremath wrote:
Did we get conclude on this? I haven't got
On 07/23/2012 10:24 AM, Jon Hunter wrote:
Hi Rob,
On 07/16/2012 10:56 AM, Jon Hunter wrote:
Hi Rob,
On 07/13/2012 09:15 PM, Rob Herring wrote:
On 07/13/2012 05:26 PM, Jon Hunter wrote:
Add the 12 GP timers nodes present in OMAP3.
Add the 11 GP timers nodes present in OMAP4.
Add
On 09/06/2012 08:45 AM, Rob Herring wrote:
On 07/23/2012 10:24 AM, Jon Hunter wrote:
[snip]
Do you have any inputs on the above? Does it make sense to reserve timer
resources for kernel system timers in device-tree?
This issue is not unique to omap. So if we do specify clockevent and
* Jon Hunter jon-hun...@ti.com [120816 08:05]:
On 08/15/2012 04:11 AM, Vaibhav Hiremath wrote:
Did we get conclude on this? I haven't got anything further on this
thread, this may block baseport support for the new devices in omap2
family, like AM33xx and OMAP5.
Sorry I have been out
Hi Vaibhav,
On 08/15/2012 04:11 AM, Vaibhav Hiremath wrote:
On 7/23/2012 8:54 PM, Jon Hunter wrote:
Hi Rob,
On 07/16/2012 10:56 AM, Jon Hunter wrote:
Hi Rob,
On 07/13/2012 09:15 PM, Rob Herring wrote:
On 07/13/2012 05:26 PM, Jon Hunter wrote:
Add the 12 GP timers nodes present in
On 7/23/2012 8:54 PM, Jon Hunter wrote:
Hi Rob,
On 07/16/2012 10:56 AM, Jon Hunter wrote:
Hi Rob,
On 07/13/2012 09:15 PM, Rob Herring wrote:
On 07/13/2012 05:26 PM, Jon Hunter wrote:
Add the 12 GP timers nodes present in OMAP3.
Add the 11 GP timers nodes present in OMAP4.
Add
Hi Rob,
On 07/16/2012 10:56 AM, Jon Hunter wrote:
Hi Rob,
On 07/13/2012 09:15 PM, Rob Herring wrote:
On 07/13/2012 05:26 PM, Jon Hunter wrote:
Add the 12 GP timers nodes present in OMAP3.
Add the 11 GP timers nodes present in OMAP4.
Add documentation for timer properties specific to
* Jon Hunter jon-hun...@ti.com [120716 09:01]:
On 07/13/2012 09:15 PM, Rob Herring wrote:
Tony, Tarun,
How would you feel on replacing omap_dmtimer_request_specific(int id)
with say omap_dm_timer_request_by_cap(int cap)?
I was thinking of changing the name so that it is clear that the
Hi Tony,
On 07/18/2012 02:19 AM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [120716 09:01]:
On 07/13/2012 09:15 PM, Rob Herring wrote:
Tony, Tarun,
How would you feel on replacing omap_dmtimer_request_specific(int id)
with say omap_dm_timer_request_by_cap(int cap)?
I was
Hi Rob,
On 07/13/2012 09:15 PM, Rob Herring wrote:
On 07/13/2012 05:26 PM, Jon Hunter wrote:
Add the 12 GP timers nodes present in OMAP3.
Add the 11 GP timers nodes present in OMAP4.
Add documentation for timer properties specific to OMAP.
For each timer an alias is being added. The
Hi Rob,
On Sat, 14 Jul 2012, Paul Walmsley wrote:
My point, perhaps unclear, was about the aliases. Do you have a different
approach in mind that applications should use, other than requesting a
specific timer by ID?
Please disregard this question, I think I'm misunderstanding something
Hi
On Fri, 13 Jul 2012, Rob Herring wrote:
I'm not sure this is really a good use of aliases. UARTs use aliases
because it is important that the UART number to tty number is known and
fixed. IIUC, as an example you are picking timer1 because it has
properties X, Y and Z. If so, then you
On 07/14/2012 01:56 AM, Paul Walmsley wrote:
Hi
On Fri, 13 Jul 2012, Rob Herring wrote:
I'm not sure this is really a good use of aliases. UARTs use aliases
because it is important that the UART number to tty number is known and
fixed. IIUC, as an example you are picking timer1 because
Hi Rob,
thanks for your response.
On Sat, 14 Jul 2012, Rob Herring wrote:
On 07/14/2012 01:56 AM, Paul Walmsley wrote:
On Fri, 13 Jul 2012, Rob Herring wrote:
I'm not sure this is really a good use of aliases. UARTs use aliases
because it is important that the UART number to tty
Add the 12 GP timers nodes present in OMAP3.
Add the 11 GP timers nodes present in OMAP4.
Add documentation for timer properties specific to OMAP.
For each timer an alias is being added. The purpose for doing this is because
the OMAP dmtimer driver uses an ID to distinguish between the different
On 07/13/2012 05:26 PM, Jon Hunter wrote:
Add the 12 GP timers nodes present in OMAP3.
Add the 11 GP timers nodes present in OMAP4.
Add documentation for timer properties specific to OMAP.
For each timer an alias is being added. The purpose for doing this is because
the OMAP dmtimer
18 matches
Mail list logo
