devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: andy.tang@nxp.com
Cc: daniel.lezcano@linaro.org, edubezval@gmail.com,
	rui.zhang@intel.com, linux-pm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Yuantian Tang <andy.tang@nxp.com>
Subject: Re: [PATCH] dt-bindings: thermal: make cooling-maps property optional
Date: Mon, 23 Mar 2020 13:56:38 -0600	[thread overview]
Message-ID: <20200323195638.GA8059@bogus> (raw)
In-Reply-To: <20200309045411.21859-1-andy.tang@nxp.com>

On Mon,  9 Mar 2020 12:54:11 +0800, andy.tang@nxp.com wrote:
> From: Yuantian Tang <andy.tang@nxp.com>
> 
> Cooling-maps doesn't have to be a required property because there may
> be no cooling device on system, or there are no enough cooling devices for
> each thermal zone in multiple thermal zone cases since cooling devices
> can't be shared.
> So make this property optional to remove such limitations.
> 
> For thermal zones with no cooling-maps, there could be critic trips
> that can trigger CPU reset or shutdown. So they still can take actions.
> 
> Signed-off-by: Yuantian Tang <andy.tang@nxp.com>
> ---
>  Documentation/devicetree/bindings/thermal/thermal.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Acked-by: Rob Herring <robh@kernel.org>

  parent reply	other threads:[~2020-03-23 19:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-09  4:54 [PATCH] dt-bindings: thermal: make cooling-maps property optional andy.tang
2020-03-16 14:52 ` Daniel Lezcano
2020-03-16 16:13   ` Amit Kucheria
2020-03-25  6:37     ` Amit Kucheria
2020-03-25  9:08       ` Daniel Lezcano
2020-03-23 19:56 ` Rob Herring [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-05-15  9:36 [PATCH] dt-bindings: thermal: Make " Yuantian Tang
2019-05-24  2:50 ` Eduardo Valentin
2019-06-04  5:56 ` Andy Tang
2019-06-04  6:04   ` Daniel Lezcano

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=20200323195638.GA8059@bogus \
    --to=robh@kernel.org \
    --cc=andy.tang@nxp.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    /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).