On 23-08-21, 15:45, Taniya Das wrote:
> As remote cpufreq updates are supported on QCOM platforms, set
> dvfs_possible_from_any_cpu cpufreq driver flag.
>
> Signed-off-by: Taniya Das <tdas@xxxxxxxxxxxxxx>
> ---
> [v3]
> * update the dvfs_possible_from_any_cpu always from qcom_cpufreq_hw_cpu_init
> [v2]
> * update the dvfs_possible_from_any_cpu always.
>
> drivers/cpufreq/qcom-cpufreq-hw.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/cpufreq/qcom-cpufreq-hw.c b/drivers/cpufreq/qcom-cpufreq-hw.c
> index f86859b..4dd77ac 100644
> --- a/drivers/cpufreq/qcom-cpufreq-hw.c
> +++ b/drivers/cpufreq/qcom-cpufreq-hw.c
> @@ -348,6 +348,7 @@ static int qcom_cpufreq_hw_cpu_init(struct cpufreq_policy *policy)
> }
>
> policy->driver_data = data;
> + policy->dvfs_possible_from_any_cpu = true;
>
> ret = qcom_cpufreq_hw_read_lut(cpu_dev, policy);
> if (ret) {
Applied. Thanks.
--
viresh
