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, kong.kongxinwei@hisilicon.com
Cc: linux-pm@vger.kernel.org, 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 v1 0/2] 96boards: add thermal senor support to hikey board
Date: Wed, 25 Mar 2015 15:50:23 +0800	[thread overview]
Message-ID: <1427269825-11324-1-git-send-email-kong.kongxinwei@hisilicon.com> (raw)

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

Thank you all for giving this RFC patches stages some comments. Here is v1
patches and address all the issues raised as part of RFC review.

The Linaro connect introduce 96boards series in Hong Kong,The HiKey board
is the first board to be certified 96Boards Consumer Edition compatible.
This board is based on the HiSilicon SoC. you can get more information
from https://www.96boards.org.

The hisilicon SoC contains thermal module, this thermal module has 4 sensors,

	- sensor 0: local sensor;
	- sensor 1: remote sensor for ACPU cluster 1;
	- sensor 2: remote sensor for ACPU cluster 2;
	- sensor 3: remote sensor for GPU;

It can obtain this device temperature by operating this hardware. The new
sensor driver satisfies thermal framework and to realize the ACPU ,GPU and
so on to cool function.

Changes v0->v1;
* Delete this hi6220 dtsi.
* Fix documentation and error checks.
* Modify this driver which makes use of kernel to decide dynamically bind
  the interrupt to hottest sensor.
* Delete "sensor-thres-temp" property in DTS and write thermal_zone trips
  points value to register.
* Delete "sensor-reset-temp" property and define the fixed value.

kongxinwei (2):
  thermal: hisilicon: add new hisilicon thermal sensor driver
  dt-bindings: Document the hi6220 thermal sensor bindings

 .../bindings/thermal/hisilicon-thermal.txt         |  45 ++
 drivers/thermal/Kconfig                            |   8 +
 drivers/thermal/Makefile                           |   1 +
 drivers/thermal/hisi_thermal.c                     | 526 +++++++++++++++++++++
 4 files changed, 580 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/thermal/hisilicon-thermal.txt
 create mode 100644 drivers/thermal/hisi_thermal.c

-- 
1.9.1



             reply	other threads:[~2015-03-25  7:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25  7:50 Xinwei Kong [this message]
2015-03-25  7:50 ` [PATCH v1 1/2] thermal: hisilicon: add new hisilicon thermal sensor driver Xinwei Kong
2015-03-26  9:14   ` YiPing Xu
2015-03-27  8:30     ` Xinwei Kong
2015-03-28  0:58       ` YiPing Xu
2015-03-28 16:00         ` Xinwei Kong
2015-03-28 16:01         ` Xinwei Kong
2015-03-25  7:50 ` [PATCH v1 2/2] dt-bindings: Document the hi6220 thermal sensor bindings 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=1427269825-11324-1-git-send-email-kong.kongxinwei@hisilicon.com \
    --to=kong.kongxinwei@hisilicon.com \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.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=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).