Thread (10 messages) 10 messages, 3 authors, 2016-10-21

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

From: Noam Camus <hidden>
Date: 2016-10-18 14:32:52
Also in: lkml

From: Rob Herring [mailto:robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org] 
Sent: Tuesday, October 18, 2016 4:57 PM
quoted
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 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).

Noam
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help