linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>,
	arnd.bergmann@linaro.org, arm@kernel.org,
	Rafael Wysocki <rjw@rjwysocki.net>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Cc: linux-pm@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Eduardo Valentin <edubezval@gmail.com>,
	Zhang Rui <rui.zhang@intel.com>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	daniel.lezcano@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 07/10] ARM: dts: gemini: Remove "cooling-{min|max}-level" for gpio-fan node
Date: Tue, 20 Mar 2018 09:43:18 +0800	[thread overview]
Message-ID: <20180320014318.g7koh7ld3seucg4c@vireshk-mac-ubuntu> (raw)
In-Reply-To: <20180312043533.GU6842@vireshk-i7>

On 12-03-18, 10:05, Viresh Kumar wrote:
> On 09-02-18, 14:28, 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
> > gpio-fan cooling device is found by referring to the
> > "gpio-fan,speed-map" instead.
> > 
> > Remove the unused properties from the gpio-fan node.
> > 
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > ---
> >  arch/arm/boot/dts/gemini-dlink-dns-313.dts | 2 --
> >  1 file changed, 2 deletions(-)
> > 
> > diff --git a/arch/arm/boot/dts/gemini-dlink-dns-313.dts b/arch/arm/boot/dts/gemini-dlink-dns-313.dts
> > index 08568ce24d06..727d16eb02d9 100644
> > --- a/arch/arm/boot/dts/gemini-dlink-dns-313.dts
> > +++ b/arch/arm/boot/dts/gemini-dlink-dns-313.dts
> > @@ -78,8 +78,6 @@
> >  		gpios = <&gpio0 11 GPIO_ACTIVE_HIGH>,
> >  			<&gpio0 12 GPIO_ACTIVE_HIGH>;
> >  		gpio-fan,speed-map = <0 0>, <3000 1>, <6000 2>;
> > -		cooling-min-level = <0>;
> > -		cooling-max-level = <2>;
> >  		#cooling-cells = <2>;
> >  	};
> >  
> 
> @Linus: Can you please pick this one for 4.17 ?

@Arnd/Olof: Can you please pick this one up as well ?

-- 
viresh

  reply	other threads:[~2018-03-20  1:43 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09  8:58 [PATCH 00/10] thermal: Remove "cooling-{min|max}-level" properties Viresh Kumar
2018-02-09  8:58 ` [PATCH 01/10] ARM: dts: exynos: Remove "cooling-{min|max}-level" for CPU nodes Viresh Kumar
2018-02-13 18:16   ` Krzysztof Kozlowski
2018-02-09  8:58 ` [PATCH 02/10] ARM: dts: omap: " Viresh Kumar
2018-02-12 17:17   ` Tony Lindgren
2018-02-12 17:18     ` Tony Lindgren
2018-02-09  8:58 ` [PATCH 03/10] ARM: dts: mt7623: " Viresh Kumar
2018-02-18 23:26   ` Rob Herring
2018-02-09  8:58 ` [PATCH 04/10] ARM: dts: sun[4-7]i: " Viresh Kumar
2018-02-13  9:13   ` Maxime Ripard
2018-02-13  9:18     ` Chen-Yu Tsai
2018-02-14  3:12       ` Viresh Kumar
2018-02-09  8:58 ` [PATCH 05/10] ARM64: dts: hi6220: " Viresh Kumar
2018-03-02 16:03   ` Wei Xu
2018-02-09  8:58 ` [PATCH 06/10] ARM64: dts: meson: " Viresh Kumar
2018-02-09  9:03   ` Neil Armstrong
2018-03-12  4:32     ` Viresh Kumar
2018-03-20  1:37   ` Viresh Kumar
2018-03-27 12:29     ` Arnd Bergmann
2018-02-09  8:58 ` [PATCH 07/10] ARM: dts: gemini: Remove "cooling-{min|max}-level" for gpio-fan node Viresh Kumar
2018-03-12  4:35   ` Viresh Kumar
2018-03-20  1:43     ` Viresh Kumar [this message]
2018-03-20  3:10   ` Linus Walleij
2018-03-27 12:26     ` Arnd Bergmann
2018-03-27 12:29       ` Linus Walleij
2018-02-09  8:58 ` [PATCH 08/10] ARM64: dts: meson: " Viresh Kumar
2018-02-09  9:04   ` Neil Armstrong
2018-02-09  8:58 ` [PATCH 09/10] dt-bindings: cpufreq-dt: Remove "cooling-{min|max}-level" properties Viresh Kumar
2018-02-18 23:26   ` Rob Herring
2018-02-09  8:58 ` [PATCH 10/10] dt-bindings: thermal: " Viresh Kumar
2018-02-18 23:29   ` Rob Herring
2018-02-19  3:43     ` Viresh Kumar
2018-02-19 18:01       ` Rob Herring
2018-03-12  4:38   ` Viresh Kumar
2018-03-20 12:49     ` Zhang Rui
2018-03-27 13:46       ` Eduardo Valentin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180320014318.g7koh7ld3seucg4c@vireshk-mac-ubuntu \
    --to=viresh.kumar@linaro.org \
    --cc=arm@kernel.org \
    --cc=arnd.bergmann@linaro.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=vincent.guittot@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).