All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cousson, Benoit" <b-cousson@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "DebBarma, Tarun Kanti" <tarun.kanti@ti.com>,
	"Hilman, Kevin" <khilman@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Gopinath, Thara" <thara@ti.com>,
	"Basak, Partha" <p-basak2@ti.com>,
	Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCHv3 3/17] dmtimer: add omap2420 hwmod database
Date: Mon, 11 Oct 2010 17:34:49 +0200	[thread overview]
Message-ID: <4CB32E99.3000201@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1010110811400.16871@utopia.booyaka.com>

Hi Tarun,

On 10/11/2010 4:19 PM, Paul Walmsley wrote:
> On Mon, 11 Oct 2010, DebBarma, Tarun Kanti wrote:
>
>> In the present implementation there is inconsistency in the clock source
>> names for the different platforms, viz. OMAP2, OMAP3 and OMAP4 as shown
>> below. Therefore, I will have to modify the names so that they all have
>> common name across the platforms for the same type of clock. In this
>> regard I am proposing to modify the clock source names similar to OMAP4.
>> Of course we also have to look around to see if there are other modules
>> who are using the clock and make the necessary changes.
>
> Please look again at the links that I sent you.  All you need to change
> are the clkdev alias names for those clocks for that particular platform
> device name, "timer" or whatever it will be called.  That won't affect any
> other modules, since they will have different platform device names.  The
> struct clk.name fields will stay the same.

Otherwise using the clock source names similar to OMAP4 is the right 
thing to do.

Benoit

  reply	other threads:[~2010-10-11 15:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21  8:51 [PATCHv3 3/17] dmtimer: add omap2420 hwmod database Tarun Kanti DebBarma
2010-09-30 21:07 ` Cousson, Benoit
2010-10-01 22:25   ` Paul Walmsley
2010-10-04  7:50     ` Cousson, Benoit
2010-10-09 14:58       ` DebBarma, Tarun Kanti
2010-10-11 14:08         ` DebBarma, Tarun Kanti
2010-10-11 14:19           ` Paul Walmsley
2010-10-11 15:34             ` Cousson, Benoit [this message]
2010-10-12  6:12             ` DebBarma, Tarun Kanti
2010-10-12  6:22               ` Paul Walmsley

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=4CB32E99.3000201@ti.com \
    --to=b-cousson@ti.com \
    --cc=khilman@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.