[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250701062314.42hudnylecbrta4f@vireshk-i7>
Date: Tue, 1 Jul 2025 11:53:14 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Aaron Kling <webgeek1234@...il.com>
Cc: Jon Hunter <jonathanh@...dia.com>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Thierry Reding <thierry.reding@...il.com>, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-tegra@...r.kernel.org
Subject: Re: [PATCH v4 1/2] cpufreq: tegra124: Remove use of disable_cpufreq
On 30-06-25, 13:43, Aaron Kling wrote:
> 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.
Lets do this and move ahead since we aren't able to conclude for a while.
--
viresh
Powered by blists - more mailing lists