Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1503009
| From | Rob Herring <robh@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 3/3] clocksource: Add clockevent support to NPS400 driver |
| Date | 2016-10-18 16:00 +0200 |
| Message-ID | <stD5U-2pf-11@gated-at.bofh.it> (permalink) |
| References | <stD5U-2pf-13@gated-at.bofh.it> <stD5U-2pf-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Oct 13, 2016 at 05:52:30PM +0300, Noam Camus wrote: > From: Noam Camus <noamca@mellanox.com> > > 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 interrupt using timer mask register > (TSI1). > > This patch will provide a way to control clock events per > HW thread. > > 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. Rob
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [PATCH 3/3] clocksource: Add clockevent support to NPS400 driver Rob Herring <robh@kernel.org> - 2016-10-18 16:00 +0200 RE: [PATCH 3/3] clocksource: Add clockevent support to NPS400 driver Noam Camus <noamca@mellanox.com> - 2016-10-18 16:40 +0200 RE: [PATCH 3/3] clocksource: Add clockevent support to NPS400 driver Noam Camus <noamca@mellanox.com> - 2016-10-18 20:30 +0200
csiph-web