All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
	Zhang Rui <rui.zhang@intel.com>,
	Eduardo Valentin <edubezval@gmail.com>,
	linux-pm@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	daniel.lezcano@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 10/10] dt-bindings: thermal: Remove "cooling-{min|max}-level" properties
Date: Sun, 18 Feb 2018 17:29:06 -0600	[thread overview]
Message-ID: <20180218232906.jkpymin3a4qxjhnc@rob-hp-laptop> (raw)
In-Reply-To: <0ec53640f1a09e6e0d7aa1a21d1a3266c3c209c7.1518166039.git.viresh.kumar@linaro.org>

On Fri, Feb 09, 2018 at 02:28:10PM +0530, Viresh Kumar wrote:
> The "cooling-min-level" and "cooling-max-level" properties are not
> parsed by any part of kernel currently and the max cooling state of a
> CPU cooling device is found by referring to the cpufreq table instead.

What about non-CPU devices? A fan for example.

> 
> Remove the unused bindings.
> 
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
>  Documentation/devicetree/bindings/thermal/thermal.txt | 16 +---------------
>  1 file changed, 1 insertion(+), 15 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/thermal/thermal.txt b/Documentation/devicetree/bindings/thermal/thermal.txt
> index 1719d47a5e2f..cc553f0952c5 100644
> --- a/Documentation/devicetree/bindings/thermal/thermal.txt
> +++ b/Documentation/devicetree/bindings/thermal/thermal.txt
> @@ -55,8 +55,7 @@ of heat dissipation). For example a fan's cooling states correspond to
>  the different fan speeds possible. Cooling states are referred to by
>  single unsigned integers, where larger numbers mean greater heat
>  dissipation. The precise set of cooling states associated with a device
> -(as referred to by the cooling-min-level and cooling-max-level
> -properties) should be defined in a particular device's binding.
> +should be defined in a particular device's binding.
>  For more examples of cooling devices, refer to the example sections below.
>  
>  Required properties:
> @@ -69,15 +68,6 @@ For more examples of cooling devices, refer to the example sections below.
>  			See Cooling device maps section below for more details
>  			on how consumers refer to cooling devices.
>  
> -Optional properties:
> -- cooling-min-level:	An integer indicating the smallest
> -  Type: unsigned	cooling state accepted. Typically 0.
> -  Size: one cell
> -
> -- cooling-max-level:	An integer indicating the largest
> -  Type: unsigned	cooling state accepted.
> -  Size: one cell
> -
>  * Trip points
>  
>  The trip node is a node to describe a point in the temperature domain
> @@ -226,8 +216,6 @@ cpus {
>  			396000  950000
>  			198000  850000
>  		>;
> -		cooling-min-level = <0>;
> -		cooling-max-level = <3>;
>  		#cooling-cells = <2>; /* min followed by max */
>  	};
>  	...
> @@ -241,8 +229,6 @@ cpus {
>  	 */
>  	fan0: fan@48 {
>  		...
> -		cooling-min-level = <0>;
> -		cooling-max-level = <9>;
>  		#cooling-cells = <2>; /* min followed by max */
>  	};
>  };
> -- 
> 2.15.0.194.g9af6a3dea062
> 

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>,
	linux-pm@vger.kernel.org, daniel.lezcano@linaro.org,
	Rafael Wysocki <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org,
	Eduardo Valentin <edubezval@gmail.com>,
	Zhang Rui <rui.zhang@intel.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 10/10] dt-bindings: thermal: Remove "cooling-{min|max}-level" properties
Date: Sun, 18 Feb 2018 17:29:06 -0600	[thread overview]
Message-ID: <20180218232906.jkpymin3a4qxjhnc@rob-hp-laptop> (raw)
In-Reply-To: <0ec53640f1a09e6e0d7aa1a21d1a3266c3c209c7.1518166039.git.viresh.kumar@linaro.org>

On Fri, Feb 09, 2018 at 02:28:10PM +0530, Viresh Kumar wrote:
> The "cooling-min-level" and "cooling-max-level" properties are not
> parsed by any part of kernel currently and the max cooling state of a
> CPU cooling device is found by referring to the cpufreq table instead.

What about non-CPU devices? A fan for example.

