From: Laxman Dewangan <ldewangan@nvidia.com>
To: Keerthy <a0393675@ti.com>,
edubezval@gmail.com, rui.zhang@intel.com, robh+dt@kernel.org
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 1/2] thermal: max77620: Add DT binding doc for thermal driver
Date: Tue, 7 Jun 2016 12:08:23 +0530 [thread overview]
Message-ID: <57566BDF.3090100@nvidia.com> (raw)
In-Reply-To: <575645B8.5090709@ti.com>
On Tuesday 07 June 2016 09:25 AM, Keerthy wrote:
>
>
> On Monday 06 June 2016 05:14 PM, Laxman Dewangan wrote:
>> Maxim Semiconductor MAX77620 supports alarm interrupts when
>> its die temperature crosses 120C and 140C. These threshold
>> temperatures are not configurable.
>>
>> Add DT binding document to details out the DT property related
>> to MAX77620 thermal functionality.
>>
>> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
>> ---
>> .../bindings/thermal/thermal-max77620.txt | 64
>> ++++++++++++++++++++++
>> 1 file changed, 64 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/thermal/thermal-max77620.txt
>>
>> diff --git
>> a/Documentation/devicetree/bindings/thermal/thermal-max77620.txt
>> b/Documentation/devicetree/bindings/thermal/thermal-max77620.txt
>> new file mode 100644
>> index 0000000..5a500d5
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/thermal/thermal-max77620.txt
>> @@ -0,0 +1,64 @@
>> +Thermal driver for MAX77620 Power management IC from Maxim
>> Semiconductor.
>> +
>> +Maxim Semiconductor MAX77620 supports alarm interrupts when its
>> +die temperature crosses 120C and 140C. These threshold temperatures
>> +are not configurable. Device does not provide the real temperature
>> +of die other than just indicating whether temperature is above or
>> +below threshold level.
>> +
>> +Required properties:
>> +-------------------
>> +#thermal-sensor-cells: Please refer
>> <devicetree/bindings/thermal/thermal.txt>
>> + for more details.
>> + The value must be 0.
>> +
>> +For more details, please refer generic thermal DT binding document
>> +<devicetree/bindings/thermal/thermal.txt>.
>> +
>> +Please refer <devicetree/bindings/mfd/max77620.txt> for mfd DT binding
>> +document for the MAX77620.
>> +
>> +Example:
>> +--------
>> +#include <dt-bindings/mfd/max77620.h>
>> +#include <dt-bindings/thermal/thermal.h>
>> +...
>> +
>> +i2c@7000d000 {
>> + spmic: max77620@3c {
>> + compatible = "maxim,max77620";
>> + :::::
>> + #thermal-sensor-cells = <0>;
>> + :::
>> + };
>> +};
>> +
>> +cool_dev: cool-dev {
>> + compatible = "cooling-dev";
>> + #cooling-cells = <2>;
>> +};
>> +
>> +thermal-zones {
>> + PMIC-Die {
>> + polling-delay = <0>;
>> + polling-delay-passive = <0>;
>> + thermal-sensors = <&spmic>;
>> +
>> + trips {
>> + die_temp_thresh: hot-die {
>> + temperature = <120000>;
>> + type = "active";
>> + hysteresis = <0>;
>> + };
>> + };
>
> What about 140C? Isn't that a critical trip point?
Yes, it is there and it can be populated/extended on the same way and
handled.
This is just an example.
>
>> +
>> + cooling-maps {
>> + map0 {
>> + trip = <&die_temp_thresh>;
>> + cooling-device = <&cool_dev THERMAL_NO_LIMIT
>> + THERMAL_NO_LIMIT>;
>> + contribution = <100>;
>> + };
>> + };
>> + };
>> +};
>>
next prev parent reply other threads:[~2016-06-07 6:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 11:44 [PATCH V3 1/2] thermal: max77620: Add DT binding doc for thermal driver Laxman Dewangan
2016-06-06 11:44 ` [PATCH V3 2/2] thermal: max77620: Add thermal driver for reporting junction temp Laxman Dewangan
2016-06-07 3:48 ` Keerthy
2016-06-07 6:35 ` Laxman Dewangan
2016-06-07 3:55 ` [PATCH V3 1/2] thermal: max77620: Add DT binding doc for thermal driver Keerthy
2016-06-07 6:38 ` Laxman Dewangan [this message]
2016-06-07 7:47 ` Keerthy
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=57566BDF.3090100@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=a0393675@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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).