On Thu, Nov 17, 2011 at 6:23 AM, Omar Ramirez Luna or.r...@gmail.com wrote:
On Wed, Nov 16, 2011 at 12:18 AM, DebBarma, Tarun Kanti
tarun.ka...@ti.com wrote:
...
My use case is as follows:
DSP sends a mailbox message to ARM, this triggers a tasklet in mailbox
for processing the message,
On Thu, Nov 17, 2011 at 3:42 AM, DebBarma, Tarun Kanti
tarun.ka...@ti.com wrote:
...
Is the intention to restrict enabling the dmtimer clocks from hard|soft
irqs?
The aim is to prevent client drivers perform clock enable/disable
independently.
Instead just use the request/start/stop APIs.
On Wed, Nov 16, 2011 at 12:18 AM, DebBarma, Tarun Kanti
tarun.ka...@ti.com wrote:
...
My use case is as follows:
DSP sends a mailbox message to ARM, this triggers a tasklet in mailbox
for processing the message, when it reaches tidspbridge it turns out
that the DSP wants to enable a gpt
Hi Tarun,
On Tue, Sep 20, 2011 at 6:30 AM, Tarun Kanti DebBarma
tarun.ka...@ti.com wrote:
Clock is enabled only when timer is started and disabled when the the timer
is stopped. Therefore before accessing registers in functions clock is enabled
and then disabled back at the end of access.
On Tue, Nov 15, 2011 at 11:27 PM, Omar Ramirez Luna or.r...@gmail.com wrote:
Hi Tarun,
On Tue, Sep 20, 2011 at 6:30 AM, Tarun Kanti DebBarma
tarun.ka...@ti.com wrote:
Clock is enabled only when timer is started and disabled when the the timer
is stopped. Therefore before accessing registers
On Thu, Sep 22, 2011 at 6:30 AM, Tony Lindgren t...@atomide.com wrote:
* Tarun Kanti DebBarma tarun.ka...@ti.com [110920 03:57]:
Clock is enabled only when timer is started and disabled when the the timer
is stopped. Therefore before accessing registers in functions clock is
enabled
and then
* Tarun Kanti DebBarma tarun.ka...@ti.com [110920 03:57]:
Clock is enabled only when timer is started and disabled when the the timer
is stopped. Therefore before accessing registers in functions clock is enabled
and then disabled back at the end of access. Context save is done dynamically
Clock is enabled only when timer is started and disabled when the the timer
is stopped. Therefore before accessing registers in functions clock is enabled
and then disabled back at the end of access. Context save is done dynamically
whenever the registers are modified. Context restore is called
