Re: [PATCH v4 1/2] cpufreq: tegra124: Remove use of disable_cpufreq

Aaron Kling
2025-06-30T18:43:53Z

On Thu, Jun 5, 2025 at 5:51 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> On 05-06-25, 11:34, Jon Hunter wrote:
> > I think that would be fine. Given that the tegra124-cpufreq driver is the
> > parent, if it fails to resume, then I assume that cpufreq-dt driver would
> > not resume either?
>
> There is no resume interface in the cpufreq-dt driver, it is the cpufreq core
> which resumes to doing DVFS and I think it will try to do DVFS even if tegra's
> driver failed.

In my opinion, I'm thinking the original flow makes more sense. If
resume fails, disable cpufreq. Then the subsystem doesn't keep trying
and failing and causing who knows what kind of havoc. But if that's
still not desired, what should I do to get this moving again? Just
drop the error handling entirely, as suggested?

Aaron