> 
> Remove the unused bindings.
> 
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
>  Documentation/devicetree/bindings/thermal/thermal.txt | 16 +---------------
>  1 file changed, 1 insertion(+), 15 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/thermal/thermal.txt b/Documentation/devicetree/bindings/thermal/thermal.txt
> index 1719d47a5e2f..cc553f0952c5 100644
> --- a/Documentation/devicetree/bindings/thermal/thermal.txt
> +++ b/Documentation/devicetree/bindings/thermal/thermal.txt
> @@ -55,8 +55,7 @@ of heat dissipation). For example a fan's cooling states correspond to
>  the different fan speeds possible. Cooling states are referred to by
>  single unsigned integers, where larger numbers mean greater heat
>  dissipation. The precise set of cooling states associated with a device
> -(as referred to by the cooling-min-level and cooling-max-level
> -properties) should be defined in a particular device's binding.
> +should be defined in a particular device's binding.
>  For more examples of cooling devices, refer to the example sections below.
>  
>  Required properties:
> @@ -69,15 +68,6 @@ For more examples of cooling devices, refer to the example sections below.
>  			See Cooling device maps section below for more details
>  			on how consumers refer to cooling devices.
>  
> -Optional properties:
> -- cooling-min-level:	An integer indicating the smallest
> -  Type: unsigned	cooling state accepted. Typically 0.
> -  Size: one cell
> -
> -- cooling-max-level:	An integer indicating the largest
> -  Type: unsigned	cooling state accepted.
> -  Size: one cell
> -
>  * Trip points
>  
>  The trip node is a node to describe a point in the temperature domain
> @@ -226,8 +216,6 @@ cpus {
>  			396000  950000
>  			198000  850000
>  		>;
> -		cooling-min-level = <0>;
> -		cooling-max-level = <3>;
>  		#cooling-cells = <2>; /* min followed by max */
>  	};
>  	...
> @@ -241,8 +229,6 @@ cpus {
>  	 */
>  	fan0: fan@48 {
>  		...
> -		cooling-min-level = <0>;
> -		cooling-max-level = <9>;
>  		#cooling-cells = <2>; /* min followed by max */
>  	};
>  };
> -- 
> 2.15.0.194.g9af6a3dea062
> 

WARNING: multiple messages have this Message-ID (diff)
From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 10/10] dt-bindings: thermal: Remove "cooling-{min|max}-level" properties
Date: Sun, 18 Feb 2018 17:29:06 -0600	[thread overview]
Message-ID: <20180218232906.jkpymin3a4qxjhnc@rob-hp-laptop> (raw)
In-Reply-To: <0ec53640f1a09e6e0d7aa1a21d1a3266c3c209c7.1518166039.git.viresh.kumar@linaro.org>

On Fri, Feb 09, 2018 at 02:28:10PM +0530, Viresh Kumar wrote:
> The "cooling-min-level" and "cooling-max-level" properties are not
> parsed by any part of kernel currently and the max cooling state of a
> CPU cooling device is found by referring to the cpufreq table instead.

What about non-CPU devices? A fan for example.

> 
> Remove the unused bindings.
> 
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
>  Documentation/devicetree/bindings/thermal/thermal.txt | 16 +---------------
>  1 file changed, 1 insertion(+), 15 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/thermal/thermal.txt b/Documentation/devicetree/bindings/thermal/thermal.txt
> index 1719d47a5e2f..cc553f0952c5 100644
> --- a/Documentation/devicetree/bindings/thermal/thermal.txt
> +++ b/Documentation/devicetree/bindings/thermal/thermal.txt
> @@ -55,8 +55,7 @@ of heat dissipation). For example a fan's cooling states correspond to
>  the different fan speeds possible. Cooling states are referred to by
>  single unsigned integers, where larger numbers mean greater heat
>  dissipation. The precise set of cooling states associated with a device
> -(as referred to by the cooling-min-level and cooling-max-level
> -properties) should be defined in a particular device's binding.
> +should be defined in a particular device's binding.
>  For more examples of cooling devices, refer to the example sections below.
>  
>  Required properties:
> @@ -69,15 +68,6 @@ For more examples of cooling devices, refer to the example sections below.
>  			See Cooling device maps section below for more details
>  			on how consumers refer to cooling devices.
>  
> -Optional properties:
> -- cooling-min-level:	An integer indicating the smallest
> -  Type: unsigned	cooling state accepted. Typically 0.
> -  Size: one cell
> -
> -- cooling-max-level:	An integer indicating the largest
> -  Type: unsigned	cooling state accepted.
> -  Size: one cell
> -
>  * Trip points
>  
>  The trip node is a node to describe a point in the temperature domain
> @@ -226,8 +216,6 @@ cpus {
>  			396000  950000
>  			198000  850000
>  		>;
> -		cooling-min-level = <0>;
> -		cooling-max-level = <3>;
>  		#cooling-cells = <2>; /* min followed by max */
>  	};
>  	...
> @@ -241,8 +229,6 @@ cpus {
>  	 */
>  	fan0: fan at 48 {
>  		...
> -		cooling-min-level = <0>;
> -		cooling-max-level = <9>;
>  		#cooling-cells = <2>; /* min followed by max */
>  	};
>  };
> -- 
> 2.15.0.194.g9af6a3dea062
> 

  reply	other threads:[~2018-02-18 23:29 UTC|newest]

