From: Rob Herring <robh@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: daniel.lezcano@linaro.org, rui.zhang@intel.com,
amit.kucheria@verdurent.com, Mark Rutland <mark.rutland@arm.com>,
"open list:THERMAL" <linux-pm@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/4] dt-bindings: thermal: Add the idle cooling device
Date: Tue, 14 Apr 2020 16:45:09 -0500 [thread overview]
Message-ID: <20200414214509.GA10673@bogus> (raw)
In-Reply-To: <20200414162634.1867-2-daniel.lezcano@linaro.org>
On Tue, 14 Apr 2020 18:26:27 +0200, Daniel Lezcano wrote:
> Some devices are not able to cool down by reducing their voltage /
> frequency because it could be not available or the system does not
> allow voltage scaling. In this configuration, it is not possible to
> use this strategy and the idle injection cooling device can be used
> instead.
>
> One idle cooling device is now present for the CPU as implemented by
> the combination of the idle injection framework belonging to the power
> capping framework and the thermal cooling device. The missing part is
> the DT binding providing a way to describe how the cooling device will
> work on the system.
>
> A first iteration was done by making the cooling device to point to
> the idle state. Unfortunately it does not make sense because it would
> need to duplicate the idle state description for each CPU in order to
> have a different phandle and make the thermal internal framework
> happy.
>
> It was proposed to add an cooling-cells to <3>, unfortunately the
> thermal framework is expecting a value of <2> as stated by the
> documentation and it is not possible from the cooling device generic
> code to loop this third value to the back end cooling device.
>
> Another proposal was to add a child 'thermal-idle' node as the SCMI
> does. This approach allows to have a self-contained configuration for
> the idle cooling device without colliding with the cpufreq cooling
> device which is based on the CPU node. In addition, it allows to have
> the cpufreq cooling device and the idle cooling device to co-exist
> together as shown in the example.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> ---
> - V2:
> - Fixed comment type
> - Added dual license
> - Fixed description s/begins to/should/
> - Changed name s/duration/duration-us/
> - Changed name s/latency/exit-latency-us/
> - Removed types for latency / duration
> - Fixed s/idle-thermal/thermal-idle/
> ---
> .../bindings/thermal/thermal-idle.yaml | 146 ++++++++++++++++++
> 1 file changed, 146 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/thermal/thermal-idle.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
Documentation/devicetree/bindings/thermal/thermal-idle.yaml: while scanning a block scalar
in "<unicode string>", line 39, column 20
found a tab character where an indentation space is expected
in "<unicode string>", line 44, column 1
Documentation/devicetree/bindings/Makefile:12: recipe for target 'Documentation/devicetree/bindings/thermal/thermal-idle.example.dts' failed
make[1]: *** [Documentation/devicetree/bindings/thermal/thermal-idle.example.dts] Error 1
make[1]: *** Waiting for unfinished jobs....
warning: no schema found in file: Documentation/devicetree/bindings/thermal/thermal-idle.yaml
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/thermal/thermal-idle.yaml: ignoring, error parsing file
Makefile:1264: recipe for target 'dt_binding_check' failed
make: *** [dt_binding_check] Error 2
See https://patchwork.ozlabs.org/patch/1270492
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure dt-schema is up to date:
pip3 install git+https://github.com/devicetree-org/dt-schema.git@master --upgrade
Please check and re-submit.
next prev parent reply other threads:[~2020-04-14 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 16:26 [PATCH v2 1/4] powercap/drivers/idle_inject: Specify idle state max latency Daniel Lezcano
2020-04-14 16:26 ` [PATCH v2 2/4] dt-bindings: thermal: Add the idle cooling device Daniel Lezcano
2020-04-14 21:45 ` Rob Herring [this message]
2020-04-14 21:49 ` Daniel Lezcano
2020-04-14 16:26 ` [PATCH v2 3/4] thermal/drivers/cpuidle_cooling: Change the registration function Daniel Lezcano
2020-04-14 16:26 ` [PATCH v2 4/4] thermal: cpuidle: Register cpuidle cooling device Daniel Lezcano
2020-04-14 16:26 ` 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=20200414214509.GA10673@bogus \
--to=robh@kernel.org \
--cc=amit.kucheria@verdurent.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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 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.