From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030315AbcJRSYT (ORCPT ); Tue, 18 Oct 2016 14:24:19 -0400 Received: from mail-db5eur01on0079.outbound.protection.outlook.com ([104.47.2.79]:6342 "EHLO EUR01-DB5-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755715AbcJRSYQ (ORCPT ); Tue, 18 Oct 2016 14:24:16 -0400 From: Noam Camus To: Rob Herring CC: "mark.rutland@arm.com" , "daniel.lezcano@linaro.org" , "tglx@linutronix.de" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , John Stultz 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//CAAAnhkA== Date: Tue, 18 Oct 2016 14:51:05 +0000 Message-ID: References: <1476370350-3853-1-git-send-email-noamca@mellanox.com> <1476370350-3853-4-git-send-email-noamca@mellanox.com> <20161018135722.oflcjm5hfy6eugiy@rob-hp-laptop> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=noamca@mellanox.com; x-originating-ip: [212.179.42.66] x-ms-office365-filtering-correlation-id: 1cebdb69-3f9f-44f1-bdb5-08d3f7663035 x-microsoft-exchange-diagnostics: 1;DB6PR0501MB2519;7:kyKAVo+kddHCUMP2P+1qJoN6Xavh1q32h+2XFpAfDzPsWC0sD2+WDWTSxBi/We1ZKJgwE55JTOOjI/lBnqT6a+uTVUA7Hzngz3iNigGVA3aD2rjlUAH44x3W3J0aq0j73rKtN5LL3QlPADJ9EuGDQg2Hc3+zeeeQ+FZlP+htos/nk6bpeUYu/c8ggkXSp5kG4q4cg+QPFu0Ejyzm7PMHjHFtjhWOx6mhd70B9SaSlVIXm69kDbpDojj+VPGg4wCbor7O7kBL6xO3ahA94EgLDnApTaYcnf30ksJnsGu5LaN+hzIiw6UG0AoIMHSI122M0kXb1CtLO2lKcu0UxXi1maWjw7evkQFAlNj6AFzo6ew= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB6PR0501MB2519; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026);SRVR:DB6PR0501MB2519;BCL:0;PCL:0;RULEID:;SRVR:DB6PR0501MB2519; x-forefront-prvs: 00997889E7 x-forefront-antispam-report: SFV:NSPM;SFS:(10009020)(6009001)(7916002)(199003)(189002)(377454003)(2900100001)(68736007)(6916009)(50986999)(33656002)(4326007)(110136003)(7696004)(106356001)(2906002)(87936001)(3846002)(66066001)(3660700001)(6116002)(74316002)(97736004)(3280700002)(122556002)(11100500001)(77096005)(8676002)(101416001)(86362001)(81156014)(92566002)(106116001)(5002640100001)(54356999)(10400500002)(586003)(102836003)(189998001)(76176999)(5660300001)(76576001)(7846002)(8936002)(7736002)(305945005)(81166006)(105586002)(9686002);DIR:OUT;SFP:1101;SCL:1;SRVR:DB6PR0501MB2519;H:DB6PR0501MB2518.eurprd05.prod.outlook.com;FPR:;SPF:None;PTR:InfoNoRecords;A:1;MX:1;LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 X-OriginatorOrg: Mellanox.com X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Oct 2016 14:51:05.5493 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0501MB2519 Sender: linux-kernel-owner@vger.kernel.org List-ID: 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 u9IIOM4J012723 >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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Noam Camus Subject: RE: [PATCH 3/3] clocksource: Add clockevent support to NPS400 driver Date: Tue, 18 Oct 2016 14:51:05 +0000 Message-ID: References: <1476370350-3853-1-git-send-email-noamca@mellanox.com> <1476370350-3853-4-git-send-email-noamca@mellanox.com> <20161018135722.oflcjm5hfy6eugiy@rob-hp-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: Content-Language: en-US Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Rob Herring Cc: "mark.rutland-5wv7dgnIgG8@public.gmane.org" , "daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org" , "tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org" , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , John Stultz List-Id: devicetree@vger.kernel.org >From: Noam Camus=20 >Sent: Tuesday, October 18, 2016 5:33 PM >>You're letting Linux details define the binding. Are these blocks differe= nt (the block itself, not connections to >the block like interrupts)? >>If you need a particular timer instance to be used, then describe whateve= r 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 t= imer interrupt served by Linux for the clockevent framework. >Please note that the numbering used here for timer (i.e. 0 or 1) are deriv= ed from HW blocks and are not any Linux detail I used for binding definitio= n (It is a note at this patch set cover letter). The timers actually are: first instance (timer 0) for clockevents and secon= d 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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html