public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Problem with Allwinner H3 clocks
Date: Thu, 28 Jan 2016 20:29:31 +0100	[thread overview]
Message-ID: <20160128192931.GB32462@lukather> (raw)
In-Reply-To: <20160128175918.78a916a8cd7bf4c0b2f2814f@free.fr>

On Thu, Jan 28, 2016 at 05:59:18PM +0100, Jean-Francois Moine wrote:
> On Thu, 28 Jan 2016 14:16:26 +0100
> Jens Kuske <jenskuske@gmail.com> wrote:
> 
> > after figuring out how to boot a devicetree kernel with allwinner's
> > u-boot I only had to add the mandatory
> > 	
> > 	clock-frequency = <24000000>;
> > 	arm,cpu-registers-not-fw-configured;
> > 
> > to the timer node and v4.5-rc1 booted successfully. They are
> > intentionally left out in the official dt, because documentation says
> > one should prefer to fix the firmware -> mainline u-boot
> > No problems with clocks or uart here.
> 
> You are right, I had these lines in my DT. Thanks.

And even though you had these lines, it was still not working? Or is
it working now? I'm confused.

> But, now, what about the PLL8 (periph1) which should be used by the MMCs?

I just sent another version of the pll6 rework to enable it.

> The A23/A33/H3 (and surely some other SoCs) documentations about
> the peripheral/periph/periph0/periph1 PLLs say:
> 
> 	Note: The PLL Output should be fixed to 600MHz, it is not
> 	recommended to vary this value arbitrarily.

I don't know if it's worth it at this point. The pll6 seems to work
fine at other rates. Have you experienced any breakage when running at
another frequency?

Thanks!
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160128/99968045/attachment.sig>

  reply	other threads:[~2016-01-28 19:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27  7:46 Problem with Allwinner H3 clocks Jean-Francois Moine
2016-01-27  8:18 ` [linux-sunxi] " Chen-Yu Tsai
2016-01-27  9:37   ` Jean-Francois Moine
2016-01-27 14:36     ` Jens Kuske
2016-01-27 16:55       ` Jean-Francois Moine
2016-01-27 18:16         ` Hans de Goede
2016-01-27 19:02           ` Jean-Francois Moine
2016-01-28  8:15             ` Hans de Goede
2016-01-28 13:16               ` Jens Kuske
2016-01-28 16:59                 ` Jean-Francois Moine
2016-01-28 19:29                   ` Maxime Ripard [this message]
2016-01-29  6:25                     ` Hans de Goede
2016-01-29  7:59                       ` Chen-Yu Tsai
2016-02-01  6:37                       ` Maxime Ripard
2016-02-01 14:26                         ` Hans de Goede
2016-02-01 14:37                           ` Chen-Yu Tsai
2016-02-01 14:45                             ` Maxime Ripard
2016-02-01 14:47                           ` Maxime Ripard
2016-01-29  7:27                     ` Jean-Francois Moine
2016-01-28 15:51               ` Jean-Francois Moine
2016-01-28 17:31               ` Maxime Ripard

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=20160128192931.GB32462@lukather \
    --to=maxime.ripard@free-electrons.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