From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: "DebBarma, Tarun Kanti" <tarun.kanti@ti.com>,
Paul Walmsley <paul@pwsan.com>, Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Gopinath, Thara" <thara@ti.com>,
"Basak, Partha" <p-basak2@ti.com>
Subject: Re: [PATCHv3 1/17] OMAP2/3/4:dmtimer:add device names to flck nodes
Date: Fri, 01 Oct 2010 08:49:12 -0700 [thread overview]
Message-ID: <87r5g9ap6v.fsf@deeprootsystems.com> (raw)
In-Reply-To: <4CA4F005.6000208@ti.com> (Benoit Cousson's message of "Thu, 30 Sep 2010 22:16:05 +0200")
"Cousson, Benoit" <b-cousson@ti.com> writes:
[...]
> Since we are in the name discussion, I'd like as well to potentially
> stop using the dmtimer / gptimer confusing naming convention, and
> replace that with a simple name "timer". Or potentially "omap_timer".
> Dual Mode timer does not mean at lot and General Purpose timer is not
> that better.
>
> We already started that discussion with Kevin some time ago but didn't
> really conclude.
>
> Tony, Paul and Kevin,
> Do you have any opinion on that subject?
Since the HW teams have decided on aligned names for all the IPs, I
think we should stick with those. In this case, "timer".
However, since that is such a generic word and used throughout the
kernel, maybe calling it omap_timer is better.
I'd live with either,
Kevin
prev parent reply other threads:[~2010-10-01 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 8:51 [PATCHv3 1/17] OMAP2/3/4:dmtimer:add device names to flck nodes Tarun Kanti DebBarma
2010-09-22 19:00 ` G, Manjunath Kondaiah
2010-09-30 20:16 ` Cousson, Benoit
2010-10-01 5:26 ` Varadarajan, Charulatha
2010-10-01 7:24 ` Cousson, Benoit
2010-10-09 15:00 ` DebBarma, Tarun Kanti
2010-10-01 15:49 ` Kevin Hilman [this message]
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=87r5g9ap6v.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=p-basak2@ti.com \
--cc=paul@pwsan.com \
--cc=tarun.kanti@ti.com \
--cc=thara@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.