linux-kernel - Re: [PATCH 3/3] clocksource: Add clockevent support to NPS400 driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 18 Oct 2016 08:57:22 -0500
From:   Rob Herring <robh@...nel.org>
To:     Noam Camus <noamca@...lanox.com>
Cc:     mark.rutland@....com, daniel.lezcano@...aro.org,
        tglx@...utronix.de, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, John Stultz <john.stultz@...aro.org>
Subject: Re: [PATCH 3/3] clocksource: Add clockevent support to NPS400 driver

On Thu, Oct 13, 2016 at 05:52:30PM +0300, Noam Camus wrote:
> From: Noam Camus <noamca@...lanox.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