[PATCH v2 0/2] 96boards: add thermal senor support to hikey board

From: Xinwei Kong
Date: Tue Mar 31 2015 - 02:59:33 EST


From: kongxinwei <kong.kongxinwei@xxxxxxxxxxxxx>

Thank you all for giving this v1 patches stages some comments. Here is v2
patches and address all the issues raised as part of v1 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 how to dynamically
bind the interrupt to hottest sensor.
* Delete "sensor-thres-temp" property and read thermal_zone trips points
replace of it.
* Delete "sensor-reset-temp" property and define the fixed value replace
of it.

Changes v1->v2;
* change patch's situation between binding document and driver file
* clean up some regiser for enabling thermal sensor
* use mutex lock to replace the spin lock

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

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

--
1.9.1


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/