[PATCH v3 1/3] cpufreq: mediatek: using global lock avoid race condition
Viresh Kumar
viresh.kumar at linaro.org
Thu Mar 20 21:56:24 PDT 2025
On 20-03-25, 08:22, Chun-Jen Tseng (曾俊仁) wrote:
> The struct mtk_cpu_dvfs_info instance is per-policy and the reg_lock is
> also in this structure. when I have two "policy-0" and "policy-6" use
> the same mtk_cpufreq_set_target() function but the info->reg_lock
> is from 2 instance(policy-0 and policy-6). when the policy-0 and
> policy-6 call set_target target, the mutex_lock is locked by per-
> policy. So, I change to global lock avoid per-policy lock.
Yes, that's what you are doing. I am asking why a global lock is required here ?
I think the per-policy lock is all you need.
--
viresh
More information about the linux-arm-kernel
mailing list