From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [RFC RESEND 1/4] arm/dts: OMAP: Add timer nodes Date: Sat, 14 Jul 2012 09:01:21 -0500 Message-ID: <50017BB1.8010702@gmail.com> References: <1342218413-30116-1-git-send-email-jon-hunter@ti.com> <1342218413-30116-2-git-send-email-jon-hunter@ti.com> <5000D647.4090200@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-omap-owner@vger.kernel.org To: Paul Walmsley Cc: Jon Hunter , Tarun Kanti DebBarma , Tony Lindgren , Grant Likely , Benoit Cousson , linux-omap , linux-arm , device-tree List-Id: devicetree@vger.kernel.org On 07/14/2012 01:56 AM, Paul Walmsley wrote: > Hi > > On Fri, 13 Jul 2012, Rob Herring wrote: > >> I'm not sure this is really a good use of aliases. UARTs use aliases >> because it is important that the UART number to tty number is known and >> fixed. IIUC, as an example you are picking timer1 because it has >> properties X, Y and Z. If so, then you should describe those h/w >> properties within the timer nodes so you can pick which timer to use >> based on it's h/w properties. > > Some GPTIMER blocks have input and output signals that can be routed to > external package balls. So it's possible that some application may need > to request a specific timer ID, since that timer would be connected to a > specific off-chip device. Yes, I understand that. So you should be describing which ones have i/o and what they are connected to. The PWM binding is probably a starting point. Rob > > > - Paul >