On 3/31/2011 11:02 PM, Tony Lindgren wrote:
* Santosh Shilimkarsantosh.shilim...@ti.com [110331 01:14]:
On 3/30/2011 11:52 PM, Tony Lindgren wrote:
What it does not have is the code to dedicate gpt1 for PM
code, which can be done later once all the other dmtimer
changes are done.
Which not
On 3/30/2011 11:52 PM, Tony Lindgren wrote:
* Santosh Shilimkarsantosh.shilim...@ti.com [110330 00:53]:
After going through entire series again, it looks very
good clean-up and right step towards moving rest of
the timer to drivers/ directory.
I also realized that the discussion we had
* Santosh Shilimkar santosh.shilim...@ti.com [110331 01:14]:
On 3/30/2011 11:52 PM, Tony Lindgren wrote:
What it does not have is the code to dedicate gpt1 for PM
code, which can be done later once all the other dmtimer
changes are done.
Which not possible to do unless you plan to hack
Tony,
On 3/29/2011 3:51 AM, Tony Lindgren wrote:
Hi all,
This series continues the work to only initialize minimal omap code
in init_early and to cut down dependencies to code that should be
initialized later. It also cleans up the omap2+ timer init code to prepare
things for the later
* Santosh Shilimkar santosh.shilim...@ti.com [110330 00:53]:
After going through entire series again, it looks very
good clean-up and right step towards moving rest of
the timer to drivers/ directory.
I also realized that the discussion we had before this series was
because of
Tony Lindgren t...@atomide.com writes:
This series continues the work to only initialize minimal omap code
in init_early and to cut down dependencies to code that should be
initialized later. It also cleans up the omap2+ timer init code to prepare
things for the later patches.
After this
Hi all,
This series continues the work to only initialize minimal omap code
in init_early and to cut down dependencies to code that should be
initialized later. It also cleans up the omap2+ timer init code to prepare
things for the later patches.
After this series further patches can make the
