All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/4] ARM: imx: add initial support for MVF600
Date: Fri, 17 May 2013 15:17:31 +0200	[thread overview]
Message-ID: <4003326.AbobOukrYT@wuerfel> (raw)
In-Reply-To: <20130517130603.GJ8607@S2101-09.ap.freescale.net>

On Friday 17 May 2013 21:06:05 Shawn Guo wrote:
> On Fri, May 17, 2013 at 02:29:52PM +0200, Arnd Bergmann wrote:
> > > > Actually I think you should move that driver to drivers/clk and use
> > > > of_clk_init(NULL) to initialize it.
> > > > 
> > > The mvf600 clock driver uses a lot of base clk support from mach-imx,
> > > and can not be moved into drivers/clk as a single driver.  Right now, in
> > > IMX clock drivers, we call of_clk_init() to only register fixed rate
> > > clocks, since all the other clocks are not represented in device tree.
> > 
> > What are your plans for this in the long run?
> > 
> We can move all the IMX clock drivers into drivers/clk at some point
> when necessary.  But I do not have a plan to register all the clocks
> by merely calling of_clk_init(), because doing that would mean we have
> to represent all these clocks in device tree.  For imx6q example, it's
> about 200 ~ 300 nodes addition to DTB.  Device tree maintainers are
> against to the idea.  They are perfectly fine with having clock driver
> in kernel to represent/register these SoC internal clocks to clk
> framework.

Can't we move the driver to drivers/clk and have it initialized through
of_clk_init() without representing all clocks in the DT?

For all I can tell, CLK_OF_DECLARE() requires only the clock provider
to be described in DT, but not the actual clocks.

	Arnd

  reply	other threads:[~2013-05-17 13:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16  6:10 [PATCH v3 0/4] Add initial Freescale Vybrid MVF600 support Jingchang Lu
2013-05-16  6:10 ` [PATCH v3 1/4] ARM: imx: add MVF600 clock support Jingchang Lu
2013-05-16  6:10 ` [PATCH v3 2/4] ARM: imx: add initial support for MVF600 Jingchang Lu
2013-05-16 10:29   ` Arnd Bergmann
2013-05-17  8:57     ` Shawn Guo
2013-05-17 12:29       ` Arnd Bergmann
2013-05-17 12:31         ` Arnd Bergmann
2013-05-17 13:06         ` Shawn Guo
2013-05-17 13:17           ` Arnd Bergmann [this message]
2013-05-17 13:54             ` Shawn Guo
2013-05-21  2:17             ` Shawn Guo
2013-05-17  9:08   ` Shawn Guo
2013-05-18  1:27   ` Shawn Guo
2013-05-16  6:10 ` [PATCH v3 3/4] ARM: dts: add SoC level device tree source " Jingchang Lu
2013-05-19 14:14   ` Shawn Guo
2013-05-16  6:10 ` [PATCH v3 4/4] ARM: dts: add initial MVF600 Tower board dts support Jingchang Lu
2013-05-19 15:29   ` Shawn Guo
2013-05-20  5:01     ` Lu Jingchang-B35083
2013-05-20  5:53       ` Shawn Guo

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=4003326.AbobOukrYT@wuerfel \
    --to=arnd@arndb.de \
    --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.