From: Noam Camus <noamca@mellanox.com>
To: Rob Herring <robh@kernel.org>
CC: "mark.rutland@arm.com" <mark.rutland@arm.com>,
        "daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
        "tglx@linutronix.de" <tglx@linutronix.de>,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        John Stultz <john.stultz@linaro.org>
Subject: RE: [PATCH 3/3] clocksource: Add clockevent support to NPS400 driver
Thread-Topic: [PATCH 3/3] clocksource: Add clockevent support to NPS400 driver
Thread-Index: AQHSJWHNAIhk4uM0/Emszg2O/1pKxaCuRFQAgAAD//A=
Date: Tue, 18 Oct 2016 14:32:35 +0000
Message-ID: <DB6PR0501MB2518A9D069CA95DE52F4A698AAD30@DB6PR0501MB2518.eurprd05.prod.outlook.com>
References: <1476370350-3853-1-git-send-email-noamca@mellanox.com>
 <1476370350-3853-4-git-send-email-noamca@mellanox.com>
 <20161018135722.oflcjm5hfy6eugiy@rob-hp-laptop>
In-Reply-To: <20161018135722.oflcjm5hfy6eugiy@rob-hp-laptop>
Accept-Language: en-US
Content-Language: en-US
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Oct 2016 14:32:35.6179
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0501MB2518
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id u9IEWtUs011010
Content-Length: 949
Lines: 18

> From: Rob Herring [mailto:robh@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 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