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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




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




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux