public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mturquette@ti.com (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM : CLK: Fix clock multiplexers when registered before their parents.
Date: Mon, 26 Nov 2012 09:52:56 -0800	[thread overview]
Message-ID: <20121126175256.21126.7989@nucleus> (raw)
In-Reply-To: <20121122191505.18016.25951.stgit@localhost>

Quoting Martin Fuzzey (2012-11-22 11:15:05)
> When a clock, C is initialised any orphan clocks listing C as
> a possible parent are reparented to it regardless of the
> parent requested by the orphan's get_parent() operation.
> 
> This means that multiplexers registered before their parents
> are reparented to the first parent subsequently declared,
> regardless of the selection made by the hardware registers.
> 
> For example:
>         static const char *sel[] = { "srcA", "srcB", "dummy", "srcC" };
> 
>         child = clk_register_mux(NULL, "child",  sel, ARRAY_SIZE(sel), ...);
>         clk_register_fixed(NULL, "dummy", ...);
>         clk_register_fixed(NULL, "srcA", ...);
>         clk_register_fixed(NULL, "srcB", ...);
>         clk_register_fixed(NULL, "srcC", ...);
> 
> Causes child's parent to always be "dummy".
> 
> To fix this, when an orphanned clock has a get_parent() operation,
> only reparent to the clock indicated by get_parent().
> 
> Signed-off-by: Martin Fuzzey <mfuzzey@parkeon.com>

Thank you for the fix Martin.  This one got lost in the "todo" pile a
long time ago since most platforms register their clocks in-order from
root nodes to leaf nodes.

Applied to clk-next.

Regards,
Mike

> ---
>  drivers/clk/clk.c |   10 +++++++++-
>  1 files changed, 9 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
> index aae7b99..4c605ea 100644
> --- a/drivers/clk/clk.c
> +++ b/drivers/clk/clk.c
> @@ -1307,12 +1307,20 @@ int __clk_init(struct device *dev, struct clk *clk)
>          * walk the list of orphan clocks and reparent any that are children of
>          * this clock
>          */
> -       hlist_for_each_entry_safe(orphan, tmp, tmp2, &clk_orphan_list, child_node)
> +       hlist_for_each_entry_safe(orphan, tmp, tmp2, &clk_orphan_list, child_node) {
> +               if (orphan->ops->get_parent) {
> +                       i = orphan->ops->get_parent(orphan->hw);
> +                       if (!strcmp(clk->name, orphan->parent_names[i]))
> +                               __clk_reparent(orphan, clk);
> +                       continue;
> +               }
> +
>                 for (i = 0; i < orphan->num_parents; i++)
>                         if (!strcmp(clk->name, orphan->parent_names[i])) {
>                                 __clk_reparent(orphan, clk);
>                                 break;
>                         }
> +        }
>  
>         /*
>          * optional platform-specific magic

      reply	other threads:[~2012-11-26 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 19:15 [PATCH] ARM : CLK: Fix clock multiplexers when registered before their parents Martin Fuzzey
2012-11-26 17:52 ` Mike Turquette [this message]

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=20121126175256.21126.7989@nucleus \
    --to=mturquette@ti.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