01.10.2021 15:32, Ulf Hansson пишет:
>> +static __maybe_unused int tegra_clock_pm_suspend(struct device *dev)
>> +{
>> + struct tegra_clk_device *clk_dev = dev_get_drvdata(dev);
>> +
>> + /*
>> + * Power management of the clock is entangled with the Tegra PMC
>> + * GENPD because PMC driver enables/disables clocks for toggling
>> + * of the PD's on/off state.
>> + *
>> + * The PMC GENPD is resumed in NOIRQ phase, before RPM of the clocks
>> + * becomes available, hence PMC can't use clocks at the early resume
>> + * phase if RPM is involved. For example when 3d clock is enabled,
>> + * it may enable the parent PLL clock that needs to be RPM-resumed.
>> + *
>> + * Secondly, the PLL clocks may be enabled by the low level suspend
>> + * code, so we need to assume that PLL is in enabled state during
>> + * suspend.
>> + *
>> + * We will keep PLLs and system clock resumed during suspend time.
>> + * All PLLs on all SoCs are low power and system clock is always-on,
>> + * so practically not much is changed here.
>> + */
>> +
>> + return clk_prepare(clk_dev->hw->clk);
> I am trying to understand, more exactly, what you intend to achieve
> with the clk_prepare() here. It looks a bit weird, to me. Can you try
> to elaborate a bit more on the use case?
The Tegra GENPD driver enable/disable clocks when domain is turned on.
This can't be done during early system resume, when domains are getting
turned on by the drivers core, because when clock is enabled, it's
getting prepared (RPM-resumed) and this preparation fails because
performance state of the clock goes up and it doesn't work during the
early resume time since I2C, which applies the state to hardware, is
suspended and can't work at that early time.
Secondly, Tegra has arch-specific low level assembly which touches
clocks during last phase of system suspend and in the beginning of
resume. Hence, clocks should stay prepared during suspend just because
technically clock should be prepared before it can be enabled.
> Is this rather about making sure that the clock's corresponding PM
> domain stays powered on during system suspend? In that case, I think
> there may be an alternative option....
>
This is not about domain staying powered on, this is about keeping the
performance state of the domain high during suspend.
