| Message ID | 1391788548-13056-2-git-send-email-thomas.ab@samsung.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On 02/07/2014 09:55 AM, Thomas Abraham wrote: > From: Thomas Abraham <thomas.ab@samsung.com> > > Lookup for the optional boost-frequency property in cpu0 node and if > available, enable support for boost mode frequencies. The frequencies > usable in boost mode are determined while preparing the cpufreq table > from the list of operating points available. > > In addition to this, enable the CPU_FREQ_BOOST_SW config option for > this driver by default. On platforms that do not support boost mode, > the boost mode frequencies will not be specified in cpu0 node and > hence the boost mode support will not be enabled. Since this driver > anyways depends on THERMAL config option, it is safe to enable > CPU_FREQ_BOOST_SW config option as default. > > Cc: Shawn Guo <shawn.guo@linaro.org> > Cc: Lukasz Majewski <l.majewski@samsung.com> > Signed-off-by: Thomas Abraham <thomas.ab@samsung.com> > --- > Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt | 2 ++ > drivers/cpufreq/Kconfig | 1 + > drivers/cpufreq/cpufreq-cpu0.c | 3 +++ > 3 files changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt b/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt > index f055515..60f321a 100644 > --- a/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt > +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt > @@ -19,6 +19,8 @@ Optional properties: > - cooling-min-level: > - cooling-max-level: > Please refer to Documentation/devicetree/bindings/thermal/thermal.txt. > +- boost-frequency: > + Please refer to Documentation/devicetree/bindings/cpufreq/cpufreq-boost.txt > > Examples: > > diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig > index 4b029c0..52cc704 100644 > --- a/drivers/cpufreq/Kconfig > +++ b/drivers/cpufreq/Kconfig > @@ -187,6 +187,7 @@ config GENERIC_CPUFREQ_CPU0 > tristate "Generic CPU0 cpufreq driver" > depends on HAVE_CLK && REGULATOR && OF && THERMAL && CPU_THERMAL > select PM_OPP > + select CPU_FREQ_BOOST_SW > help > This adds a generic cpufreq driver for CPU0 frequency management. > It supports both uniprocessor (UP) and symmetric multiprocessor (SMP) > diff --git a/drivers/cpufreq/cpufreq-cpu0.c b/drivers/cpufreq/cpufreq-cpu0.c > index 0c12ffc..06539eb 100644 > --- a/drivers/cpufreq/cpufreq-cpu0.c > +++ b/drivers/cpufreq/cpufreq-cpu0.c > @@ -195,6 +195,9 @@ static int cpu0_cpufreq_probe(struct platform_device *pdev) > transition_latency += ret * 1000; > } > > + if (of_find_property(cpu_dev->of_node, "boost-frequency", NULL)) > + cpu0_cpufreq_driver.boost_supported = true; > + > ret = cpufreq_register_driver(&cpu0_cpufreq_driver); > if (ret) { > pr_err("failed register driver: %d\n", ret); > might as well hide that under the opp api which returns a bool that says if boost is supported or not. that allows the parse to be isolated to a single location.
On Fri, Feb 7, 2014 at 9:46 PM, Nishanth Menon <nm@ti.com> wrote: > On 02/07/2014 09:55 AM, Thomas Abraham wrote: >> From: Thomas Abraham <thomas.ab@samsung.com> >> >> Lookup for the optional boost-frequency property in cpu0 node and if >> available, enable support for boost mode frequencies. The frequencies >> usable in boost mode are determined while preparing the cpufreq table >> from the list of operating points available. >> >> In addition to this, enable the CPU_FREQ_BOOST_SW config option for >> this driver by default. On platforms that do not support boost mode, >> the boost mode frequencies will not be specified in cpu0 node and >> hence the boost mode support will not be enabled. Since this driver >> anyways depends on THERMAL config option, it is safe to enable >> CPU_FREQ_BOOST_SW config option as default. >> >> Cc: Shawn Guo <shawn.guo@linaro.org> >> Cc: Lukasz Majewski <l.majewski@samsung.com> >> Signed-off-by: Thomas Abraham <thomas.ab@samsung.com> >> --- >> Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt | 2 ++ >> drivers/cpufreq/Kconfig | 1 + >> drivers/cpufreq/cpufreq-cpu0.c | 3 +++ >> 3 files changed, 6 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt b/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt >> index f055515..60f321a 100644 >> --- a/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt >> +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt >> @@ -19,6 +19,8 @@ Optional properties: >> - cooling-min-level: >> - cooling-max-level: >> Please refer to Documentation/devicetree/bindings/thermal/thermal.txt. >> +- boost-frequency: >> + Please refer to Documentation/devicetree/bindings/cpufreq/cpufreq-boost.txt >> >> Examples: >> >> diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig >> index 4b029c0..52cc704 100644 >> --- a/drivers/cpufreq/Kconfig >> +++ b/drivers/cpufreq/Kconfig >> @@ -187,6 +187,7 @@ config GENERIC_CPUFREQ_CPU0 >> tristate "Generic CPU0 cpufreq driver" >> depends on HAVE_CLK && REGULATOR && OF && THERMAL && CPU_THERMAL >> select PM_OPP >> + select CPU_FREQ_BOOST_SW >> help >> This adds a generic cpufreq driver for CPU0 frequency management. >> It supports both uniprocessor (UP) and symmetric multiprocessor (SMP) >> diff --git a/drivers/cpufreq/cpufreq-cpu0.c b/drivers/cpufreq/cpufreq-cpu0.c >> index 0c12ffc..06539eb 100644 >> --- a/drivers/cpufreq/cpufreq-cpu0.c >> +++ b/drivers/cpufreq/cpufreq-cpu0.c >> @@ -195,6 +195,9 @@ static int cpu0_cpufreq_probe(struct platform_device *pdev) >> transition_latency += ret * 1000; >> } >> >> + if (of_find_property(cpu_dev->of_node, "boost-frequency", NULL)) >> + cpu0_cpufreq_driver.boost_supported = true; >> + >> ret = cpufreq_register_driver(&cpu0_cpufreq_driver); >> if (ret) { >> pr_err("failed register driver: %d\n", ret); >> > > might as well hide that under the opp api which returns a bool that > says if boost is supported or not. that allows the parse to be > isolated to a single location. This is specific to the cpufreq-cpu0 driver. Other cpufreq drivers might want to use other methods and additional constraints to determine if boost has to be enabled. Thanks, Thomas. > > -- > Regards, > Nishanth Menon
On Fri, Feb 7, 2014 at 11:19 PM, Thomas Abraham <ta.omasab@gmail.com> wrote: >>> --- a/drivers/cpufreq/cpufreq-cpu0.c >>> +++ b/drivers/cpufreq/cpufreq-cpu0.c >>> @@ -195,6 +195,9 @@ static int cpu0_cpufreq_probe(struct platform_device *pdev) >>> transition_latency += ret * 1000; >>> } >>> >>> + if (of_find_property(cpu_dev->of_node, "boost-frequency", NULL)) >>> + cpu0_cpufreq_driver.boost_supported = true; >>> + >> might as well hide that under the opp api which returns a bool that >> says if boost is supported or not. that allows the parse to be >> isolated to a single location. > > This is specific to the cpufreq-cpu0 driver. Other cpufreq drivers > might want to use other methods and additional constraints to > determine if boost has to be enabled. struct cpufreq_driver::boost_supported is nothing CPU0 specifc - i am just saying that the same property "boost-frequency" parsed by in two places (dev_pm_opp_init_cpufreq_table and cpu0_cpufreq_probe) is a very bad idea. you could instead make int dev_pm_opp_init_cpufreq_table(struct device *dev, struct cpufreq_frequency_table **table) into: int dev_pm_opp_init_cpufreq_table(struct device *dev, struct cpufreq_frequency_table **table, bool *boost_supported); Then use boost_supported for anything of your driver's choice (including updating cpufreq_driver::boost_supported). That allows the property to be isolated into a single function, who can be modified without impacting other drivers at a later point in time. Regards, Nishanth Menon
Hi Thomas, > From: Thomas Abraham <thomas.ab@samsung.com> > > Lookup for the optional boost-frequency property in cpu0 node and if > available, enable support for boost mode frequencies. The frequencies > usable in boost mode are determined while preparing the cpufreq table > from the list of operating points available. > > In addition to this, enable the CPU_FREQ_BOOST_SW config option for > this driver by default. On platforms that do not support boost mode, > the boost mode frequencies will not be specified in cpu0 node and > hence the boost mode support will not be enabled. Since this driver > anyways depends on THERMAL config option, it is safe to enable > CPU_FREQ_BOOST_SW config option as default. I think that you introduce some implicit dependency here. I don't like the idea to enable CPU_FREQ_BOOST_SW by default and depend on other option (THERMAL in this case). I think that user shall feel free to explicitly enable or disable boost from menuconfig. > > Cc: Shawn Guo <shawn.guo@linaro.org> > Cc: Lukasz Majewski <l.majewski@samsung.com> > Signed-off-by: Thomas Abraham <thomas.ab@samsung.com> > --- > Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt | 2 ++ > drivers/cpufreq/Kconfig | 1 + > drivers/cpufreq/cpufreq-cpu0.c | 3 +++ > 3 files changed, 6 insertions(+) > > diff --git > a/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt > b/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt index > f055515..60f321a 100644 --- > a/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt +++ > b/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt @@ -19,6 > +19,8 @@ Optional properties: > - cooling-min-level: > - cooling-max-level: > Please refer to > Documentation/devicetree/bindings/thermal/thermal.txt. +- > boost-frequency: > + Please refer to > Documentation/devicetree/bindings/cpufreq/cpufreq-boost.txt > Examples: > > diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig > index 4b029c0..52cc704 100644 > --- a/drivers/cpufreq/Kconfig > +++ b/drivers/cpufreq/Kconfig > @@ -187,6 +187,7 @@ config GENERIC_CPUFREQ_CPU0 > tristate "Generic CPU0 cpufreq driver" > depends on HAVE_CLK && REGULATOR && OF && THERMAL && > CPU_THERMAL select PM_OPP > + select CPU_FREQ_BOOST_SW > help > This adds a generic cpufreq driver for CPU0 frequency > management. It supports both uniprocessor (UP) and symmetric > multiprocessor (SMP) diff --git a/drivers/cpufreq/cpufreq-cpu0.c > b/drivers/cpufreq/cpufreq-cpu0.c index 0c12ffc..06539eb 100644 > --- a/drivers/cpufreq/cpufreq-cpu0.c > +++ b/drivers/cpufreq/cpufreq-cpu0.c > @@ -195,6 +195,9 @@ static int cpu0_cpufreq_probe(struct > platform_device *pdev) transition_latency += ret * 1000; > } > > + if (of_find_property(cpu_dev->of_node, "boost-frequency", > NULL)) > + cpu0_cpufreq_driver.boost_supported = true; > + This is also a bit misleading. Here you assume, that boost is supported when somebody define "boost-frequency" DTS attribute. Conceptually the boost is supported when user explicitly selects CONFIG_CPU_FREQ_BOOST_SW. I would prefer to see approach similar to the one now found at exynos-cpufreq.c exynos_driver struct: static struct cpufreq_driver cpu0_cpufreq_driver = { .flags = CPUFREQ_STICKY, .verify = cpu0_verify_speed, .target = cpu0_set_target, .get = cpu0_get_speed, #ifdef CONFIG_CPU_FREQ_BOOST_SW .boost_supported = true, #endif ... other fields ... and also, please remove references to CONFIG_ARM_EXYNOS_CPU_FREQ_BOOST_SW flag since it will not be used after the exynos cpufreq clean up. > ret = cpufreq_register_driver(&cpu0_cpufreq_driver); > if (ret) { > pr_err("failed register driver: %d\n", ret);
Hi Thomas, On 07.02.2014 16:55, Thomas Abraham wrote: > From: Thomas Abraham <thomas.ab@samsung.com> > > Lookup for the optional boost-frequency property in cpu0 node and if > available, enable support for boost mode frequencies. The frequencies > usable in boost mode are determined while preparing the cpufreq table > from the list of operating points available. > > In addition to this, enable the CPU_FREQ_BOOST_SW config option for > this driver by default. On platforms that do not support boost mode, > the boost mode frequencies will not be specified in cpu0 node and > hence the boost mode support will not be enabled. Since this driver > anyways depends on THERMAL config option, it is safe to enable > CPU_FREQ_BOOST_SW config option as default. > > Cc: Shawn Guo <shawn.guo@linaro.org> > Cc: Lukasz Majewski <l.majewski@samsung.com> > Signed-off-by: Thomas Abraham <thomas.ab@samsung.com> > --- > Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt | 2 ++ > drivers/cpufreq/Kconfig | 1 + > drivers/cpufreq/cpufreq-cpu0.c | 3 +++ > 3 files changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt b/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt > index f055515..60f321a 100644 > --- a/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt > +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt > @@ -19,6 +19,8 @@ Optional properties: > - cooling-min-level: > - cooling-max-level: > Please refer to Documentation/devicetree/bindings/thermal/thermal.txt. > +- boost-frequency: > + Please refer to Documentation/devicetree/bindings/cpufreq/cpufreq-boost.txt > > Examples: > > diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig > index 4b029c0..52cc704 100644 > --- a/drivers/cpufreq/Kconfig > +++ b/drivers/cpufreq/Kconfig > @@ -187,6 +187,7 @@ config GENERIC_CPUFREQ_CPU0 > tristate "Generic CPU0 cpufreq driver" > depends on HAVE_CLK && REGULATOR && OF && THERMAL && CPU_THERMAL > select PM_OPP > + select CPU_FREQ_BOOST_SW > help > This adds a generic cpufreq driver for CPU0 frequency management. > It supports both uniprocessor (UP) and symmetric multiprocessor (SMP) > diff --git a/drivers/cpufreq/cpufreq-cpu0.c b/drivers/cpufreq/cpufreq-cpu0.c > index 0c12ffc..06539eb 100644 > --- a/drivers/cpufreq/cpufreq-cpu0.c > +++ b/drivers/cpufreq/cpufreq-cpu0.c > @@ -195,6 +195,9 @@ static int cpu0_cpufreq_probe(struct platform_device *pdev) > transition_latency += ret * 1000; > } > > + if (of_find_property(cpu_dev->of_node, "boost-frequency", NULL)) > + cpu0_cpufreq_driver.boost_supported = true; > + > ret = cpufreq_register_driver(&cpu0_cpufreq_driver); > if (ret) { > pr_err("failed register driver: %d\n", ret); > I'd say that boost should be enabled depending on user's preference, as done before in Exynos cpufreq driver. So both presence of boost-frequency property and state of CPU_FREQ_BOOST_SW should be considered. As for CPU_FREQ_BOOST_SW, I don't think it should be always selected, but ather, either converted to a user-selectable bool entry or made selectable by other entry, like current ARM_EXYNOS_CPU_FREQ_BOOST_SW. Best regards, Tomasz
On Wed, Feb 12, 2014 at 8:28 PM, Tomasz Figa <t.figa@samsung.com> wrote: > Hi Thomas, > > > On 07.02.2014 16:55, Thomas Abraham wrote: >> >> From: Thomas Abraham <thomas.ab@samsung.com> >> >> Lookup for the optional boost-frequency property in cpu0 node and if >> available, enable support for boost mode frequencies. The frequencies >> usable in boost mode are determined while preparing the cpufreq table >> from the list of operating points available. >> >> In addition to this, enable the CPU_FREQ_BOOST_SW config option for >> this driver by default. On platforms that do not support boost mode, >> the boost mode frequencies will not be specified in cpu0 node and >> hence the boost mode support will not be enabled. Since this driver >> anyways depends on THERMAL config option, it is safe to enable >> CPU_FREQ_BOOST_SW config option as default. >> >> Cc: Shawn Guo <shawn.guo@linaro.org> >> Cc: Lukasz Majewski <l.majewski@samsung.com> >> Signed-off-by: Thomas Abraham <thomas.ab@samsung.com> >> --- >> Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt | 2 ++ >> drivers/cpufreq/Kconfig | 1 + >> drivers/cpufreq/cpufreq-cpu0.c | 3 +++ >> 3 files changed, 6 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt >> b/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt >> index f055515..60f321a 100644 >> --- a/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt >> +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt >> @@ -19,6 +19,8 @@ Optional properties: >> - cooling-min-level: >> - cooling-max-level: >> Please refer to >> Documentation/devicetree/bindings/thermal/thermal.txt. >> +- boost-frequency: >> + Please refer to >> Documentation/devicetree/bindings/cpufreq/cpufreq-boost.txt >> >> Examples: >> >> diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig >> index 4b029c0..52cc704 100644 >> --- a/drivers/cpufreq/Kconfig >> +++ b/drivers/cpufreq/Kconfig >> @@ -187,6 +187,7 @@ config GENERIC_CPUFREQ_CPU0 >> tristate "Generic CPU0 cpufreq driver" >> depends on HAVE_CLK && REGULATOR && OF && THERMAL && CPU_THERMAL >> select PM_OPP >> + select CPU_FREQ_BOOST_SW >> help >> This adds a generic cpufreq driver for CPU0 frequency >> management. >> It supports both uniprocessor (UP) and symmetric multiprocessor >> (SMP) >> diff --git a/drivers/cpufreq/cpufreq-cpu0.c >> b/drivers/cpufreq/cpufreq-cpu0.c >> index 0c12ffc..06539eb 100644 >> --- a/drivers/cpufreq/cpufreq-cpu0.c >> +++ b/drivers/cpufreq/cpufreq-cpu0.c >> @@ -195,6 +195,9 @@ static int cpu0_cpufreq_probe(struct platform_device >> *pdev) >> transition_latency += ret * 1000; >> } >> >> + if (of_find_property(cpu_dev->of_node, "boost-frequency", NULL)) >> + cpu0_cpufreq_driver.boost_supported = true; >> + >> ret = cpufreq_register_driver(&cpu0_cpufreq_driver); >> if (ret) { >> pr_err("failed register driver: %d\n", ret); >> > > I'd say that boost should be enabled depending on user's preference, as done > before in Exynos cpufreq driver. So both presence of boost-frequency > property and state of CPU_FREQ_BOOST_SW should be considered. > > As for CPU_FREQ_BOOST_SW, I don't think it should be always selected, but > ather, either converted to a user-selectable bool entry or made selectable > by other entry, like current ARM_EXYNOS_CPU_FREQ_BOOST_SW. We still will have the same problem on Exynos multi-platform kernel where one Exynos platform needs it and others don't. Same with just using the CPU_FREQ_BOOST_SW config option. So that was the reason to just fallback on presence of boost property. Thanks, Thomas. > > Best regards, > Tomasz
On 13.02.2014 09:02, Thomas Abraham wrote: > On Wed, Feb 12, 2014 at 8:28 PM, Tomasz Figa <t.figa@samsung.com> wrote: >> Hi Thomas, >> >> >> On 07.02.2014 16:55, Thomas Abraham wrote: [snip] >>> diff --git a/drivers/cpufreq/cpufreq-cpu0.c >>> b/drivers/cpufreq/cpufreq-cpu0.c >>> index 0c12ffc..06539eb 100644 >>> --- a/drivers/cpufreq/cpufreq-cpu0.c >>> +++ b/drivers/cpufreq/cpufreq-cpu0.c >>> @@ -195,6 +195,9 @@ static int cpu0_cpufreq_probe(struct platform_device >>> *pdev) >>> transition_latency += ret * 1000; >>> } >>> >>> + if (of_find_property(cpu_dev->of_node, "boost-frequency", NULL)) >>> + cpu0_cpufreq_driver.boost_supported = true; >>> + >>> ret = cpufreq_register_driver(&cpu0_cpufreq_driver); >>> if (ret) { >>> pr_err("failed register driver: %d\n", ret); >>> >> >> I'd say that boost should be enabled depending on user's preference, as done >> before in Exynos cpufreq driver. So both presence of boost-frequency >> property and state of CPU_FREQ_BOOST_SW should be considered. >> >> As for CPU_FREQ_BOOST_SW, I don't think it should be always selected, but >> ather, either converted to a user-selectable bool entry or made selectable >> by other entry, like current ARM_EXYNOS_CPU_FREQ_BOOST_SW. > > We still will have the same problem on Exynos multi-platform kernel > where one Exynos platform needs it and others don't. Same with just > using the CPU_FREQ_BOOST_SW config option. So that was the reason to > just fallback on presence of boost property. I don't think we really have a problem here, because we have well defined semantics for particular enable methods: - Kconfig is supposed to be a global enable - if an option is disabled, it is not even built into the kernel and can be used in any way - this is per-user choice, regardless of platform the image is going to be running on, - device tree is supposed to be telling us whether the hardware we are running on supports given feature and all the required data to enable it, if yes, - then, for per system configuration, you should be able to enable/disable given feature by a command line parameter, e.g. cpufreq.boost_disable. If you follow the above description, you should be able to get any configuration you want on any system, as long as it's supported by hardware. Best regards, Tomasz
diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt b/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt index f055515..60f321a 100644 --- a/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt @@ -19,6 +19,8 @@ Optional properties: - cooling-min-level: - cooling-max-level: Please refer to Documentation/devicetree/bindings/thermal/thermal.txt. +- boost-frequency: + Please refer to Documentation/devicetree/bindings/cpufreq/cpufreq-boost.txt Examples: diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig index 4b029c0..52cc704 100644 --- a/drivers/cpufreq/Kconfig +++ b/drivers/cpufreq/Kconfig @@ -187,6 +187,7 @@ config GENERIC_CPUFREQ_CPU0 tristate "Generic CPU0 cpufreq driver" depends on HAVE_CLK && REGULATOR && OF && THERMAL && CPU_THERMAL select PM_OPP + select CPU_FREQ_BOOST_SW help This adds a generic cpufreq driver for CPU0 frequency management. It supports both uniprocessor (UP) and symmetric multiprocessor (SMP) diff --git a/drivers/cpufreq/cpufreq-cpu0.c b/drivers/cpufreq/cpufreq-cpu0.c index 0c12ffc..06539eb 100644 --- a/drivers/cpufreq/cpufreq-cpu0.c +++ b/drivers/cpufreq/cpufreq-cpu0.c @@ -195,6 +195,9 @@ static int cpu0_cpufreq_probe(struct platform_device *pdev) transition_latency += ret * 1000; } + if (of_find_property(cpu_dev->of_node, "boost-frequency", NULL)) + cpu0_cpufreq_driver.boost_supported = true; + ret = cpufreq_register_driver(&cpu0_cpufreq_driver); if (ret) { pr_err("failed register driver: %d\n", ret);