* Re: possibility of parent clock selection through DT
[not found] <CAPub14-CPS48gQ1h8vvAYBpO_=egjheG_rMoZ894Y4XZ2CinUQ@mail.gmail.com>
@ 2012-11-07 6:36 ` Shiraz Hashim
[not found] ` <CAPub148Bq=uwTuky25WzXn4yfCukJ+WacxkBvuyV5yTzGasGOQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
0 siblings, 1 reply; 3+ messages in thread
From: Shiraz Hashim @ 2012-11-07 6:36 UTC (permalink / raw)
To: Mike Turquette, Rob Herring
Cc: linux-arm-kernel, linux-kernel, Viresh Kumar, devicetree-discuss
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.
--
regards
Shiraz Hashim
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: possibility of parent clock selection through DT
[not found] ` <CAPub148Bq=uwTuky25WzXn4yfCukJ+WacxkBvuyV5yTzGasGOQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2012-11-12 21:22 ` Mike Turquette
2012-11-18 4:14 ` Shiraz Hashim
0 siblings, 1 reply; 3+ messages in thread
From: Mike Turquette @ 2012-11-12 21:22 UTC (permalink / raw)
To: Shiraz Hashim, Rob Herring
Cc: Viresh Kumar, devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
Quoting Shiraz Hashim (2012-11-06 22:36:10)
> On Wed, Nov 7, 2012 at 11:42 AM, Shiraz Hashim
> <shiraz.linux.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: possibility of parent clock selection through DT
2012-11-12 21:22 ` Mike Turquette
@ 2012-11-18 4:14 ` Shiraz Hashim
0 siblings, 0 replies; 3+ messages in thread
From: Shiraz Hashim @ 2012-11-18 4:14 UTC (permalink / raw)
To: Mike Turquette
Cc: Viresh Kumar, devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r, Rob Herring,
linux-kernel-u79uwXL29TY76Z2rM5mHXA
Hi Mike,
On Tue, Nov 13, 2012 at 2:52 AM, Mike Turquette <mturquette-l0cyMroinI0@public.gmane.org> wrote:
> Quoting Shiraz Hashim (2012-11-06 22:36:10)
>> On Wed, Nov 7, 2012 at 11:42 AM, Shiraz Hashim
>> <shiraz.linux.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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
Thanks for the information.
So the generic SoC part can be handled through set_rate but
what about boards preferences and restrictions. For e.g., it prefers
to route a clock from a particular clk source only and wants its own
fixed (as per its design) clk source selections.
--
regards
Shiraz Hashim
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-11-18 4:14 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAPub14-CPS48gQ1h8vvAYBpO_=egjheG_rMoZ894Y4XZ2CinUQ@mail.gmail.com>
2012-11-07 6:36 ` possibility of parent clock selection through DT Shiraz Hashim
[not found] ` <CAPub148Bq=uwTuky25WzXn4yfCukJ+WacxkBvuyV5yTzGasGOQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-11-12 21:22 ` Mike Turquette
2012-11-18 4:14 ` Shiraz Hashim
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).