From: bob.dunlop@xyzzy.org.uk (Bob Dunlop)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] davinci: dm6467/T EVM: pass reference clock rate to dm646x_init()
Date: Tue, 7 Jun 2011 08:41:45 +0100 [thread overview]
Message-ID: <20110607074145.GA6593@xyzzy.org.uk> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593024D383514@dbde02.ent.ti.com>
On Mon, Jun 06 at 06:32, Nori, Sekhar wrote:
...
> > 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.
Okay let's drop this idea. I must admit I was concerned about opening
up the structure availability.
--
Bob Dunlop
prev parent reply other threads:[~2011-06-07 7:41 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
2011-06-07 7:41 ` Bob Dunlop [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=20110607074145.GA6593@xyzzy.org.uk \
--to=bob.dunlop@xyzzy.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).