RE: [PATCH 3/3] clocksource: Add clockevent support to NPS400 driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




>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 difference in the h/w.  For >example, the clockevent timer has to be the timer with an interrupt.

>Yes, blocks are different.
>The difference is that only second timer instance are actually producing timer interrupt served by Linux for the clockevent framework.
>Please note that the numbering used here for timer (i.e. 0 or 1) are derived from HW blocks and are not any Linux detail I used for binding definition (It is a note at this patch set cover letter).

The timers actually are: first instance (timer 0) for clockevents and second instance (timer 1) for clocksource.
Sorry for the confusion.

Noam
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux