On 3/8/2024 4:29 PM, Bryan O'Donoghue wrote:
On 08/03/2024 10:58, Bryan O'Donoghue wrote:
On 08/03/2024 10:46, Satya Priya Kakitapalli (Temp) wrote:
Not if you mark it critical
Marking the clock as critical keeps the associated power domain
always-on which impacts power. For this reason we are not using
CLK_IS_CRITICAL and instead making them always on from probe.
How does the clock do anything _useful_ if the power-domain gets
switched off ?
---
bod
i.e. the clock can't be running "always-on" if it has no power..
If BIT(0) is set from probe, during any active usecase, the clock gets
turned ON automatically when the power domain is turned ON.
But when we use CLK_IS_CRITICAL flag, the framework keeps the power
domain ON and doesn't let the power domain to turn off even when there
is no active usecase.
