devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Punit Agrawal <punit.agrawal@arm.com>
To: edubezval@gmail.com
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	Punit Agrawal <punit.agrawal@arm.com>,
	rui.zhang@intel.com, mark.rutland@arm.com, robh+dt@kernel.org,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org
Subject: [PATCH 0/2] Update OF thermal properties for cooling-{min,max}-level
Date: Tue,  8 Sep 2015 12:16:51 +0100	[thread overview]
Message-ID: <1441711013-11220-1-git-send-email-punit.agrawal@arm.com> (raw)

Hi,

The device tree properties regarding the specification and usage of
states for cooling devices suffer from inconsistency in the bindings
as well as the usage.

The two patches here update the bindings to be consistent without
breaking existing support for the device trees already in upstream.

Thanks,
Punit

Punit Agrawal (2):
  of: thermal: Fix inconsitency between cooling-*-state and
    cooling-*-level
  of: thermal: Mark cooling-*-level properties optional

 .../devicetree/bindings/thermal/thermal.txt        | 27 +++++++++++-----------
 1 file changed, 14 insertions(+), 13 deletions(-)

-- 
2.5.0


             reply	other threads:[~2015-09-08 11:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 11:16 Punit Agrawal [this message]
2015-09-08 11:20 ` [PATCH 1/2] of: thermal: Fix inconsitency between cooling-*-state and cooling-*-level Punit Agrawal
2015-09-25 18:33   ` Rob Herring
2015-09-28  8:58     ` Punit Agrawal
     [not found] ` <1441711013-11220-1-git-send-email-punit.agrawal-5wv7dgnIgG8@public.gmane.org>
2015-09-08 11:20   ` [PATCH 2/2] of: thermal: Mark cooling-*-level properties optional Punit Agrawal
2015-09-16  8:58 ` [PATCH 0/2] Update OF thermal properties for cooling-{min,max}-level Punit Agrawal
2015-09-17 19:39 ` Rob Herring

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=1441711013-11220-1-git-send-email-punit.agrawal@arm.com \
    --to=punit.agrawal@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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).