From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bryan Brattlof <bb@ti.com>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Keerthy <j-keerthy@ti.com>,
Linux Thermal <linux-pm@vger.kernel.org>,
Linux Device Tree <devicetree@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 05/11] dt-bindings: thermal: k3-j72xx: elaborate on binding descriptions
Date: Wed, 12 Oct 2022 09:36:04 -0400 [thread overview]
Message-ID: <06249fe9-97eb-1ab8-5e35-00b3c613d3a7@linaro.org> (raw)
In-Reply-To: <20221011231727.8090-6-bb@ti.com>
On 11/10/2022 19:17, Bryan Brattlof wrote:
> Elaborate on the function of this device node as well as some of the
> properties that this node uses.
>
> Signed-off-by: Bryan Brattlof <bb@ti.com>
> ---
> .../bindings/thermal/ti,j72xx-thermal.yaml | 27 ++++++++++++++++++-
> 1 file changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/thermal/ti,j72xx-thermal.yaml b/Documentation/devicetree/bindings/thermal/ti,j72xx-thermal.yaml
> index c74f124ebfc00..0b6a6fa07a532 100644
> --- a/Documentation/devicetree/bindings/thermal/ti,j72xx-thermal.yaml
> +++ b/Documentation/devicetree/bindings/thermal/ti,j72xx-thermal.yaml
> @@ -9,6 +9,24 @@ title: Texas Instruments J72XX VTM (DTS) binding
> maintainers:
> - Keerthy <j-keerthy@ti.com>
>
> +description: |
> + The TI K3 family of SoCs typically have a Voltage & Thermal
> + Management (VTM) device to control up to 8 temperature diode
> + sensors to measure silicon junction temperatures from different
> + hotspots of the chip as well as provide temperature, interrupt
> + and alerting information.
> +
> + The VTM device will periodically enable these temperature sensors
> + to make a temperature measurement and store the reported data
> + allowing the sensors to stay in a reset state when not in use
> + to maximize the sensor's life.
> +
> + This VTM driver will then use the following polynomial equation to
"VTM driver" is some physical/electronic element called driver? Or Linux
driver? If the latter, drop it and just describe the equation.
> + calculate the temperature from the value stored in the VTM device.
> +
> + Temp = (-9.2627e-12) * x^4 + (6.0373e-08) * x^3 + \
> + (-1.7058e-04) * x^2 + (3.2512e-01) * x + (-4.9003e+01)
> +
> properties:
> compatible:
> enum:
> @@ -19,9 +37,16 @@ properties:
> items:
> - description: VTM cfg1 register space
> - description: VTM cfg2 register space
> - - description: VTM efuse register space
> + - description: |
> + A software trimming method must be applied to some Jacinto
> + devices to function properly. This eFuse region provides
> + the information needed for these SoCs to report
> + temperatures accurately.
>
> power-domains:
> + description: |
> + Should contain the phandle to a power management (PM) domain
> + node and the device-id of this device.
This is quite generic - why adding it?
> maxItems: 1
>
> "#thermal-sensor-cells":
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-10-12 13:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 23:17 [PATCH 00/11] enable VTM node of all TI's K3 SoCs Bryan Brattlof
2022-10-11 23:17 ` [PATCH 01/11] thermal: k3_j72xx_bandgap: simplify k3_thermal_get_temp() function Bryan Brattlof
2022-10-11 23:17 ` [PATCH 02/11] thermal: k3_j72xx_bandgap: use bool for i2128 erratum flag Bryan Brattlof
2022-10-11 23:17 ` [PATCH 03/11] thermal: k3_j72xx_bandgap: remove fuse_base from structure Bryan Brattlof
2022-10-11 23:17 ` [PATCH 04/11] thermal: k3_j72xx_bandgap: map fuse_base only for erratum workaround Bryan Brattlof
2022-10-11 23:17 ` [PATCH 05/11] dt-bindings: thermal: k3-j72xx: elaborate on binding descriptions Bryan Brattlof
2022-10-12 13:36 ` Krzysztof Kozlowski [this message]
2022-10-12 18:19 ` Bryan Brattlof
2022-10-13 23:30 ` Krzysztof Kozlowski
2022-10-11 23:17 ` [PATCH 06/11] dt-bindings: thermal: k3-j72xx: conditionally require efuse reg range Bryan Brattlof
2022-10-12 13:19 ` Rob Herring
2022-10-12 13:38 ` Krzysztof Kozlowski
2022-10-12 18:15 ` Bryan Brattlof
2022-10-12 13:39 ` Krzysztof Kozlowski
2022-10-11 23:17 ` [PATCH 07/11] arm64: dts: ti: k3-am64-main: add VTM node Bryan Brattlof
2022-10-11 23:17 ` [PATCH 08/11] arm64: dts: ti: k3-am62-wakeup: " Bryan Brattlof
2022-10-11 23:17 ` [PATCH 09/11] arm64: dts: ti: k3-j721e-mcu-wakeup: " Bryan Brattlof
2022-10-11 23:17 ` [PATCH 10/11] arm64: dts: ti: k3-j721s2-mcu-wakeup: " Bryan Brattlof
2022-10-11 23:17 ` [PATCH 11/11] arm64: dts: ti: k3-j7200-mcu-wakeup: " Bryan Brattlof
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=06249fe9-97eb-1ab8-5e35-00b3c613d3a7@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=amitk@kernel.org \
--cc=bb@ti.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--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;
as well as URLs for NNTP newsgroup(s).