From: Eduardo Valentin <edubezval@gmail.com>
To: Xinwei Kong <kong.kongxinwei@hisilicon.com>
Cc: Matt Porter <mporter@konsulko.com>,
rui.zhuang@intel.com, mark.rutland@arm.com,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
linuxarm@huawei.com, xuwei5@hisilicon.com,
linux-kernel@vger.kernel.org, jorge.ramirez-ortiz@linaro.org,
xweikong@hotmail.com, liguozhu@hisilicon.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] dt-bindings: Document the hi6220 thermal sensor bindings
Date: Mon, 6 Apr 2015 21:27:28 -0700 [thread overview]
Message-ID: <20150407042727.GA30242@localhost.localdomain> (raw)
In-Reply-To: <5523530E.3000400@hisilicon.com>
[-- Attachment #1: Type: text/plain, Size: 4385 bytes --]
On Tue, Apr 07, 2015 at 11:46:22AM +0800, Xinwei Kong wrote:
>
>
> On 2015/4/6 22:03, Matt Porter wrote:
> > On Tue, Mar 31, 2015 at 02:59:21PM +0800, Xinwei Kong wrote:
> >> 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 | 45 ++++++++++++++++++++++
> >> 1 file changed, 45 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..ceb6e2e
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/thermal/hisilicon-thermal.txt
> >> @@ -0,0 +1,45 @@
> >> +* Hisilicon Thermal
> >> +
> >> +This driver is for hi6220 SoC which contain 4 thermal sensor.
> >> +
> >> + 1. sensor 0: local sensor;
> >> + 2. sensor 1: remote sensor for ACPU cluster 1;
> >> + 3. sensor 2: remote sensor for ACPU cluster 2;
> >> + 4. sensor 3: remote sensor for GPU.
> >> +
> >> +Every sensor use one child node to represent it, so thermal sensor include
> >> +parent node and four child node. The parent node describe common feature and
> >> +child node describe private feature for thermal sensor;
> >> +
> >> +** 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.
> >> +
> >> +** Required properties for child nodes :
> >> +
> >> +- hisilicon,tsensor-id: the index of thermal sensor and use it to distinguish
> >> + thermal sensor. For example: <0> stands for local sensor; <1> stands for
> >> + acpu1 sensor;
> >
> > Please show an example illustrating why this property is needed. The
> > example below doesn't show any per sensor properties aside from the
> > sensor id. Other bindings with a similar sub-sensor hardware design like
> > tegra-soctherm and rockchip-thermal don't have a need for a vendor
> > specific property like this. Their drivers simply iterate over an id
> > index during thermal sensor registration.
> >
> > -Matt
> >
> Thermal Ip of hisilicon SoC can get four module temperature--local sensor, ACPU0
> sensor, ACPU1 sensor and gpu sensor. In order to use these sensors, this driver
> will make use of sensor id to distinguish sensor in using process.
>
> These four sensors only get one sensor temperature at the same times. Because
> these sensor commonly use the same register by setting diff value to enable one
> sensor. howerver, sensor id is key flag for these diff sensor modules.
>
> If deleting sensor id, this driver will define some value which set diff sensor
> regitser and it difficult to understand sensor register operation.
The above still do not explain why you need a specific property.
Could you please check
Documentation/devicetree/bindings/thermal/thermal.txt file?
There are several examples there on how to define DT nodes for the exact
case you describe above.
>
> Thanks
> Xinwei
>
> >> +
> >> +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>;
> >> +
> >> + local_sensor {
> >> + hisilicon,tsensor-id = <0>;
> >> + }
> >> + .......
> >> + }
> >> --
> >> 1.9.1
> >>
> >>
> >>
> >> _______________________________________________
> >> linux-arm-kernel mailing list
> >> linux-arm-kernel@lists.infradead.org
> >> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> >
> > .
> >
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2015-04-07 4:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 6:59 [PATCH v2 0/2] 96boards: add thermal senor support to hikey board Xinwei Kong
2015-03-31 6:59 ` [PATCH v2 1/2] dt-bindings: Document the hi6220 thermal sensor bindings Xinwei Kong
[not found] ` <1427785162-15172-2-git-send-email-kong.kongxinwei-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2015-04-06 14:03 ` Matt Porter
2015-04-07 3:46 ` Xinwei Kong
2015-04-07 4:27 ` Eduardo Valentin [this message]
[not found] ` <20150407042727.GA30242-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-04-07 7:06 ` Xinwei Kong
2015-03-31 6:59 ` [PATCH v2 2/2] thermal: hisilicon: add new hisilicon thermal sensor driver 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=20150407042727.GA30242@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jorge.ramirez-ortiz@linaro.org \
--cc=kong.kongxinwei@hisilicon.com \
--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=mark.rutland@arm.com \
--cc=mporter@konsulko.com \
--cc=rui.zhuang@intel.com \
--cc=xuwei5@hisilicon.com \
--cc=xweikong@hotmail.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).