[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250122061250.kxdpkkvce4g5nar2@vireshk-i7>
Date: Wed, 22 Jan 2025 11:42:50 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Beata Michalska <beata.michalska@....com>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-pm@...r.kernel.org, ionela.voinescu@....com,
sudeep.holla@....com, will@...nel.org, catalin.marinas@....com,
rafael@...nel.org, sumitg@...dia.com, yang@...amperecomputing.com,
vanshikonda@...amperecomputing.com, lihuisong@...wei.com,
zhanjie9@...ilicon.com
Subject: Re: [PATCH v9 1/5] cpufreq: Allow arch_freq_get_on_cpu to return an
error
On 21-01-25, 16:14, Beata Michalska wrote:
> Theoretically speaking - it should, though what would 0 actually
> represent then ?
0 won't be a failure, that's clear, since errors are represented
differently now. I am not sure what 0 frequency would mean and it can
be left as an architecture specific value, which is a corner case I am
not sure will ever occur.
--
viresh
Powered by blists - more mailing lists