linux-kernel - Re: [PATCH 1/3] clk: qcom: Add MSM8916 iommu clocks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <55538F88.2060502@codeaurora.org>
Date:	Wed, 13 May 2015 10:53:12 -0700
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Georgi Djakov <georgi.djakov@...aro.org>
CC:	mturquette@...aro.org, linux-clk@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH 1/3] clk: qcom: Add MSM8916 iommu clocks

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@...aro.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/