From: Keerthy <j-keerthy@ti.com>
To: <rui.zhang@intel.com>, <robh+dt@kernel.org>, <daniel.lezcano@linaro.org>
Cc: <j-keerthy@ti.com>, <amit.kucheria@verdurent.com>,
<t-kristo@ti.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-pm@vger.kernel.org>, <mark.rutland@arm.com>
Subject: [PATCH v2 4/4] arm64: dts: ti: am6: Add VTM node
Date: Fri, 14 Feb 2020 12:04:43 +0530 [thread overview]
Message-ID: <20200214063443.23589-5-j-keerthy@ti.com> (raw)
In-Reply-To: <20200214063443.23589-1-j-keerthy@ti.com>
VTM stands for voltage and thermal management. Add the vtm node and
the associated thermal zones on the SoC.
Signed-off-by: Keerthy <j-keerthy@ti.com>
---
arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi
index f4227e2743f2..e7ef96b621b3 100644
--- a/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi
@@ -89,4 +89,15 @@
clocks = <&k3_clks 59 0>;
clock-names = "gpio";
};
+
+ wkup_vtm0: wkup_vtm0@42050000 {
+ compatible = "ti,am654-vtm";
+ reg = <0x42050000 0x25c>;
+ power-domains = <&k3_pds 80 TI_SCI_PD_EXCLUSIVE>;
+ #thermal-sensor-cells = <1>;
+ };
+
+ thermal_zones: thermal-zones {
+ #include "k3-am654-industrial-thermal.dtsi"
+ };
};
--
2.17.1
prev parent reply other threads:[~2020-02-14 6:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 6:34 [PATCH v2 0/4] thermal: k3: Add support for bandgap sensors Keerthy
2020-02-14 6:34 ` [PATCH v2 1/4] dt-bindings: thermal: k3: Add VTM bindings documentation Keerthy
2020-02-18 20:20 ` Rob Herring
2020-02-19 7:40 ` Keerthy
2020-02-20 20:28 ` Rob Herring
2020-02-24 1:12 ` J, KEERTHY
2020-02-14 6:34 ` [PATCH v2 2/4] thermal: k3: Add support for bandgap sensors Keerthy
2020-02-14 6:34 ` [PATCH v2 3/4] arm64: dts: ti: am654: Add thermal zones Keerthy
2020-02-14 6:34 ` Keerthy [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=20200214063443.23589-5-j-keerthy@ti.com \
--to=j-keerthy@ti.com \
--cc=amit.kucheria@verdurent.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=t-kristo@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).