Thread overview: 91+ 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 ` Viresh Kumar
2018-02-09  8:58 ` Viresh Kumar
2018-02-09  8:58 ` 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-09  8:58   ` Viresh Kumar
2018-02-13 18:16   ` Krzysztof Kozlowski
2018-02-13 18:16     ` Krzysztof Kozlowski
2018-02-09  8:58 ` [PATCH 02/10] ARM: dts: omap: " Viresh Kumar
2018-02-09  8:58   ` Viresh Kumar
2018-02-12 17:17   ` Tony Lindgren
2018-02-12 17:17     ` Tony Lindgren
2018-02-12 17:18     ` Tony Lindgren
2018-02-12 17:18       ` Tony Lindgren
2018-02-09  8:58 ` [PATCH 03/10] ARM: dts: mt7623: " Viresh Kumar
2018-02-09  8:58   ` Viresh Kumar
2018-02-09  8:58   ` Viresh Kumar
2018-02-18 23:26   ` Rob Herring
2018-02-18 23:26     ` Rob Herring
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-09  8:58   ` Viresh Kumar
2018-02-13  9:13   ` Maxime Ripard
2018-02-13  9:13     ` Maxime Ripard
2018-02-13  9:18     ` Chen-Yu Tsai
2018-02-13  9:18       ` Chen-Yu Tsai
2018-02-14  3:12       ` Viresh Kumar
2018-02-14  3:12         ` Viresh Kumar
2018-02-09  8:58 ` [PATCH 05/10] ARM64: dts: hi6220: " Viresh Kumar
2018-02-09  8:58   ` Viresh Kumar
2018-03-02 16:03   ` Wei Xu
2018-03-02 16:03     ` Wei Xu
2018-03-02 16:03     ` Wei Xu
2018-02-09  8:58 ` [PATCH 06/10] ARM64: dts: meson: " Viresh Kumar
2018-02-09  8:58   ` Viresh Kumar
2018-02-09  8:58   ` Viresh Kumar
2018-02-09  8:58   ` Viresh Kumar
2018-02-09  9:03   ` Neil Armstrong
2018-02-09  9:03     ` Neil Armstrong
2018-02-09  9:03     ` Neil Armstrong
2018-03-12  4:32     ` Viresh Kumar
2018-03-12  4:32       ` Viresh Kumar
2018-03-12  4:32       ` Viresh Kumar
2018-03-20  1:37   ` Viresh Kumar
2018-03-20  1:37     ` Viresh Kumar
2018-03-20  1:37     ` Viresh Kumar
2018-03-27 12:29     ` Arnd Bergmann
2018-03-27 12:29       ` Arnd Bergmann
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-02-09  8:58   ` Viresh Kumar
2018-02-09  8:58   ` Viresh Kumar
2018-03-12  4:35   ` Viresh Kumar
2018-03-12  4:35     ` Viresh Kumar
2018-03-20  1:43     ` Viresh Kumar
2018-03-20  1:43       ` Viresh Kumar
2018-03-20  3:10   ` Linus Walleij
2018-03-20  3:10     ` Linus Walleij
2018-03-27 12:26     ` Arnd Bergmann
2018-03-27 12:26       ` Arnd Bergmann
2018-03-27 12:29       ` Linus Walleij
2018-03-27 12:29         ` Linus Walleij
2018-02-09  8:58 ` [PATCH 08/10] ARM64: dts: meson: " Viresh Kumar
2018-02-09  8:58   ` Viresh Kumar
2018-02-09  8:58   ` Viresh Kumar
2018-02-09  9:04   ` Neil Armstrong
2018-02-09  9:04     ` Neil Armstrong
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-09  8:58   ` Viresh Kumar
2018-02-18 23:26   ` Rob Herring
2018-02-18 23:26     ` Rob Herring
2018-02-18 23:26     ` Rob Herring
2018-02-09  8:58 ` [PATCH 10/10] dt-bindings: thermal: " Viresh Kumar
2018-02-09  8:58   ` Viresh Kumar
2018-02-09  8:58   ` Viresh Kumar
2018-02-18 23:29   ` Rob Herring [this message]
2018-02-18 23:29     ` Rob Herring
2018-02-18 23:29     ` Rob Herring
2018-02-19  3:43     ` Viresh Kumar
2018-02-19  3:43       ` Viresh Kumar
2018-02-19  3:43       ` Viresh Kumar
2018-02-19 18:01       ` Rob Herring
2018-02-19 18:01         ` Rob Herring
2018-02-19 18:01         ` Rob Herring
2018-03-12  4:38   ` Viresh Kumar
2018-03-12  4:38     ` Viresh Kumar
2018-03-20 12:49     ` Zhang Rui
2018-03-20 12:49       ` Zhang Rui
2018-03-27 13:46       ` Eduardo Valentin
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=20180218232906.jkpymin3a4qxjhnc@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --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=rui.zhang@intel.com \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.