From: b20788@freescale.com (Anson Huang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] thermal: imx: add clk info for thermal sensor
Date: Thu, 19 Dec 2013 13:17:25 -0500 [thread overview]
Message-ID: <1387477045-19037-3-git-send-email-b20788@freescale.com> (raw)
In-Reply-To: <1387477045-19037-1-git-send-email-b20788@freescale.com>
thermal sensor needs dedicated clock to work in correct way,
so we need to add necessary clock info in dts.
Signed-off-by: Anson Huang <b20788@freescale.com>
---
.../devicetree/bindings/thermal/imx-thermal.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/thermal/imx-thermal.txt b/Documentation/devicetree/bindings/thermal/imx-thermal.txt
index 541c25e..e518c6e 100644
--- a/Documentation/devicetree/bindings/thermal/imx-thermal.txt
+++ b/Documentation/devicetree/bindings/thermal/imx-thermal.txt
@@ -7,6 +7,7 @@ Required properties:
- fsl,tempmon-data : phandle pointer to fuse controller that contains TEMPMON
calibration data, e.g. OCOTP on imx6q. The details about calibration data
can be found in SoC Reference Manual.
+- clocks : thermal sensor's clock source.
Example:
@@ -14,4 +15,5 @@ tempmon {
compatible = "fsl,imx6q-tempmon";
fsl,tempmon = <&anatop>;
fsl,tempmon-data = <&ocotp>;
+ clocks = <&clks 172>;
};
--
1.7.9.5
next prev parent reply other threads:[~2013-12-19 18:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 18:17 [PATCH 1/3] ARM: dts: imx6qdl: add necessary thermal clk Anson Huang
2013-12-19 7:06 ` Shawn Guo
2013-12-19 18:17 ` [PATCH 2/3] thermal: imx: add necessary clk operation Anson Huang
2013-12-19 6:24 ` Baruch Siach
2013-12-19 6:52 ` Anson.Huang at freescale.com
2013-12-19 6:59 ` Shawn Guo
2013-12-19 7:08 ` Anson.Huang at freescale.com
2013-12-19 7:29 ` Shawn Guo
2013-12-19 7:33 ` Anson.Huang at freescale.com
2013-12-19 18:17 ` Anson Huang [this message]
2013-12-19 6:57 ` [PATCH 3/3] thermal: imx: add clk info for thermal sensor Shawn Guo
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=1387477045-19037-3-git-send-email-b20788@freescale.com \
--to=b20788@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).