All of lore.kernel.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: Mon, 1 Feb 2016 15:45:48 +0100	[thread overview]
Message-ID: <20160201144548.GD4652@lukather> (raw)
In-Reply-To: <CAGb2v67AC+KO9mebyTosxSig7SzYm4Ovr5vCpEsX5N7YadJ-hw@mail.gmail.com>

On Mon, Feb 01, 2016 at 10:37:45PM +0800, Chen-Yu Tsai wrote:
> >> There is, but it's opt-in, and we're not using it yet for anything but
> >> the hstimers (and in that case, we don't prevent the reclocking, we
> >> just take it into account).
> >
> > Shouldn't we be opt-ing in then ? At least the mmc driver makes
> > clk_set_rate calls, it would be bad if that somehow ends up changing the
> > pll6 rate while other peripherals are using it.
> 
> The mod clocks do not have CLK_SET_RATE_PARENT set, which prevents the
> CCF from propagating clk_set_rate to its parent. As is for the other
> child clocks of PLL6. The only exception is the SATA clock in PLL6.

The PLL6 you're talking about is not the PLL6 we're talking about ;)

We're talking about the A31's, while the SATA on the A10 / A20 is
driven by the A10's (the equivalent for the A10 would be the PLL5)

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/20160201/3321040e/attachment.sig>

  reply	other threads:[~2016-02-01 14:45 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
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 [this message]
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=20160201144548.GD4652@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.