linux-kernel - Re: [PATCH] clk: qcom: camcc-sc8280xp: Remove always-on GDSC hard-coding

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 for Android: free password hash cracker in your pocket

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

Message-ID: <dd588276-8f1c-4389-7b3a-88f483b7072e@quicinc.com>
Date: Fri, 19 Jul 2024 12:55:54 +0530
From: "Satya Priya Kakitapalli (Temp)" <quic_skakitap@...cinc.com>
To: Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
        Bjorn Andersson
	<andersson@...nel.org>,
        Michael Turquette <mturquette@...libre.com>,
        Stephen
 Boyd <sboyd@...nel.org>
CC: <dmitry.baryshkov@...aro.org>, <stable@...r.kernel.org>,
        <linux-arm-msm@...r.kernel.org>, <linux-clk@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] clk: qcom: camcc-sc8280xp: Remove always-on GDSC
 hard-coding


On 7/17/2024 4:41 PM, Bryan O'Donoghue wrote:
> On 17/07/2024 12:08, Satya Priya Kakitapalli (Temp) wrote:
>>> How would it break ?
>>>
>>> We park the clock to XO it never gets turned off this way.
>>>
>>
>> Parking the parent at XO doesn't ensure the branch clock is always 
>> on, it can be disabled by consumers or CCF if modelled.
>>
>> If the CCF disables this clock in late init, then the clock stays in 
>> disabled state until it is enabled again explicitly. Hence it is 
>> recommended to not model such always-on clocks.
>
> What is the use-case to keep that clock always-on unless/util someone 
> wants camss ?
>

The clock also has dependency on MMCX rail, this rail anyway will be OFF 
until there is a use-case. So the clock will also be OFF.


> I've tested this patch on sc8280xp and it works just fine.
>

Is the cam_cc_gdsc_clk clock ON after the boot up?


> ---
> bod