From: Stephen Boyd <sboyd@codeaurora.org>
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: mturquette@linaro.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/3] clk: qcom: Add MSM8916 iommu clocks
Date: Wed, 13 May 2015 10:53:12 -0700 [thread overview]
Message-ID: <55538F88.2060502@codeaurora.org> (raw)
In-Reply-To: <55537F93.2000101@linaro.org>
On 05/13/15 09:45, Georgi Djakov wrote:
> On 05/13/2015 10:36 AM, Stephen Boyd wrote:
>> On 05/12, Georgi Djakov wrote:
>>> Add support for the msm8916 TCU clocks that are needed for IOMMU.
>>>
>>> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
>>> ---
>> Applied to clk-next
>>
> Hi Stephen,
> Just got a report that this patch has some issues - gcc_bimc_clk
> may get disabled by the CCF, which turns out to be not good.
> So I am going to remove it from the chain leaving only the
> bimc_ddr_clk_src as the parent of apss_tcu and gfx_tcu clocks.
> Will re-send this series soon. Apologies for the extra work.
>
Ah right. You should also remove ftbl_bimc_ddr_clk and turn the
bimc_ddr_clk_src clock into a read-only rcg. It's unfortunate that we
have to do tricks like this because of hardware sharing with the RPM.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-05-13 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 11:00 [PATCH 1/3] clk: qcom: Add MSM8916 iommu clocks Georgi Djakov
2015-05-12 11:00 ` [PATCH 2/3] clk: qcom: Add MSM8916 gpu clocks Georgi Djakov
2015-05-13 7:36 ` Stephen Boyd
2015-05-12 11:00 ` [PATCH 3/3] clk: qcom: Add MSM8916 audio clocks Georgi Djakov
2015-05-13 7:36 ` Stephen Boyd
2015-05-13 7:36 ` [PATCH 1/3] clk: qcom: Add MSM8916 iommu clocks Stephen Boyd
2015-05-13 16:45 ` Georgi Djakov
2015-05-13 17:53 ` Stephen Boyd [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=55538F88.2060502@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=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@linaro.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).