public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Caesar Wang <wxt@rock-chips.com>
Cc: edubezval@gmail.com, dianders@chromium.org,
	briannorris@google.com, smbarber@google.com,
	linux-rockchip@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Jianqun Xu <jay.xu@rock-chips.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] ARM64: dts: rockchip: add thermal zone node for rk3399 SoCs
Date: Tue, 07 Jun 2016 16:33:49 +0200	[thread overview]
Message-ID: <2777347.d7vA3TK9Oa@diego> (raw)
In-Reply-To: <1464161975-31299-1-git-send-email-wxt@rock-chips.com>

Am Mittwoch, 25. Mai 2016, 15:39:35 schrieb Caesar Wang:
> This adds thermal zone node to rk3399 dtsi, rk3399 thermal data is
> including the cpu and gpu sensor zone node.
> 
> The thermal zone node is the node containing all the required info
> for describing a thermal zone, including its cooling device bindings.
> The thermal zone node must contain, apart from its own properties, one
> sub-node containing trip nodes and one sub-node containing all the zone
> cooling maps.
> 
> The following is the parameter is introduced:
> * polling-delay:
> The maximum number of milliseconds to wait between polls
> 
> * polling-delay-passive:
> The maximum number of milliseconds to wait between polls when performing
> passive cooling.
> 
> * trips:
> A sub-node which is a container of only trip point nodes required to
> describe the thermal zone.
> 
> * cooling-maps:
> A sub-node which is a container of only cooling device map nodes, used to
> describe the relation between trips and cooling devices.
> 
> * cooling-device:
> A phandle of a cooling device with its specifier, referring to which
> cooling device is used in this cooling specifier binding. In the cooling
> specifier, the first cell is the minimum cooling state and the second cell
> is the maximum cooling state used in this map.
> 
> Signed-off-by: Caesar Wang <wxt@rock-chips.com>

applied to my dts64 branch for 4.8.
I've dropped all the milliseconds etc comments though. They're part of the 
binding, so no need to document the unit in the dts all the time :-)


Thanks
Heiko

      reply	other threads:[~2016-06-07 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25  7:39 [RESEND PATCH] ARM64: dts: rockchip: add thermal zone node for rk3399 SoCs Caesar Wang
2016-06-07 14:33 ` Heiko Stübner [this message]

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=2777347.d7vA3TK9Oa@diego \
    --to=heiko@sntech.de \
    --cc=briannorris@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=edubezval@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jay.xu@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=smbarber@google.com \
    --cc=will.deacon@arm.com \
    --cc=wxt@rock-chips.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