From: Georgi Djakov <georgi.djakov@linaro.org>
To: sboyd@codeaurora.org
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
georgi.djakov@linaro.org
Subject: [PATCH v4 0/4] Add support for more MSM8916 clocks
Date: Wed, 16 Sep 2015 16:24:44 +0300 [thread overview]
Message-ID: <1442409888-19917-1-git-send-email-georgi.djakov@linaro.org> (raw)
This patchset adds support for iommu, gpu and audio clocks on
the MSM8916 platforms.
Changes since v3 (https://lkml.org/lkml/2015/8/13/393)
* Use recalc_rate() to find current frequency when enabling
a shared branch clock and there is no cached frequency yet.
Changes since v2 (https://lkml.org/lkml/2015/6/5/324)
* Dropped patch for read-only RCGs as it is not needed.
* Updated RCGs with shared branches patch and addressed various issues
pointed by Stephen.
* Rebased on clk-next.
Changes since v1
* Added a set of ops for read-only RCGs and RCGs with shared branches.
Georgi Djakov (4):
clk: qcom: Add MSM8916 iommu clocks
clk: qcom: Add support for RCGs with shared branches
clk: qcom: Add MSM8916 gpu clocks
clk: qcom: Add MSM8916 audio clocks
drivers/clk/qcom/clk-rcg.h | 4 +-
drivers/clk/qcom/clk-rcg2.c | 78 ++++
drivers/clk/qcom/gcc-msm8916.c | 497 ++++++++++++++++++++++++++
include/dt-bindings/clock/qcom,gcc-msm8916.h | 22 ++
4 files changed, 600 insertions(+), 1 deletion(-)
next reply other threads:[~2015-09-16 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 13:24 Georgi Djakov [this message]
2015-09-16 13:24 ` [PATCH v4 1/4] clk: qcom: Add MSM8916 iommu clocks Georgi Djakov
2015-09-16 13:24 ` [PATCH v4 2/4] clk: qcom: Add support for RCGs with shared branches Georgi Djakov
2015-09-16 22:07 ` Stephen Boyd
2015-09-16 13:24 ` [PATCH v4 3/4] clk: qcom: Add MSM8916 gpu clocks Georgi Djakov
2015-09-16 13:24 ` [PATCH v4 4/4] clk: qcom: Add MSM8916 audio clocks Georgi Djakov
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=1442409888-19917-1-git-send-email-georgi.djakov@linaro.org \
--to=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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).