From: Lukasz Luba <lukasz.luba@arm.com>
To: Amit Kucheria <amit.kucheria@linaro.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
swboyd@chromium.org, mka@chromium.org, daniel.lezcano@linaro.org,
Amit Kucheria <amit.kucheria@verdurent.com>,
Zhang Rui <rui.zhang@intel.com>
Cc: Rob Herring <robh@kernel.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 3/3] dt-bindings: thermal: Add yaml bindings for thermal zones
Date: Wed, 1 Apr 2020 13:26:58 +0100 [thread overview]
Message-ID: <d4b8bf55-e240-6181-4976-880846cee413@arm.com> (raw)
In-Reply-To: <af3625a9cdf1a8f0e433d67e3d785b03aae7bc82.1585738725.git.amit.kucheria@linaro.org>
Hi Amit,
Apart from small mistake during probably copy-paste (please check
below), looks good.
On 4/1/20 12:15 PM, Amit Kucheria wrote:
> As part of moving the thermal bindings to YAML, split it up into 3
> bindings: thermal sensors, cooling devices and thermal zones.
>
> The thermal-zone binding is a software abstraction to capture the
> properties of each zone - how often they should be checked, the
> temperature thresholds (trips) at which mitigation actions need to be
> taken and the level of mitigation needed at those thresholds.
>
> Signed-off-by: Amit Kucheria <amit.kucheria@linaro.org>
> Reviewed-by: Rob Herring <robh@kernel.org>
> ---
> Changes since v3:
> - Clarify example by using cooling state numbers and a comment
> - Restrict thermal-sensors to a single reference to reflect actual code
> where there is a one-to-one mapping between sensors and thermal zones
> - Add two optional properties that were missed in earlier submissions:
> coefficients and sustainable-power
> - Improve description of hysteresis and contribution properties
>
> .../bindings/thermal/thermal-zones.yaml | 341 ++++++++++++++++++
> 1 file changed, 341 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/thermal/thermal-zones.yaml
>
[snip]
> + cooling-maps {
> + map0 {
> + trip = <&cpu0_alert0>;
> + /* Corresponds to 1400MHz in OPP table */
> + cooling-device = <&CPU0 3 3>, <&CPU1 3 3>,
> + <&CPU2 3 3>, <&CPU3 3 3>;
> + };
> +
> + map1 {
> + trip = <&cpu0_alert1>;
> + /* Corresponds to 1400MHz in OPP table */
s/1400MHz/1000MHz/
1400MHZ is used in map0 as <&CPUx 3 3>, here we have '5 5'.
> + cooling-device = <&CPU0 5 5>, <&CPU1 5 5>,
> + <&CPU2 5 5>, <&CPU3 5 5>;
> + };
> + };
> + };
Apart from that, looks good:
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
Regards,
Lukasz
prev parent reply other threads:[~2020-04-01 12:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 11:15 [PATCH v4 0/3] Convert thermal bindings to yaml Amit Kucheria
2020-04-01 11:15 ` [PATCH v4 1/3] dt-bindings: thermal: Add yaml bindings for thermal sensors Amit Kucheria
2020-04-01 12:40 ` Lukasz Luba
2020-04-01 13:38 ` Amit Kucheria
2020-04-01 11:15 ` [PATCH v4 2/3] dt-bindings: thermal: Add yaml bindings for thermal cooling-devices Amit Kucheria
2020-04-01 12:34 ` Lukasz Luba
2020-04-01 11:15 ` [PATCH v4 3/3] dt-bindings: thermal: Add yaml bindings for thermal zones Amit Kucheria
2020-04-01 12:26 ` Lukasz Luba [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=d4b8bf55-e240-6181-4976-880846cee413@arm.com \
--to=lukasz.luba@arm.com \
--cc=amit.kucheria@linaro.org \
--cc=amit.kucheria@verdurent.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mka@chromium.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
--cc=swboyd@chromium.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
Powered by JetHome