linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: at91 clocks
Date: Wed, 25 Mar 2015 19:18:19 +0100	[thread overview]
Message-ID: <5512FBEB.2060609@atmel.com> (raw)
In-Reply-To: <20150325173751.0d6479df@bbrezillon>

Le 25/03/2015 17:37, Boris Brezillon a ?crit :
> Hi Jonas,
> 
> On Wed, 25 Mar 2015 10:06:46 +0100
> Jonas Andersson <jonas@microbit.se> wrote:
> 
>> Hi Boris and others,
>>
>> On 2015-03-25 01:32, Boris Brezillon wrote:
>>> Hi Jonas,
>>>
>>> On Tue, 24 Mar 2015 15:32:08 +0100
>>> Jonas Andersson <jonas@microbit.se> wrote:
>>>
>>>> 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, see http://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.
> 
>>
>>>
>>>> Extract from
>>>> /sys/kernel/debug/at91_clk:
>>>> pllb       users= 1 on   96000000 Hz main
>>>> pck1       users= 1 on   12000000 Hz pllb
>>>>
>>> With the new implementation calling clk_set_rate(pck1, 120000000)
>>> should do the job: it should choose the best parent clk and divisor.
>>
>> Ok thank you for that information. I tried that now (new code in link 
>> above), and i got a clock output but not exactly my wanted 12MHz. I 
>> measure 9.216MHz at pck1 output.
>>
>>         mainck                             2            2 
>> 18432000          0 0
>>            prog1                           1            1 
>> 9216000          0 0
>>               pck1                         1            1 
>> 9216000          0 0
>>
>> pllbck is still unused.
>>
>> I tried kernel 4.0-rc5 but it hangs in boot after ethernet init.
> 
> Is this related to the changes I suggested ?

It seems to be related as I tried to boot an at91sam9260ek with current
Linus' tree and it doesn't hangs after Ethernet on my side...

Bye,
-- 
Nicolas Ferre

  reply	other threads:[~2015-03-25 18:18 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 [this message]
2015-03-27  9:28         ` Jonas Andersson
2015-03-27  9:48           ` Nicolas Ferre
2015-03-26 10:02       ` Jonas Andersson
     [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=5512FBEB.2060609@atmel.com \
    --to=nicolas.ferre@atmel.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;
as well as URLs for NNTP newsgroup(s).