From: Felipe Balbi <balbi@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>, Paul Walmsley <paul@pwsan.com>,
Mike Turquette <mturquette@linaro.org>,
linux-omap@vger.kernel.org, Nishanth Menon <nm@ti.com>,
Felipe Balbi <balbi@ti.com>
Subject: Re: [RFC PATCH] clk: ti: set CLK_SET_RATE_NO_REPARENT for ti,mux-clock
Date: Tue, 17 Jun 2014 08:23:13 -0500 [thread overview]
Message-ID: <20140617132313.GC9070@saruman.home> (raw)
In-Reply-To: <1402992272-21413-2-git-send-email-tomi.valkeinen@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
On Tue, Jun 17, 2014 at 11:04:32AM +0300, Tomi Valkeinen wrote:
> When setting the rate of a clock, by default the clock framework will
> change the parent of the clock to the most suitable one in
> __clk_mux_determine_rate() (most suitable by looking at the clock rate).
>
> This is a rather dangerous default, and causes problems on AM43x when
> using display and ethernet. There are multiple ways to select the clock
> muxes on AM43x, and some of those clock paths have the same source
> clocks for display and ethernet. When changing the clock rate for the
> display subsystem, the clock framework decides to change the display mux
> from the dedicated display PLL to a shared PLL which is used by the
> ethernet, and then changes the rate of the shared PLL, breaking the
> ethernet.
>
> As I don't think there ever is a case where we want the clock framework
> to automatically change the parent clock of a clock mux, this patch sets
> the CLK_SET_RATE_NO_REPARENT for all ti,mux-clocks.
>
> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
am437x-sk presents no problem with this patch:
Tested-by: Felipe Balbi <balbi@ti.com>
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-06-17 13:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 8:04 [RFC PATCH] clk: ti: CLK_SET_RATE_NO_REPARENT for ti,mux-clock Tomi Valkeinen
2014-06-17 8:04 ` [RFC PATCH] clk: ti: set " Tomi Valkeinen
2014-06-17 8:11 ` Tero Kristo
2014-06-17 8:19 ` Paul Walmsley
2014-06-17 8:23 ` Tero Kristo
2014-06-17 21:08 ` Mike Turquette
2014-06-18 6:33 ` Paul Walmsley
2014-06-17 8:15 ` Paul Walmsley
2014-06-17 21:34 ` Mike Turquette
2014-06-18 6:57 ` Paul Walmsley
2014-06-18 7:06 ` Paul Walmsley
2014-06-17 13:23 ` Felipe Balbi [this message]
2014-06-19 11:33 ` Tero Kristo
2014-07-01 19:48 ` Felipe Balbi
2014-07-03 7:41 ` Tero Kristo
2014-07-03 22:06 ` Mike Turquette
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=20140617132313.GC9070@saruman.home \
--to=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=t-kristo@ti.com \
--cc=tomi.valkeinen@ti.com \
/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).