On 09-02-18, 10:03, Neil Armstrong wrote:
> On 09/02/2018 09:58, Viresh Kumar wrote:
> > The "cooling-min-level" and "cooling-max-level" properties are not
> > parsed by any part of the kernel currently and the max cooling state of
> > a CPU cooling device is found by referring to the cpufreq table instead.
> >
> > Remove the unused properties from the CPU nodes.
> >
> > Signed-off-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
> > ---
> > arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts | 4 ----
> > 1 file changed, 4 deletions(-)
> >
> > diff --git a/arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts b/arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts
> > index 1448c3dba08e..658215c9822c 100644
> > --- a/arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts
> > +++ b/arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts
> > @@ -209,14 +209,10 @@
> > };
> >
> > &cpu0 {
> > - cooling-min-level = <0>;
> > - cooling-max-level = <6>;
> > #cooling-cells = <2>;
> > };
> >
> > &cpu4 {
> > - cooling-min-level = <0>;
> > - cooling-max-level = <4>;
> > #cooling-cells = <2>;
> > };
> >
> >
>
> Acked-by: Neil Armstrong <narmstrong@xxxxxxxxxxxx>
Is Kevin going to apply these for 4.17 ?
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
