From: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
To: "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Cc: "wsa+renesas@sang-engineering.com"
<wsa+renesas@sang-engineering.com>,
"jsarha@ti.com" <jsarha@ti.com>,
"horms@verge.net.au" <horms@verge.net.au>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"magnus.damm@gmail.com" <magnus.damm@gmail.com>,
"ce3a@gmx.de" <ce3a@gmx.de>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"geert+renesas@glider.be" <geert+renesas@glider.be>
Subject: Re: [PATCH v3] clk: clk-gpio: propagate rate change to parent
Date: Mon, 11 Nov 2019 09:31:15 +0000 [thread overview]
Message-ID: <f219739b465f32d0f1b8fe75c137581a44257744.camel@analog.com> (raw)
In-Reply-To: <20191108210854.95C8C20869@mail.kernel.org>
On Fri, 2019-11-08 at 13:08 -0800, Stephen Boyd wrote:
> Quoting Alexandru Ardelean (2019-11-07 23:17:18)
> > From: Michael Hennerich <michael.hennerich@analog.com>
> >
> > For an external clock source, which is gated via a GPIO, the
> > rate change should typically be propagated to the parent clock.
> >
> > The situation where we are requiring this propagation, is when an
> > external clock is connected to override an internal clock (which
> > typically
> > has a fixed rate). The external clock can have a different rate than
> > the
> > internal one, and may also be variable, thus requiring the rate
> > propagation.
> >
> > This rate change wasn't propagated until now, and it's unclear about
> > cases
> > where this shouldn't be propagated. Thus, it's unclear whether this is
> > fixing a bug, or extending the current driver behavior. Also, it's
> > unsure
> > about whether this may break any existing setups; in the case that it
> > does,
> > a device-tree property may be added to disable this flag.
> >
> > Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
> > Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
> > ---
>
> Applied to clk-next
>
> Next time please send as a new topic instead of a reply to the original
> patch. Makes it easier for me to apply the patch.
>
Ack.
Will do that.
Thanks
Alex
prev parent reply other threads:[~2019-11-11 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 11:35 [PATCH] clk: clk-gpio: Add dt option to propagate rate change to parent Alexandru Ardelean
2019-11-06 22:43 ` Stephen Boyd
2019-11-07 13:25 ` Ardelean, Alexandru
[not found] ` <20191107225313.4ED9D21D7B@mail.kernel.org>
2019-11-08 6:50 ` Ardelean, Alexandru
2019-11-08 7:10 ` Ardelean, Alexandru
2019-11-08 7:09 ` [PATCH v2] clk: clk-gpio: " Alexandru Ardelean
2019-11-08 7:17 ` [PATCH v3] " Alexandru Ardelean
2019-11-08 21:08 ` Stephen Boyd
2019-11-11 9:31 ` Ardelean, Alexandru [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=f219739b465f32d0f1b8fe75c137581a44257744.camel@analog.com \
--to=alexandru.ardelean@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=ce3a@gmx.de \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=jsarha@ti.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=wsa+renesas@sang-engineering.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).