From: "J, KEERTHY" <j-keerthy@ti.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<daniel.lezcano@linaro.org>, <rui.zhang@intel.com>,
<amitk@kernel.org>, <kristo@kernel.org>
Cc: <rafael@kernel.org>, <linux-pm@vger.kernel.org>,
<vigneshr@ti.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v8 1/2] dt-bindings: thermal: k3-j72xx: Add VTM bindings documentation
Date: Tue, 17 May 2022 20:37:17 +0530 [thread overview]
Message-ID: <324bd9c8-06b4-b9f5-7213-0e4b2a50653b@ti.com> (raw)
In-Reply-To: <03c0e4fa-ccfb-fd86-0899-92a1086cac09@linaro.org>
On 5/17/2022 8:08 PM, Krzysztof Kozlowski wrote:
> On 17/05/2022 14:14, Keerthy wrote:
>> Add VTM bindings documentation. In the Voltage Thermal
>> Management Module(VTM), K3 J72XX supplies a voltage
>> reference and a temperature sensor feature that are gathered in the band
>> gap voltage and temperature sensor (VBGAPTS) module. The band
>> gap provides current and voltage reference for its internal
>> circuits and other analog IP blocks. The analog-to-digital
>> converter (ADC) produces an output value that is proportional
>> to the silicon temperature.
>>
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>
> It seems I am repeating myself... Tags are still missing...
I still do not have a Reviewed-by from you. Should i add yours?
You are still giving additional comments so I did not add.
>
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/soc/ti,sci_pm_domain.h>
>> + wkup_vtm0: thermal-sensor@42040000 {
>> + compatible = "ti,j721e-vtm";
>> + reg = <0x42040000 0x350>,
>> + <0x42050000 0x350>,
>> + <0x43000300 0x10>;
>
> Please align the continued entries with opening <.
Okay. I will fix that.
>
>> + power-domains = <&k3_pds 154 TI_SCI_PD_EXCLUSIVE>;
>> + #thermal-sensor-cells = <1>;
>> + };
>> +
>> + mpu_thermal: mpu-thermal {
>> + polling-delay-passive = <250>; /* milliseconds */
>> + polling-delay = <500>; /* milliseconds */
>> + thermal-sensors = <&wkup_vtm0 0>;
>> +
>> + trips {
>> + mpu_crit: mpu-crit {
>
> You still have here incorrect/inconsistent indentation. Entire DTS
> example goes usually with 4 spaces.
Okay.
>
>> + temperature = <125000>; /* milliCelsius */
>> + hysteresis = <2000>; /* milliCelsius */
>> + type = "critical";
>> + };
>> + };
>> + };
>> +...
>
>
Thanks,
Keerthy
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2022-05-17 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 12:14 [PATCH v8 0/2] thermal: k3_j72xx_bandgap: Add the bandgap driver support Keerthy
2022-05-17 12:14 ` [PATCH v8 1/2] dt-bindings: thermal: k3-j72xx: Add VTM bindings documentation Keerthy
2022-05-17 14:38 ` Krzysztof Kozlowski
2022-05-17 15:07 ` J, KEERTHY [this message]
2022-05-17 15:15 ` Krzysztof Kozlowski
2022-05-17 12:14 ` [PATCH v8 2/2] thermal: k3_j72xx_bandgap: Add the bandgap driver support 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=324bd9c8-06b4-b9f5-7213-0e4b2a50653b@ti.com \
--to=j-keerthy@ti.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=vigneshr@ti.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