Re: [PATCHv2 0/4] cpufreq-dt, platform_data based proposal

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

 



On 10 September 2014 17:38, Thomas Petazzoni
<thomas.petazzoni@xxxxxxxxxxxxxxxxxx> wrote:
> Hello,
>
> Here is the v2 of the platform_data based proposal to make cpufreq-dt
> understand when it has a shared clock by all CPUs vs. independent
> clock for each CPU.
>
> Changes since v1:
>
>  - Use a 'void *driver_data' in cpufreq_driver instead of extending
>    the existing flags field. Suggested by Viresh.
>
>  - Keep the regulator related warning in cpufreq-dt, but reword it,
>    and move it to the dev_dbg() level instead of dev_warn().
>
> Thanks,
>
> Thomas
>
> Thomas Petazzoni (4):
>   cpufreq: allow driver-specific data
>   cpufreq: cpufreq-dt: extend with platform_data
>   ARM: mvebu: use the cpufreq-dt platform_data for independent clocks
>   cpufreq: cpufreq-dt: adjust message related to regulators

After Arnd's reply:

Acked-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [Linux for Sparc]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux