From: Sascha Hauer <s.hauer@pengutronix.de>
To: Abel Vesa <abel.vesa@nxp.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Lucas Stach <l.stach@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Aisheng Dong <aisheng.dong@nxp.com>, Jacky Bai <ping.bai@nxp.com>,
Anson Huang <anson.huang@nxp.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC] clk: imx: Allow re-parenting by default on set rate
Date: Wed, 13 Mar 2019 11:41:49 +0100 [thread overview]
Message-ID: <20190313104149.blhwqgn53lsgow6z@pengutronix.de> (raw)
In-Reply-To: <20190311104140.n65jvamx76rzkonr@fsr-ub1664-175>
On Mon, Mar 11, 2019 at 10:41:40AM +0000, Abel Vesa wrote:
> On 19-03-11 11:28:25, Sascha Hauer wrote:
> > Hi Abel,
> >
> > On Thu, Mar 07, 2019 at 09:20:37AM +0000, Abel Vesa wrote:
> > > By default, the muxes should re-parent on set_rate.
> > > This would allow the drivers to control only the leaf clock node,
> > > leaving the rest to the clock driver, that way simplifying the
> > > clock control.
> >
> > I am afraid of this change. Besides the rate there might be other
> > reasons to choose one mux input over another, consider for example low
> > power audio playback where we need one specific mux setting because it
> > provides a clock which runs at low power mode.
> > On the IPU on i.MX5/6 there are clocks being used as pixel clocks
> > derived from different muxes. I don't think you want to pick an input
> > clock just because it happens to deliver the best clock rate at that
> > point in time, but really is shared with some other clock that changes
> > its rate in the next moment.
> >
>
> > I have no concrete examples for things that break with this change, but
> > I would be more confident if we change the behaviour explicitly only for
> > the muxes that we have reviewed to cope with this change.
> >
>
> Fair enough. We could replace all the imx_clk_mux with imx_clk_mux_noreparent
> and after that we can independently switch the clocks that are safe (to switch)
> to imx_clk_mux (which would not have the noreparent flag set).
Ok with me.
>
> The main idea is to simplify the clock control from drivers point of view.
Which drivers do you have in mind? I hardly ever missed reparenting on
rate changes, so where is this feature useful?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2019-03-13 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 9:20 Abel Vesa
2019-03-11 10:28 ` Sascha Hauer
2019-03-11 10:41 ` Abel Vesa
2019-03-13 10:41 ` Sascha Hauer [this message]
2019-03-13 11:29 ` Daniel Baluta
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=20190313104149.blhwqgn53lsgow6z@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=anson.huang@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=ping.bai@nxp.com \
--cc=sboyd@kernel.org \
--cc=shawnguo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®