From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1] clk: Add clk_composite_set_rate_and_parent
Date: Wed, 13 Apr 2016 17:43:31 -0700 [thread overview]
Message-ID: <20160414004331.GK14441@codeaurora.org> (raw)
In-Reply-To: <3986787.PS6VzOpSAJ@phil>
On 04/12, Heiko Stuebner wrote:
>
> I remember having clocks not overflow their target rate came up in some ELC
> talk last week (probably in Stephens Qualcomm-kernel-talk) and a general
> solution might need some changes closer to the core.
Yep. It's on the list. Hopefully coordinated clk rate changes
will help here. Composite clks are sort of already coordinated
rates in a minor form though.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-04-14 0:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 1:54 [PATCH v1] clk: Add clk_composite_set_rate_and_parent Finlye Xiao
2016-04-12 5:04 ` Heiko Stuebner
2016-04-14 0:43 ` Stephen Boyd [this message]
2016-04-14 4:56 ` Heiko Stübner
2016-04-12 8:43 ` [PATCH v2] " Finlye Xiao
2016-04-15 22:15 ` 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=20160414004331.GK14441@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).