From: Afzal Mohammed <afzal.mohd.ma@gmail.com>
To: Daniel Mack <zonque@gmail.com>
Cc: Fabio Estevam <festevam@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Mike Turquette <mturquette@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Question about fixed-clock
Date: Fri, 8 Mar 2013 00:12:41 +0530 [thread overview]
Message-ID: <20130307184240.GA3327@afzal-ThinkPad-R50e> (raw)
In-Reply-To: <20130219033931.GA2479@afzal-ThinkPad-R50e> <51234B8E.2000504@gmail.com>
Hi Daniel,
On Tue, Feb 19, 2013 at 09:09:31AM +0530, Afzal Mohammed wrote:
> Hope invoking of_clk_init before clock generator driver helps
Mails coming from this id are in my personal capacity.
On Tue, Feb 19, 2013 at 10:53:18AM +0100, Daniel Mack wrote:
> On 19.02.2013 02:33, Fabio Estevam wrote:
> > Have you registered it with clk_register_fixed_rate() ?
> Hmm no, I didn't do anything else than adding it to the DT in the first
> place, hoping that a driver will pick it up and add the clock for me.
> But it turns out that of_clk_init() is not called at all on my platform.
>
> I'm doing this now from omap_generic_init() and it works. If that's an
> appropriate place to call it, I can provide a patch.
Initially didn't realize that it was for an am335x based one.
I feel that for a platform having it's clock tree in DT, of_clk_init
would take care of it, but if clock tree data is not in DT, clock
tree would have to be extended in a non-DT way.
Regards
Afzal
next prev parent reply other threads:[~2013-03-07 18:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 23:55 Question about fixed-clock Daniel Mack
2013-02-19 0:07 ` Daniel Mack
2013-02-19 1:33 ` Fabio Estevam
2013-02-19 9:53 ` Daniel Mack
[not found] ` <20130219172246.11471.14635@quantum>
2013-02-19 17:32 ` Daniel Mack
2013-03-02 14:09 ` Daniel Mack
2013-03-07 18:42 ` Afzal Mohammed [this message]
2013-03-07 22:31 ` Daniel Mack
2013-03-08 2:15 ` Mark Brown
2013-03-08 13:30 ` Daniel Mack
2013-03-09 8:26 ` Sebastian Hesselbarth
2013-03-12 18:40 ` Mark Brown
2013-02-19 3:39 ` Afzal Mohammed
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=20130307184240.GA3327@afzal-ThinkPad-R50e \
--to=afzal.mohd.ma@gmail.com \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@linaro.org \
--cc=zonque@gmail.com \
/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