| Message ID | 1371661969-7660-5-git-send-email-l.majewski@samsung.com (mailing list archive) |
|---|---|
| State | Changes Requested, archived |
| Headers | show |
On 19 June 2013 22:42, Lukasz Majewski <l.majewski@samsung.com> wrote: > The struct cpufreq_driver has been extended to embrace the information > related to boost support. > > When "boost_mode" device tree attribute is defined for a platform, the > boost_supported flag is set. Moreover boost related attributes were > exported. > > Signed-off-by: Lukasz Majewski <l.majewski@samsung.com> > Signed-off-by: Myungjoo Ham <myungjoo.ham@samsung.com> > > Changes for v4: > - None > > Changes for v3: > - Remove low level boost code > - Move boost management code to cpufreq core code > - Use boost_supported flag to indicate if driver supports over clocking > > Changes for v2: > - Removal of struct cpufreq_boost > - Removal of the CONFIG_CPU_FREQ_BOOST flag > - low_level_boost with valid address when boost is supported > --- > drivers/cpufreq/exynos-cpufreq.c | 4 ++++ > 1 file changed, 4 insertions(+) Yes, this looks fine.. I will Ack the whole series in the end, so no individual acks :) -- To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 27 Jun 2013 14:28:11 +0530, Viresh Kumar wrote: > On 19 June 2013 22:42, Lukasz Majewski <l.majewski@samsung.com> wrote: > > The struct cpufreq_driver has been extended to embrace the > > information related to boost support. > > > > When "boost_mode" device tree attribute is defined for a platform, > > the boost_supported flag is set. Moreover boost related attributes > > were exported. > > > > Signed-off-by: Lukasz Majewski <l.majewski@samsung.com> > > Signed-off-by: Myungjoo Ham <myungjoo.ham@samsung.com> > > > > Changes for v4: > > - None > > > > Changes for v3: > > - Remove low level boost code > > - Move boost management code to cpufreq core code > > - Use boost_supported flag to indicate if driver supports over > > clocking > > > > Changes for v2: > > - Removal of struct cpufreq_boost > > - Removal of the CONFIG_CPU_FREQ_BOOST flag > > - low_level_boost with valid address when boost is supported > > --- > > drivers/cpufreq/exynos-cpufreq.c | 4 ++++ > > 1 file changed, 4 insertions(+) > > Yes, this looks fine.. > > I will Ack the whole series in the end, so no individual acks :) Ok.
diff --git a/drivers/cpufreq/exynos-cpufreq.c b/drivers/cpufreq/exynos-cpufreq.c index 3197d88..b0e424e 100644 --- a/drivers/cpufreq/exynos-cpufreq.c +++ b/drivers/cpufreq/exynos-cpufreq.c @@ -264,6 +264,7 @@ static int exynos_cpufreq_cpu_exit(struct cpufreq_policy *policy) static struct freq_attr *exynos_cpufreq_attr[] = { &cpufreq_freq_attr_scaling_available_freqs, + &cpufreq_freq_attr_scaling_boost_freqs, NULL, }; @@ -359,6 +360,7 @@ static struct of_device_id exynos_cpufreq_of_match[] __initconst = { static int __init exynos_cpufreq_probe(struct platform_device *pdev) { + struct device_node *node = pdev->dev.of_node; int ret = -EINVAL; exynos_info = kzalloc(sizeof(struct exynos_dvfs_info), GFP_KERNEL); @@ -391,6 +393,8 @@ static int __init exynos_cpufreq_probe(struct platform_device *pdev) } locking_frequency = exynos_getspeed(0); + if (of_property_read_bool(node, "boost_mode")) + exynos_driver.boost_supported = 1; register_pm_notifier(&exynos_cpufreq_nb);