On 11.07.2025 05:50, Penny Zheng wrote: > Right now, only when we failed cpufreq driver registration with -ENODEV, we > get > the chance to try the fallback option. > There are two code path erroring out other than -ENODEV in cpufreq driver > registration: one is when the driver itself is broken, like missing mandatory > hooks, cpufreq_register_driver() will fail with -EINVAL, in which we shall > be able to try the fallback option, and the other is -EBUSY due to repeated > registration, in which we shall just exit the loop. > > So in conclusion, when error code is -EBUSY or successful return, both > indicating a proper driver is already registered, we shall bail the loop, > other than that, we shall continue to try the fallback option. > > Signed-off-by: Penny Zheng <penny.zh...@amd.com>
Reviewed-by: Jan Beulich <jbeul...@suse.com> (and perhaps also a Reported-by: or Suggested-by: ...)
