All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: "Daniel Glöckner" <daniel-gl@gmx.net>
Cc: <linux-clk@vger.kernel.org>
Subject: Re: Bits that affect several muxes
Date: Tue, 26 Jan 2016 10:22:15 +0200	[thread overview]
Message-ID: <56A72CB7.7050707@mentor.com> (raw)
In-Reply-To: <20160122233737.GA15679@minime.bse>

Hi Daniel,

On 23.01.2016 01:37, Daniel Glöckner wrote:
> Hi,
> 
> today at work I just realized that the i.MX6 clock tree is not correctly
> modeled wrt. PLL bypassing since bypassing the PLL also bypasses all PFD
> post dividers. I've seen this before on the jz4730 where disabling the
> PLL also sets several clocks to the same source.

could you please give a more detailed example for iMX6 (particular clock
names, registers, bit fields from the Reference Manual)?

> Maybe I haven't dug deep enough into the mail archive, but I couldn't
> find any information on how to handle cases like these. Can this be
> modeled with the existing clock primitives?

I believe I met something similar (one bit control, which changes several
muxes or gates), and practically I found that in read-only muxes case this
can be handled by registering several such muxes with the same hardware
controls (same mux register, bit shift and mask) but different list of
parents, which are specific to every particular mux. And CCF is not yet
ready to correctly process clk_set_parent() calls on such kind of muxes.

Best wishes,
Vladimir


  reply	other threads:[~2016-01-26  8:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 23:37 Bits that affect several muxes Daniel Glöckner
2016-01-26  8:22 ` Vladimir Zapolskiy [this message]
2016-01-27  2:32   ` Daniel Glöckner

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=56A72CB7.7050707@mentor.com \
    --to=vladimir_zapolskiy@mentor.com \
    --cc=daniel-gl@gmx.net \
    --cc=linux-clk@vger.kernel.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.