From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756457AbcHBW5Y (ORCPT ); Tue, 2 Aug 2016 18:57:24 -0400 Received: from 216-12-86-13.cv.mvl.ntelos.net ([216.12.86.13]:59465 "EHLO brightrain.aerifal.cx" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752287AbcHBW5P (ORCPT ); Tue, 2 Aug 2016 18:57:15 -0400 Date: Tue, 2 Aug 2016 18:57:12 -0400 From: Rich Felker To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org Cc: Rob Herring , Mark Rutland , Daniel Lezcano , Thomas Gleixner Subject: Re: [PATCH v5 1/2] of: add J-Core timer bindings Message-ID: <20160802225712.GD15995@brightrain.aerifal.cx> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 17, 2016 at 11:18:58PM +0000, Rich Felker wrote: > Signed-off-by: Rich Felker > --- > .../devicetree/bindings/timer/jcore,pit.txt | 25 ++++++++++++++++++++++ > 1 file changed, 25 insertions(+) > create mode 100644 Documentation/devicetree/bindings/timer/jcore,pit.txt > > diff --git a/Documentation/devicetree/bindings/timer/jcore,pit.txt b/Documentation/devicetree/bindings/timer/jcore,pit.txt > new file mode 100644 > index 0000000..0f42af4 > --- /dev/null > +++ b/Documentation/devicetree/bindings/timer/jcore,pit.txt > @@ -0,0 +1,25 @@ > +J-Core Programmable Interval Timer and Clocksource > + > +Required properties: > + > +- compatible: Must be "jcore,pit". > + > +- reg: Memory region(s) for timer/clocksource registers. For SMP, > + there should be one region per cpu, indexed by the sequential, > + zero-based hardware cpu number (which is also the logical cpu > + number). One detail I missed: Mark Rutland asked me to remove the corresponding remark about logical cpu numbers from the AIC binding document, so I think it should be removed here too for the same reason -- it's a Linux implementation detail, not part of the hw binding. Rich