From: jonas@microbit.se (Jonas Andersson)
To: linux-arm-kernel@lists.infradead.org
Subject: at91 clocks
Date: Thu, 26 Mar 2015 11:02:42 +0100 [thread overview]
Message-ID: <5513D942.7050307@microbit.se> (raw)
In-Reply-To: <20150325173751.0d6479df@bbrezillon>
Hi Boris and others,
>>>> Hi all,
>>>>
>>>> I am working on a system with at91sam9260 soc. Trying to move from
>>>> kernel 3.17.4 to 3.19.2. I have problem with pck1 clock.
>>>>
>>>> In my old code i use clk_get() to get pck1 and pllb, set pllb as parent
>>>> for pck1, set rate for pck1, enable pck1.
>>> How do you do that (clk_set_parent + clk_set_rate) ?
>>> Could you paste your code somewhere ?
>> Yes, seehttp://pastie.org/10052161
> Your pllb seems to be configured to output a 0Hz rate, and I'm not
> forwarding rate change to prog clk parents yet.
> That's definitely something I should work on, but in the meantime you
> could try to manually set pllb rate.
I tried to set pllb rate to 96MHz but it still shows 0Hz. |clk_set_rate
returns 0|.
>
>> I tried kernel 4.0-rc5 but it hangs in boot after ethernet init.
> Is this related to the changes I suggested ?
>
No, it doesnt work before changes. I will try to get it running later,
direct from linus tree without modifications..
Thanks for help.
Jonas
next prev parent reply other threads:[~2015-03-26 10:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 14:32 at91 clocks Jonas Andersson
2015-03-25 0:32 ` Boris Brezillon
2015-03-25 9:06 ` Jonas Andersson
2015-03-25 16:37 ` Boris Brezillon
2015-03-25 18:18 ` Nicolas Ferre
2015-03-27 9:28 ` Jonas Andersson
2015-03-27 9:48 ` Nicolas Ferre
2015-03-26 10:02 ` Jonas Andersson [this message]
[not found] ` <5513D701.2080201@microbit.se>
2015-03-26 15:28 ` Boris Brezillon
2015-03-27 10:21 ` Jonas Andersson
2015-03-27 12:20 ` Boris Brezillon
2015-03-27 12:25 ` Boris Brezillon
2015-03-27 12:51 ` Jonas Andersson
2015-03-27 13:54 ` Boris Brezillon
2015-03-27 14:42 ` Jonas Andersson
2015-03-30 11:24 ` Jonas Andersson
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=5513D942.7050307@microbit.se \
--to=jonas@microbit.se \
--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).