All of lore.kernel.org
 help / color / mirror / Atom feed
From: nsekhar@ti.com (Nori, Sekhar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] davinci: dm6467/T EVM: pass reference clock rate to dm646x_init()
Date: Mon, 6 Jun 2011 18:32:21 +0530	[thread overview]
Message-ID: <B85A65D85D7EB246BE421B3FB0FBB593024D383514@dbde02.ent.ti.com> (raw)
In-Reply-To: <20110606122552.GA2729@xyzzy.org.uk>

Hi Bob,

On Mon, Jun 06, 2011 at 17:55:52, Bob Dunlop wrote:
> Hi,
> 
> On Mon, Jun 06 at 05:01, Nori, Sekhar wrote:
> > On Sun, Jun 05, 2011 at 18:30:04, Sergei Shtylyov wrote:
> > >     I don't think you should ascribe *your* patch to Bob. There's 
> > > Suggested-by: line if you want to credit Bob.
> > 
> > Bob, do you have an opinion on this? If not, I will go with what
> > Sergei is suggesting.
> 
> I have no problem one way or the other, we all know who we are.

Okay, I will do what Sergei is suggesting then.

> 
> Anyway I'd like to propose a simpler patch that covers both boards in one.
> Fewer files touched than the original da850 patch.
> 
> Add the ref_clk_rate parameter to the davinci_soc_info structure and
> perform the clock adjustment in davinci_common_init().  The code assumes

Lets not extend davinci_soc_info any further. We need to be looking
at ways of reducing its usage (for example by making GPIO code use
platform device).

Also, refclk is a board information not soc information so placing
it there makes it misplaced.

> that if which to tweak the ref_clk it will be the first one listed in
> cpu_clocks[] which is the case for all boards sofar.
> 
> The only downside is you need to export the davinci_soc_info_dm646x struct
> in order to tweak it.

That's not very elegant as well. SoC information structure for a given
SoC should be private to the SoC specific file. Making it public will
open it up for abuse.

Thanks,
Sekhar

  reply	other threads:[~2011-06-06 13:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 17:11 [PATCH 1/3] davinci: dm646x.h: include header files under mach/ after those in linux/ Sekhar Nori
2011-06-02 17:11 ` [PATCH 2/3] davinci: dm6467/T EVM: pass reference clock rate to dm646x_init() Sekhar Nori
2011-06-02 17:11   ` [PATCH v3 3/3] davinci: da850: move input frequency to board specific files Sekhar Nori
2011-06-02 18:01   ` [PATCH 2/3] davinci: dm6467/T EVM: pass reference clock rate to dm646x_init() Olof Johansson
2011-06-03 11:32     ` Nori, Sekhar
2011-06-03 16:59       ` Olof Johansson
2011-06-05 11:24         ` Nori, Sekhar
2011-06-05 13:00   ` Sergei Shtylyov
2011-06-06 11:31     ` Nori, Sekhar
2011-06-06 12:25       ` Bob Dunlop
2011-06-06 13:02         ` Nori, Sekhar [this message]
2011-06-07  7:41           ` Bob Dunlop

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=B85A65D85D7EB246BE421B3FB0FBB593024D383514@dbde02.ent.ti.com \
    --to=nsekhar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.