From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: prevent erronous parsing of children during rate change
Date: Wed, 17 Sep 2014 13:27:37 -0500 [thread overview]
Message-ID: <20140917182737.GF8140@saruman.home> (raw)
In-Reply-To: <20140903192203.11368.5520@quantum>
Hi Mike,
On Wed, Sep 03, 2014 at 12:22:03PM -0700, Mike Turquette wrote:
> Quoting Tero Kristo (2014-08-21 06:47:45)
> > In some cases, clocks can switch their parent with clk_set_rate, for
> > example clk_mux can do this in some cases. Current implementation of
> > clk_change_rate uses un-safe list iteration on the clock children, which
> > will cause wrong clocks to be parsed in case any of the clock children
> > change their parents during the change rate operation. Fixed by using
> > the safe list iterator instead.
> >
> > The problem was detected due to some divide by zero errors generated
> > by clock init on dra7-evm board, see discussion under
> > http://article.gmane.org/gmane.linux.ports.arm.kernel/349180 for details.
> >
> > Signed-off-by: Tero Kristo <t-kristo@ti.com>
> > To: Mike Turquette <mturquette@linaro.org>
> > Reported-by: Nishanth Menon <nm@ti.com>
>
> Applied to clk-fixes.
v3.17-rc5 and today's next still exhibit the same bug. Any chance we can
this fix into v3.17-final ?
--
balbi
-------------- 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/20140917/01cf6821/attachment.sig>
next prev parent reply other threads:[~2014-09-17 18:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 13:47 [PATCH] clk: prevent erronous parsing of children during rate change Tero Kristo
2014-08-21 13:59 ` Nishanth Menon
2014-09-03 19:22 ` Mike Turquette
2014-09-17 18:27 ` Felipe Balbi [this message]
2014-09-22 19:18 ` Stephen Boyd
2014-09-23 13:38 ` Tero Kristo
2014-09-26 1:35 ` Stephen Boyd
2014-09-26 7:18 ` Tero Kristo
2014-09-26 23:24 ` Mike Turquette
2014-09-29 8:09 ` Tero Kristo
2014-09-30 7:07 ` Mike Turquette
2014-09-30 8:48 ` Tero Kristo
2014-09-30 19:03 ` Mike Turquette
2014-10-02 13:31 ` Tero Kristo
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=20140917182737.GF8140@saruman.home \
--to=balbi@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;
as well as URLs for NNTP newsgroup(s).