public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mturquette@ti.com (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: possibility of parent clock selection through DT
Date: Mon, 12 Nov 2012 13:22:12 -0800	[thread overview]
Message-ID: <20121112212212.20034.78522@nucleus> (raw)
In-Reply-To: <CAPub148Bq=uwTuky25WzXn4yfCukJ+WacxkBvuyV5yTzGasGOQ@mail.gmail.com>

Quoting Shiraz Hashim (2012-11-06 22:36:10)
> On Wed, Nov 7, 2012 at 11:42 AM, Shiraz Hashim
> <shiraz.linux.kernel@gmail.com> wrote:
> > Hi Mike, Rob,
> >
> > Devices in a SoC can have multiple possible clock sources which is
> > perfectly captured through clk framework.
> >
> > But the device itself may not be aware of the complex hierarchy above it.
> > In this case how do you suggest a board (through DT) should select its
> > preference.
> >
> > Is there some work already going on in this direction ?
> 
> Just to make it clear, I already have referred the clock DT bindings and
> Shawn Guo patch on removing clk look up registration from kernel code.
> 
> Here I am talking about possibility of selecting desired clock hierarchy
> by the boards about which device nodes are not aware.
> 

One way to achieve this is to use clk_set_rate as a way to switch
parents at run-time.  The OMAP CCF code currently does this when
relocking PLLs and makes use of __clk_reparent to update the clock
framework's representation of the hierarchy dynamically.

Maybe something like the following is helpful to you:
http://git.linaro.org/gitweb?p=people/mturquette/linux.git;a=blob;f=arch/arm/mach-omap2/dpll3xxx.c;h=f72dedb4eee892ce4cd5bdf22cc8c22510f3d526;hb=clk-omap-3.8#l542

Regards,
Mike

> -- 
> regards
> Shiraz Hashim

  reply	other threads:[~2012-11-12 21:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07  6:12 possibility of parent clock selection through DT Shiraz Hashim
2012-11-07  6:36 ` Shiraz Hashim
2012-11-12 21:22   ` Mike Turquette [this message]
2012-11-18  4:14     ` Shiraz Hashim

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=20121112212212.20034.78522@nucleus \
    --to=mturquette@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox