devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xinwei Kong <kong.kongxinwei@hisilicon.com>
To: rui.zhuang@intel.com, edubezval@gmail.com, mporter@konsulko.com,
	jorge.ramirez-ortiz@linaro.org, haojian.zhuang@linaro.org,
	linux-pm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linuxarm@huawei.com,
	devicetree@vger.kernel.org, liguozhu@hisilicon.com,
	xuwei5@hisilicon.com
Subject: [PATCH v3 1/2] dt-bindings: Document the hi6220 thermal sensor bindings
Date: Tue, 7 Apr 2015 18:40:51 +0800	[thread overview]
Message-ID: <1428403252-8208-2-git-send-email-kong.kongxinwei@hisilicon.com> (raw)
In-Reply-To: <1428403252-8208-1-git-send-email-kong.kongxinwei@hisilicon.com>

From: kongxinwei <kong.kongxinwei@hisilicon.com>

This adds documentation of device tree bindings for the
thermal sensor controller of hi6220 SoC.

Signed-off-by: Leo Yan <leo.yan@linaro.org>
Signed-off-by: kongxinwei <kong.kongxinwei@hisilicon.com>
---
 .../bindings/thermal/hisilicon-thermal.txt         | 23 ++++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/thermal/hisilicon-thermal.txt

diff --git a/Documentation/devicetree/bindings/thermal/hisilicon-thermal.txt b/Documentation/devicetree/bindings/thermal/hisilicon-thermal.txt
new file mode 100644
index 0000000..b2a349f
--- /dev/null
+++ b/Documentation/devicetree/bindings/thermal/hisilicon-thermal.txt
@@ -0,0 +1,23 @@
+* Temperature Sensor on hisilicon SoCs
+
+** Required properties :
+
+- compatible: "hisilicon,tsensor".
+- reg: physical base address of thermal sensor and length of memory mapped
+  region.
+- interrupt: The interrupt number to the cpu. Defines the interrupt used
+  by SOCTHERM.
+- clock-names: Input clock name, should be 'thermal_clk'.
+- clocks: phandles for clock specified in "clock-names" property.
+- #thermal-sensor-cells: Should be 1. See ./thermal.txt for a description.
+
+Example :
+
+	tsensor: tsensor@0,f7030700 {
+		compatible = "hisilicon,tsensor";
+		reg = <0x0 0xf7030700 0x0 0x1000>;
+		interrupts = <0 7 0x4>;
+		clocks = <&clock_sys HI6220_TSENSOR_CLK>;
+		clock-names = "thermal_clk";
+		#thermal-sensor-cells = <1>;
+	}
-- 
1.9.1



  reply	other threads:[~2015-04-07 10:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 10:40 [PATCH v3 0/2] 96boards: add thermal senor support to hikey board Xinwei Kong
2015-04-07 10:40 ` Xinwei Kong [this message]
2015-04-07 10:40 ` [PATCH v3 2/2] thermal: hisilicon: add new hisilicon thermal sensor driver Xinwei Kong
2015-04-21  9:09   ` 答复: " Wangfei (William, Euler)
2015-04-21  9:15     ` Wangfei (William, Euler)
     [not found]     ` <62D2F9B90E00B742A0ABA02CC88C65EA298E4D81-tJwL4pWccCbk2xaCPkHFjwK1hpo4iccwjNknBlVQO8k@public.gmane.org>
2015-04-22  5:47       ` Xinwei Kong

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=1428403252-8208-2-git-send-email-kong.kongxinwei@hisilicon.com \
    --to=kong.kongxinwei@hisilicon.com \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=haojian.zhuang@linaro.org \
    --cc=jorge.ramirez-ortiz@linaro.org \
    --cc=liguozhu@hisilicon.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mporter@konsulko.com \
    --cc=rui.zhuang@intel.com \
    --cc=xuwei5@hisilicon.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).