From: Eduardo Valentin <edubezval@gmail.com>
To: Narendran Rajan <nrajan@codeaurora.org>
Cc: Zhang Rui <rui.zhang@intel.com>,
Linux ARM MSM <linux-arm-msm@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: document qcom tsens thermal
Date: Thu, 29 Jan 2015 18:35:52 -0400 [thread overview]
Message-ID: <20150129223550.GC29837@developer.amazonguestwifi.org> (raw)
In-Reply-To: <1422331687-19535-1-git-send-email-nrajan@codeaurora.org>
On Mon, Jan 26, 2015 at 08:08:07PM -0800, Narendran Rajan wrote:
> Add binding documentation for the QCOM tsens device tree node
> ---
> .../devicetree/bindings/thermal/qcom-thermal.txt | 58 ++++++++++++++++++++++
> 1 file changed, 58 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/thermal/qcom-thermal.txt
>
> diff --git a/Documentation/devicetree/bindings/thermal/qcom-thermal.txt b/Documentation/devicetree/bindings/thermal/qcom-thermal.txt
> new file mode 100644
> index 0000000..d2e99d6
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/thermal/qcom-thermal.txt
> @@ -0,0 +1,58 @@
> +* QCOM SoC Temperature Sensor (TSENS)
> +
> +Required properties:
> +- compatible : "qcom,ipq806x-tsens"
> +- interrupts : The interrupt number to the cpu. The interrupt specifier format
> + depends on the interrupt controller.
> +- qcom,imem : Must contain phandle to imem syscon node
> +- qcom,tsens-base : Must contain phandle to clock controller node
> +- qcom,calib-offsets : Must contain offsets to primary and secondary
> + calibration data within imem
> +- qcom,tsens-slopes : Must contain slope value for each of the sensors controlled
> + by this device
Can you please check if the above two properties can be mapped into the
'coefficients' property? It is an optional property of the thermal zone
node.
Check Documentation/devicetree/bindings/thermal/thermal.txt
However, it might require additional implementation in the of thermal
code, as we still have not got that done in any other driver.
My concern here is to avoid adding specific DT entries while we already
defined generic options that can be used.
> +- #thermal-sensor-cells : Should be 1. See ./thermal.txt for a description.
> +
> +Exiample:
s/Exiample/Example/g
> +tsens: tsens-msm8960 {
> + compatible = "qcom,ipq806x-tsens";
> + interrupts = <0 178 1>;
> + qcom,imem = <&imem>;
> + qcom,tsens-base = <&gcc>;
> + qcom,calib-offsets = <0x400 0x410>;
> + qcom,tsens-slopes = <1176 1176 1154 1176 1111
> + 1132 1132 1199 1132 1199
> + 1132>;
> + #thermal-sensor-cells = <1>;
> + };
> +
> +Example: referring to thermal sensors:
> +thermal-zones {
> + cpu_thermal: cpu_thermal {
> + polling-delay-passive = <1000>; /* milliseconds */
> + polling-delay = <5000>; /* milliseconds */
> +
> + /* sensor ID */
> + thermal-sensors = <&tsens 1>;
> +
Something like:
coefficients = <[slope] [offset]>;
> + trips {
> + cpu_alert0: cpu_alert {
> + temperature = <80000>; /* millicelsius */
> + hysteresis = <2000>; /* millicelsius */
> + type = "passive";
> + };
> + cpu_crit: cpu_crit {
> + temperature = <120000>; /* millicelsius */
> + hysteresis = <2000>; /* millicelsius */
> + type = "critical";
> + };
> + };
> +
> + cooling-maps {
> + map0 {
> + trip = <&cpu_alert0>;
> + cooling-device =
> + <&cpu0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
> + };
> + };
> + };
> +};
> --
> Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
>
prev parent reply other threads:[~2015-01-29 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 4:08 [PATCH] dt-bindings: document qcom tsens thermal Narendran Rajan
2015-01-27 7:15 ` Srinivas Kandagatla
2015-01-27 19:44 ` Narendran Rajan
2015-01-29 6:06 ` Srinivas Kandagatla
2015-01-29 22:29 ` Eduardo Valentin
2015-01-29 18:02 ` Lina Iyer
2015-01-29 22:35 ` Eduardo Valentin [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=20150129223550.GC29837@developer.amazonguestwifi.org \
--to=edubezval@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nrajan@codeaurora.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).