Re: [PATCH 1/2] cpufreq: Set policy->related_cpus to atleast policy->cpus

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 29 January 2013 10:09, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote:
> With the addition of following patch, related_cpus is required to be set by
> cpufreq platform drivers:
>
> commit c1070fd743533efb54e98142252283583f379190
> Author: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
> Date:   Mon Jan 14 13:23:04 2013 +0000
>
>     cpufreq: Simplify cpufreq_add_dev()
>
> Because this change is required by all platform drivers, why not do this in the
> core itself. Hence, this patch is an attempt towards fixing all broken drivers.
>
> From now on, platforms don't really need to set related_cpus from their init()
> routines, as the same work is done by core too.
>
> If platform driver needs to set the related_cpus mask with some additional cpus,
> other than cpus present in policy->cpus, they are free to do it as we aren't
> overriding anything.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
> ---
> Inderpal,
>
> Can you please add your tested-by for this patch? And this will require you to
> drop your patch for exynos-cpufreq.c :)

ARM mail servers are broken. Patches attached.

Attachment: 0001-cpufreq-Set-policy-related_cpus-to-atleast-policy-cp.patch
Description: Binary data

Attachment: 0002-Revert-cpufreq-Don-t-use-cpu-removed-during-cpufreq_.patch
Description: Binary data


[Index of Archives]     [Linux Kernel Devel]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Forum]     [Linux SCSI]

  Powered by Linux