On Thu, Oct 13, 2016 at 05:52:30PM +0300, Noam Camus wrote:
> From: Noam Camus
>
> Till now we used clockevent from generic ARC driver.
> This was enough as long as we worked with simple multicore SoC.
> When we are working with multithread SoC each HW thread can be
> scheduled to receive timer i
>From: Noam Camus
>Sent: Tuesday, October 18, 2016 5:33 PM
>>You're letting Linux details define the binding. Are these blocks different
>>(the block itself, not connections to >the block like interrupts)?
>>If you need a particular timer instance to be used, then describe whatever is
>>the
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: Tuesday, October 18, 2016 4:57 PM
>>
>> Driver can be used from device tree by:
>> compatible = "ezchip,nps400-timer0" <-- for clocksource compatible =
>> "ezchip,nps400-timer1" <-- for clockevent
>You're letting Linux details define the bin
On Thu, Oct 13, 2016 at 05:52:30PM +0300, Noam Camus wrote:
> From: Noam Camus
>
> Till now we used clockevent from generic ARC driver.
> This was enough as long as we worked with simple multicore SoC.
> When we are working with multithread SoC each HW thread can be
> scheduled to receive timer i
4 matches
Mail list logo
