From: Rob Herring <robherring2@gmail.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Jon Hunter <jon-hunter@ti.com>,
Tarun Kanti DebBarma <tarun.kanti@ti.com>,
Tony Lindgren <tony@atomide.com>,
Grant Likely <grant.likely@secretlab.ca>,
Benoit Cousson <b-cousson@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
device-tree <devicetree-discuss@lists.ozlabs.org>
Subject: Re: [RFC RESEND 1/4] arm/dts: OMAP: Add timer nodes
Date: Sat, 14 Jul 2012 09:01:21 -0500 [thread overview]
Message-ID: <50017BB1.8010702@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1207140048210.3876@utopia.booyaka.com>
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
>
WARNING: multiple messages have this Message-ID (diff)
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC RESEND 1/4] arm/dts: OMAP: Add timer nodes
Date: Sat, 14 Jul 2012 09:01:21 -0500 [thread overview]
Message-ID: <50017BB1.8010702@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1207140048210.3876@utopia.booyaka.com>
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
>
next prev parent reply other threads:[~2012-07-14 14:01 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 22:26 [RFC RESEND 0/4] ARM: OMAP3+: Add device-tree support for timers Jon Hunter
2012-07-13 22:26 ` Jon Hunter
2012-07-13 22:26 ` [RFC RESEND 1/4] arm/dts: OMAP: Add timer nodes Jon Hunter
2012-07-13 22:26 ` Jon Hunter
2012-07-14 2:15 ` Rob Herring
2012-07-14 2:15 ` Rob Herring
[not found] ` <5000D647.4090200-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-07-14 5:30 ` Mis?use of aliases Mitch Bradley
[not found] ` <50010402.3050502-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2012-07-14 16:37 ` David Gibson
2012-07-14 16:37 ` David Gibson
[not found] ` <20120714163701.GI11326-MK4v0fQdeXQXU02nzanrWNbf9cGiqdzd@public.gmane.org>
2012-07-14 17:07 ` Mitch Bradley
2012-07-14 17:07 ` Mitch Bradley
[not found] ` <5001A745.3000509-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2012-07-15 7:39 ` David Gibson
2012-07-15 7:39 ` David Gibson
2012-07-14 6:56 ` [RFC RESEND 1/4] arm/dts: OMAP: Add timer nodes Paul Walmsley
2012-07-14 6:56 ` Paul Walmsley
2012-07-14 14:01 ` Rob Herring [this message]
2012-07-14 14:01 ` Rob Herring
[not found] ` <50017BB1.8010702-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-07-14 17:42 ` Paul Walmsley
2012-07-14 17:42 ` Paul Walmsley
2012-07-16 17:48 ` Paul Walmsley
2012-07-16 17:48 ` Paul Walmsley
2012-07-16 15:56 ` Jon Hunter
2012-07-16 15:56 ` Jon Hunter
2012-07-18 7:19 ` Tony Lindgren
2012-07-18 7:19 ` Tony Lindgren
2012-07-18 15:11 ` Jon Hunter
2012-07-18 15:11 ` Jon Hunter
2012-07-23 15:24 ` Jon Hunter
2012-07-23 15:24 ` Jon Hunter
2012-08-15 9:11 ` Vaibhav Hiremath
2012-08-15 9:11 ` Vaibhav Hiremath
2012-08-16 15:04 ` Jon Hunter
2012-08-16 15:04 ` Jon Hunter
2012-08-30 20:14 ` Tony Lindgren
2012-08-30 20:14 ` Tony Lindgren
2012-09-07 20:26 ` Jon Hunter
2012-09-07 20:26 ` Jon Hunter
2012-09-07 20:56 ` Tony Lindgren
2012-09-07 20:56 ` Tony Lindgren
2012-09-07 21:16 ` Jon Hunter
2012-09-07 21:16 ` Jon Hunter
2012-09-06 13:45 ` Rob Herring
2012-09-06 13:45 ` Rob Herring
[not found] ` <5048A8F6.6080108-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-09-07 2:09 ` Jon Hunter
2012-09-07 2:09 ` Jon Hunter
2012-07-13 22:26 ` [RFC RESEND 2/4] ARM: OMAP3: Dynamically disable secure timer nodes for secure devices Jon Hunter
2012-07-13 22:26 ` Jon Hunter
2012-08-15 9:13 ` Vaibhav Hiremath
2012-08-15 9:13 ` Vaibhav Hiremath
2012-08-16 16:57 ` Jon Hunter
2012-08-16 16:57 ` Jon Hunter
[not found] ` <502D2686.4090107-l0cyMroinI0@public.gmane.org>
2012-08-17 5:32 ` Hiremath, Vaibhav
2012-08-17 5:32 ` Hiremath, Vaibhav
2012-08-17 12:24 ` Jon Hunter
2012-08-17 12:24 ` Jon Hunter
2012-08-24 15:56 ` Hiremath, Vaibhav
2012-08-24 15:56 ` Hiremath, Vaibhav
2012-07-13 22:26 ` [RFC RESEND 3/4] ARM: OMAP4: Add timer clock aliases for device-tree Jon Hunter
2012-07-13 22:26 ` Jon Hunter
2012-07-13 22:26 ` [RFC RESEND 4/4] ARM: OMAP: Add DT support for timer driver Jon Hunter
2012-07-13 22:26 ` Jon Hunter
2012-07-13 23:41 ` Paul Walmsley
2012-07-13 23:41 ` Paul Walmsley
[not found] ` <alpine.DEB.2.00.1207131740460.25585-rwI8Ez+7Ko+d5PgPZx9QOdBPR1lH4CV8@public.gmane.org>
2012-07-14 0:57 ` Jon Hunter
2012-07-14 0:57 ` Jon Hunter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50017BB1.8010702@gmail.com \
--to=robherring2@gmail.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tarun.kanti@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.