From: Heiko Stuebner <heiko@sntech.de>
To: mturquette@baylibre.com, sboyd@codeaurora.org
Cc: linux-clk@vger.kernel.org, linux-rockchip@lists.infradead.org,
zhengxing@rock-chips.com, zhangqing@rock-chips.com,
tomeu.vizoso@collabora.com, Heiko Stuebner <heiko@sntech.de>
Subject: [RFC PATCH 0/3] clk: attempt to keep requested rate on parent changes
Date: Mon, 2 May 2016 18:36:19 +0200 [thread overview]
Message-ID: <1462206982-10444-1-git-send-email-heiko@sntech.de> (raw)
I remember reading about people discussing that problem in the past, but
haven't been able to find another approach to it yet [or I'm just blind
as happens to often].
Our problem is the following clock structure:
[anotherPLL]
|
------ [div] ----- dclk_vop
|
[ vpll ] --------- hdmi_phy
We need to set the vpll dynamically but still want to retain
The other option that comes to mind, would be to have a clock-notifier,
in the drm driver, but calling clk_set_rate from their looks like it
shouldn't work due to the prepare mutex already being held.
The whole thing is labeled RFC because while it works for us and solves
the problem, I'm not sure if I'm overlooking some important aspect or
am interferring with some other planned approach for that issue.
Heiko Stuebner (3):
clk: fix inconsistent use of req_rate
clk: adjust clocks to their requested rate after parent changes
clk: rockchip: make rk3399 vop dclks keep their rate on parent rate changes
drivers/clk/clk.c | 37 +++++++++++++++++++++++++++++--------
drivers/clk/rockchip/clk-rk3399.c | 4 ++--
include/linux/clk-provider.h | 1 +
3 files changed, 32 insertions(+), 10 deletions(-)
--
2.8.0.rc3
next reply other threads:[~2016-05-02 16:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 16:36 Heiko Stuebner [this message]
2016-05-02 16:36 ` [RFC PATCH 1/3] clk: fix inconsistent use of req_rate Heiko Stuebner
2016-05-02 16:36 ` [RFC PATCH 2/3] clk: adjust clocks to their requested rate after parent changes Heiko Stuebner
2016-05-06 0:35 ` Doug Anderson
2016-05-06 0:49 ` Doug Anderson
2016-05-06 0:49 ` Doug Anderson
2016-05-08 20:34 ` Heiko Stuebner
2016-05-09 11:40 ` Heiko Stuebner
2016-05-09 15:49 ` Doug Anderson
2016-05-09 15:49 ` Doug Anderson
2016-07-05 7:27 ` Elaine Zhang
2016-07-05 7:27 ` Elaine Zhang
2016-07-05 22:24 ` Heiko Stuebner
2016-07-05 22:24 ` Heiko Stuebner
2016-07-06 1:39 ` Elaine Zhang
2016-07-06 23:01 ` Doug Anderson
2016-07-06 23:01 ` Doug Anderson
2016-07-06 22:41 ` Doug Anderson
2016-05-02 16:36 ` [RFC PATCH 3/3] clk: rockchip: make rk3399 vop dclks keep their rate on parent rate changes Heiko Stuebner
2016-05-05 13:30 ` [RFC PATCH 0/3] clk: attempt to keep requested rate on parent changes Tomeu Vizoso
2016-05-05 15:07 ` Heiko Stübner
2016-05-06 0:46 ` Doug Anderson
2016-05-06 0:46 ` Doug Anderson
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=1462206982-10444-1-git-send-email-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=tomeu.vizoso@collabora.com \
--cc=zhangqing@rock-chips.com \
--cc=zhengxing@rock-chips.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 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.