From: Stephen Boyd <sboyd@codeaurora.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Mike Turquette <mturquette@baylibre.com>,
Jongsung Kim <neidhard.kim@lge.com>, Chen-Yu Tsai <wens@csie.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] clk: fixed-factor: Allow for a few clocks to change the parent rate
Date: Fri, 1 Jul 2016 17:17:08 -0700 [thread overview]
Message-ID: <20160702001708.GE27880@codeaurora.org> (raw)
In-Reply-To: <20160622091555.18415-1-maxime.ripard@free-electrons.com>
On 06/22, Maxime Ripard wrote:
> The only way for a fixed factor clock to change its rate would be to change
> its parent rate.
>
> Since passing blindly CLK_SET_RATE_PARENT might break a lot of platforms
> that were relying on the fact that the parent rate wouldn't change,
> introduce a compatible-based whitelist that will allow clocks to opt-in
> that flag.
>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] clk: fixed-factor: Allow for a few clocks to change the parent rate
Date: Fri, 1 Jul 2016 17:17:08 -0700 [thread overview]
Message-ID: <20160702001708.GE27880@codeaurora.org> (raw)
In-Reply-To: <20160622091555.18415-1-maxime.ripard@free-electrons.com>
On 06/22, Maxime Ripard wrote:
> The only way for a fixed factor clock to change its rate would be to change
> its parent rate.
>
> Since passing blindly CLK_SET_RATE_PARENT might break a lot of platforms
> that were relying on the fact that the parent rate wouldn't change,
> introduce a compatible-based whitelist that will allow clocks to opt-in
> that flag.
>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-07-02 0:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 9:15 [PATCH 1/2] clk: fixed-factor: Allow for a few clocks to change the parent rate Maxime Ripard
2016-06-22 9:15 ` Maxime Ripard
2016-06-22 9:15 ` Maxime Ripard
2016-06-22 9:15 ` [PATCH 2/2] ARM: sun5i: Allow PLL3 2x fixed factor clock to change PLL3 rate Maxime Ripard
2016-06-22 9:15 ` Maxime Ripard
2016-06-22 9:15 ` Maxime Ripard
2016-06-24 4:43 ` [PATCH 1/2] clk: fixed-factor: Allow for a few clocks to change the parent rate Jongsung Kim
2016-06-24 4:43 ` Jongsung Kim
2016-06-24 15:52 ` Rob Herring
2016-06-24 15:52 ` Rob Herring
2016-07-02 0:17 ` Stephen Boyd [this message]
2016-07-02 0:17 ` Stephen Boyd
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=20160702001708.GE27880@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=mturquette@baylibre.com \
--cc=neidhard.kim@lge.com \
--cc=wens@csie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.