qcom: Add support for TSENS driver
Subsystems (7)
v4 cover qcom: Add support for TSENS driver
Patches 1/8 to 4/8 will need to go via the thermal tree/Eduardo. Patches 5/8 to 8/8 will need to go via qcom-msm tree/Andy.
Eduardo, can you please take a look at the patches and let me know if you see any issues.
Current set of patches apply on 4.3-rc4. Need to pull in clk-next (for a dependent patch) to be able to test on ifc6410 board.
Changes since v3:
* Dropped 'clk: qcom: create virtual child device for TSENS' which is picked up by Stephen
* Updated GCC bindings with optional TSENS properties
Changes since v2:
* Minor review fixes from Stephen/Punit and rebase on 4.3-rc4
Changes since v1:
* Created virtual tsens device from gcc driver for 8960, with DT having a single node for gcc and tsens
* Minor fixes with rebasing on 4.3-rc1
Changes since RFC:
* Added support for 8916 and 8084
* Based off the latest nvmem framework patches [1]
* Minor review fixes for comments mostly from Lina
This is an attempt to have a single TSENS driver for the different versions of the TSENS IP that exist, on different qcom msm/apq SoCs'
Support is added for msm8916, msm8960 and msm8974 families.
A lot of the work is based of original code from Stephen Boyd and Siddartha Mohanadoss. I have also picked some of what Narendran Rajan did in his attempt to upstream the support for 8960 family. I could not keep the original authorship on any of the patches because I ended up moving the code around quite a bit in an effort to have a single driver for the various devices. I would be glad to change the authorship for any of the patches if needed.
Rajendra Nayak (8):
thermal: qcom: tsens: Add a skeletal TSENS drivers
thermal: qcom: tsens-8916: Add support for 8916 family of SoCs
thermal: qcom: tsens-8974: Add support for 8974 family of SoCs
thermal: qcom: tsens-8960: Add support for 8960 family of SoCs
arm: dts: msm8974: Add thermal zones, tsens and qfprom nodes
arm: dts: apq8064: Add thermal zones, tsens and qfprom nodes
arm: dts: apq8084: Add thermal zones, tsens and qfprom nodes
arm64: dts: msm8916: Add thermal zones, tsens and qfprom nodes
.../devicetree/bindings/clock/qcom,gcc.txt | 20 ++ .../devicetree/bindings/thermal/qcom-tsens.txt | 33 +++ arch/arm/boot/dts/qcom-apq8064.dtsi | 101 +++++++ arch/arm/boot/dts/qcom-apq8084.dtsi | 105 ++++++++ arch/arm/boot/dts/qcom-msm8974.dtsi | 105 ++++++++ arch/arm64/boot/dts/qcom/msm8916.dtsi | 66 +++++ drivers/thermal/Kconfig | 5 + drivers/thermal/Makefile | 1 + drivers/thermal/qcom/Kconfig | 10 + drivers/thermal/qcom/Makefile | 2 + drivers/thermal/qcom/tsens-8916.c | 107 ++++++++ drivers/thermal/qcom/tsens-8960.c | 291 +++++++++++++++++++++ drivers/thermal/qcom/tsens-8974.c | 239 +++++++++++++++++ drivers/thermal/qcom/tsens-common.c | 130 +++++++++ drivers/thermal/qcom/tsens.c | 206 +++++++++++++++ drivers/thermal/qcom/tsens.h | 69 +++++ 16 files changed, 1490 insertions(+) create mode 100644 Documentation/devicetree/bindings/thermal/qcom-tsens.txt create mode 100644 drivers/thermal/qcom/Kconfig create mode 100644 drivers/thermal/qcom/Makefile create mode 100644 drivers/thermal/qcom/tsens-8916.c create mode 100644 drivers/thermal/qcom/tsens-8960.c create mode 100644 drivers/thermal/qcom/tsens-8974.c create mode 100644 drivers/thermal/qcom/tsens-common.c create mode 100644 drivers/thermal/qcom/tsens.c create mode 100644 drivers/thermal/qcom/tsens.h
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 1/8 thermal: qcom: tsens: Add a skeletal TSENS drivers
TSENS is Qualcomms' thermal temperature sensor device. It supports reading temperatures from multiple thermal sensors present on various QCOM SoCs.
Calibration data is generally read from a non-volatile memory (eeprom) device.
Add a skeleton driver with all the necessary abstractions so a variety of qcom device families which support TSENS can add driver extensions.
Also add the required device tree bindings which can be used to describe the TSENS device in DT.
--- .../devicetree/bindings/thermal/qcom-tsens.txt | 33 ++++ drivers/thermal/Kconfig | 5 + drivers/thermal/Makefile | 1 + drivers/thermal/qcom/Kconfig | 10 ++ drivers/thermal/qcom/Makefile | 2 + drivers/thermal/qcom/tsens.c | 199 +++++++++++++++++++++ drivers/thermal/qcom/tsens.h | 58 ++++++ 7 files changed, 308 insertions(+) create mode 100644 Documentation/devicetree/bindings/thermal/qcom-tsens.txt create mode 100644 drivers/thermal/qcom/Kconfig create mode 100644 drivers/thermal/qcom/Makefile create mode 100644 drivers/thermal/qcom/tsens.c create mode 100644 drivers/thermal/qcom/tsens.h
Documentation/devicetree/bindings/thermal/qcom-tsens.txt new file +33 -0
@@ -0,0 +1,33 @@ +* QCOM SoC Temperature Sensor (TSENS) + +Required properties: +- compatible : + - "qcom,msm8916-tsens" : For 8916 Family of SoCs + - "qcom,msm8974-tsens" : For 8974 Family of SoCs + +- reg: Address range of the thermal registers +- qcom,tsens-slopes : Must contain slope value for each of the sensors controlled + by this device +- #thermal-sensor-cells : Should be 1. See ./thermal.txt for a description. +- Refer to Documentation/devicetree/bindings/nvmem/nvmem.txt to know how to specify +nvmem cells + +Optional properties: +- qcom,sensor-id: List of sensor instances used in a given SoC. A TSENS IP can + have a fixed number of sensors (like 11) but a given SoC can + use only 5 of these and they might not always the first 5. They + could be sensors 0, 1, 4, 8 and 9. This property is used to + describe the subset of the sensors used. If this property is + missing they are assumed to be the first 'n' sensors numbered + sequentially in which case the number of sensors defaults to + the number of slope values. + +Example: +tsens: thermal-sensor at 900000 { + compatible = "qcom,msm8916-tsens"; + nvmem-cells = <&tsens_caldata>, <&tsens_calsel>; + nvmem-cell-names = "caldata", "calsel"; + qcom,tsens-slopes = <3200 3200 3200 3200 3200>; + qcom,sensor-id = <0 1 2 4 5>; + #thermal-sensor-cells = <1>; + };
drivers/thermal/Kconfig +5 -0
@@ -374,4 +374,9 @@ config QCOM_SPMI_TEMP_ALARM real time die temperature if an ADC is present or an estimate of the temperature based upon the over temperature stage value. +menu "Qualcomm thermal drivers" +depends on ARCH_QCOM && OF +source "drivers/thermal/qcom/Kconfig" +endmenu + endif
drivers/thermal/Makefile +1 -0
@@ -43,5 +43,6 @@ obj-$(CONFIG_TI_SOC_THERMAL) += ti-soc-thermal/ obj-$(CONFIG_INT340X_THERMAL) += int340x_thermal/ obj-$(CONFIG_INTEL_PCH_THERMAL) += intel_pch_thermal.o obj-$(CONFIG_ST_THERMAL) += st/ +obj-$(CONFIG_QCOM_TSENS) += qcom/ obj-$(CONFIG_TEGRA_SOCTHERM) += tegra_soctherm.o obj-$(CONFIG_HISI_THERMAL) += hisi_thermal.o
drivers/thermal/qcom/Kconfig new file +10 -0
@@ -0,0 +1,10 @@ +config QCOM_TSENS + tristate "Qualcomm TSENS Temperature Alarm" + depends on THERMAL + depends on QCOM_QFPROM + help + This enables the thermal sysfs driver for the TSENS device. It shows + up in Sysfs as a thermal zone with multiple trip points. Disabling the + thermal zone device via the mode file results in disabling the sensor. + Also able to set threshold temperature for both hot and cold and update + when a threshold is reached.
drivers/thermal/qcom/Makefile new file +2 -0
@@ -0,0 +1,2 @@ +obj-$(CONFIG_QCOM_TSENS) += qcom_tsens.o +qcom_tsens-y += tsens.o
drivers/thermal/qcom/tsens.c new file +199 -0
199 lines not on this page · raw message
drivers/thermal/qcom/tsens.h new file +58 -0
58 lines not on this page · raw message
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 1/8 thermal: qcom: tsens: Add a skeletal TSENS drivers
Hello Rajendra,
On Fri, Oct 09, 2015 at 03:11:03PM +0530, Rajendra Nayak wrote:
<cut>
Documentation/devicetree/bindings/thermal/qcom-tsens.txt line 23
Quoted 13 lines
+- #thermal-sensor-cells : Should be 1. See ./thermal.txt for a description. +- Refer to Documentation/devicetree/bindings/nvmem/nvmem.txt to know how to specifyDocumentation/devicetree/bindings/thermal/qcom-tsens.txt new file +11
-0+nvmem cells + +Optional properties: +- qcom,sensor-id: List of sensor instances used in a given SoC. A TSENS IP can + have a fixed number of sensors (like 11) but a given SoC can + use only 5 of these and they might not always the first 5. They + could be sensors 0, 1, 4, 8 and 9. This property is used to + describe the subset of the sensors used. If this property is + missing they are assumed to be the first 'n' sensors numbered + sequentially in which case the number of sensors defaults to + the number of slope values.
Can you please elaborate a bit more on why you could not solve this using the thermal sensor descriptor id?
Documentation/devicetree/bindings/thermal/qcom-tsens.txt line 30
Quoted 7 lines
Documentation/devicetree/bindings/thermal/qcom-tsens.txt new file +7
-0+ +Example: +tsens: thermal-sensor at 900000 { + compatible = "qcom,msm8916-tsens"; + nvmem-cells = <&tsens_caldata>, <&tsens_calsel>; + nvmem-cell-names = "caldata", "calsel"; + qcom,tsens-slopes = <3200 3200 3200 3200 3200>;
This property is not documented. Please, also consider my comment on Narendran's work: use the already existing thermal zone properties.
Have a look on the binding documentation:Documentation/devicetree/bindings/thermal/thermal.txt
<quote>
Optional property:
- coefficients: An array of integers (one signed cell) containing Type: array coefficients to compose a linear relation between Elem size: one cell the sensors listed in the thermal-sensors property. Elem type: signed Coefficients defaults to 1, in case this property
is not specified. A simple linear polynomial is used:
Z = c0 * x0 + c1 + x1 + ... + c(n-1) * x(n-1) + cn.
The coefficients are ordered and they match with sensors by means of sensor ID. Additional coefficients are interpreted as constant offset.
</quote>
Today the code supports only slope + offset linear coefficients. Which I am assuming you could reuse in your case.
Documentation/devicetree/bindings/thermal/qcom-tsens.txt line 32
Quoted 2 lines
Documentation/devicetree/bindings/thermal/qcom-tsens.txt new file +2
-0+ qcom,sensor-id = <0 1 2 4 5>; + #thermal-sensor-cells = <1>;
How about if you simply make the sensor driver expose all sensors, then in the thermal zone descriptor, you pick which sensor to use using the thermal sensor descriptor (quoting the binding again):
ocp {
...
/*
* A simple IC with several bandgap temperature sensors.
*/
bandgap0: bandgap at 0x0000ED00 {
...
#thermal-sensor-cells = <1>;
};
};thermal-zones {
cpu_thermal: cpu-thermal {
polling-delay-passive = <250>; /* milliseconds */
polling-delay = <1000>; /* milliseconds */
/* sensor ID */
thermal-sensors = <&bandgap0 0>;
};
gpu_thermal: gpu-thermal {
polling-delay-passive = <120>; /* milliseconds */
polling-delay = <1000>; /* milliseconds */
/* sensor ID */
thermal-sensors = <&bandgap0 1>;
};};
Would that simplify ?
BR,
Eduardo Valentin
drivers/thermal/Kconfig config QCOM_SPMI_TEMP_ALARM · line 378
Quoted 11 lines
(quoted diff) +1
-0+ };drivers/thermal/Kconfig +2
-0@@ -374,4 +374,9 @@ config QCOM_SPMI_TEMP_ALARM real time die temperature if an ADC is present or an estimate of the temperature based upon the over temperature stage value. +menu "Qualcomm thermal drivers" +depends on ARCH_QCOM && OF
Please add compile test too.
Quoted 21 lines
drivers/thermal/Kconfig +3
-0+source "drivers/thermal/qcom/Kconfig" +endmenu + endifdrivers/thermal/Makefile +1
-0@@ -43,5 +43,6 @@ obj-$(CONFIG_TI_SOC_THERMAL) += ti-soc-thermal/ obj-$(CONFIG_INT340X_THERMAL) += int340x_thermal/ obj-$(CONFIG_INTEL_PCH_THERMAL) += intel_pch_thermal.o obj-$(CONFIG_ST_THERMAL) += st/ +obj-$(CONFIG_QCOM_TSENS) += qcom/ obj-$(CONFIG_TEGRA_SOCTHERM) += tegra_soctherm.o obj-$(CONFIG_HISI_THERMAL) += hisi_thermal.odrivers/thermal/qcom/Kconfig new file +0
-0
drivers/thermal/qcom/Kconfig line 4
Quoted 4 lines
drivers/thermal/qcom/Kconfig new file +4
-0@@ -0,0 +1,10 @@ +config QCOM_TSENS + tristate "Qualcomm TSENS Temperature Alarm" + depends on THERMAL + depends on QCOM_QFPROM
Compile test..
Quoted 256 lines
drivers/thermal/qcom/Kconfig new file +6
-0+ help + This enables the thermal sysfs driver for the TSENS device. It shows + up in Sysfs as a thermal zone with multiple trip points. Disabling the + thermal zone device via the mode file results in disabling the sensor. + Also able to set threshold temperature for both hot and cold and update + when a threshold is reached.drivers/thermal/qcom/Makefile new file +2
-0@@ -0,0 +1,2 @@ +obj-$(CONFIG_QCOM_TSENS) += qcom_tsens.o +qcom_tsens-y += tsens.odrivers/thermal/qcom/tsens.c new file +199
-0@@ -0,0 +1,199 @@ +/* +* Copyright (c) 2015, The Linux Foundation. All rights reserved. +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License version 2 and +* only version 2 as published by the Free Software Foundation. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +*/ + +#include <linux/err.h> +#include <linux/module.h> +#include <linux/of.h> +#include <linux/platform_device.h> +#include <linux/pm.h> +#include <linux/slab.h> +#include <linux/thermal.h> +#include "tsens.h" + +static int tsens_get_temp (void *data,int *temp) +{ +const struct tsens_sensor *s = data; +struct tsens_device *tmdev = s->tmdev; + +return tmdev->ops->get_temp (tmdev, s->id, temp); +} + +static int tsens_get_trend (void *data,long *temp) +{ +const struct tsens_sensor *s = data; +struct tsens_device *tmdev = s->tmdev; + +if (tmdev->ops->get_trend) +return tmdev->ops->get_trend (tmdev, s->id, temp); + +return -ENOSYS ; +} + +static int tsens_suspend (struct device *dev) +{ +struct tsens_device *tmdev =dev_get_drvdata (dev); + +if (tmdev->ops && tmdev->ops->suspend) +return tmdev->ops->suspend (tmdev); + +return 0 ; +} + +static int tsens_resume (struct device *dev) +{ +struct tsens_device *tmdev =dev_get_drvdata (dev); + +if (tmdev->ops && tmdev->ops->resume) +return tmdev->ops->resume (tmdev); + +return 0 ; +} + +static SIMPLE_DEV_PM_OPS(tsens_pm_ops, tsens_suspend, tsens_resume); + +static const struct of_device_id tsens_table[] = { + { + .compatible ="qcom,msm8916-tsens" , + }, { + .compatible ="qcom,msm8974-tsens" , + }, + {} +}; +MODULE_DEVICE_TABLE (of, tsens_table); + +static const struct thermal_zone_of_device_ops tsens_of_ops = { + .get_temp = tsens_get_temp, + .get_trend = tsens_get_trend, +}; + +static int tsens_register (struct tsens_device *tmdev) +{ +int i, ret; +struct thermal_zone_device *tzd; +u32 *hw_id, n = tmdev->num_sensors; +struct device_node *np = tmdev->dev->of_node; + + hw_id =devm_kcalloc (tmdev->dev, n,sizeof (u32),GFP_KERNEL ); +if (!hw_id) +return -ENOMEM ; + + ret =of_property_read_u32_array (np,"qcom,sensor-id" , hw_id, n); +for (i =0 ; i < tmdev->num_sensors; i++) { +if (ret) + tmdev->sensor[i].hw_id = i; +else + tmdev->sensor[i].hw_id = hw_id[i]; + tmdev->sensor[i].tmdev = tmdev; + tmdev->sensor[i].id = i; + tzd =thermal_zone_of_sensor_register (tmdev->dev, i, + &tmdev->sensor[i], + &tsens_of_ops); +if (IS_ERR (tzd)) +continue ; + tmdev->sensor[i].tzd = tzd; +if (tmdev->ops->enable) + tmdev->ops->enable (tmdev, i); + } +return 0 ; +} + +static int tsens_probe (struct platform_device *pdev) +{ +int ret, i, num; +struct device *dev; +struct device_node *np; +struct tsens_sensor *s; +struct tsens_device *tmdev; +const struct of_device_id *id; + + dev = &pdev->dev; + np = dev->of_node; + + num =of_property_count_u32_elems (np,"qcom,tsens-slopes" ); +if (num <=0 ) { +dev_err (dev,"invalid tsens slopes\n" ); +return -EINVAL ; + } + + tmdev =devm_kzalloc (dev,sizeof (*tmdev) + + num *sizeof (*s),GFP_KERNEL ); +if (!tmdev) +return -ENOMEM ; + + tmdev->dev = dev; + tmdev->num_sensors = num; + +for (i =0 , s = tmdev->sensor; i < tmdev->num_sensors; i++, s++) +of_property_read_u32_index (np,"qcom,tsens-slopes" , i, + &s->slope); + + id =of_match_node (tsens_table, np); +if (!id) +return -ENODEV ; + + tmdev->ops = id->data; +if (!tmdev->ops || !tmdev->ops->init || !tmdev->ops->calibrate || + !tmdev->ops->get_temp) +return -EINVAL ; + + ret = tmdev->ops->init (tmdev); +if (ret <0 ) { +dev_err (dev,"tsens init failed\n" ); +return ret; + } + + ret = tmdev->ops->calibrate (tmdev); +if (ret <0 ) { +dev_err (dev,"tsens calibration failed\n" ); +return ret; + } + + ret =tsens_register (tmdev); + +platform_set_drvdata (pdev, tmdev); + +return ret; +} + +static int tsens_remove (struct platform_device *pdev) +{ +int i; +struct tsens_device *tmdev =platform_get_drvdata (pdev); +struct thermal_zone_device *tzd; + +if (tmdev->ops->disable) + tmdev->ops->disable (tmdev); + +for (i =0 ; i < tmdev->num_sensors; i++) { + tzd = tmdev->sensor[i].tzd; +thermal_zone_of_sensor_unregister (&pdev->dev, tzd); + } + +return 0 ; +} + +static struct platform_driver tsens_driver = { + .probe = tsens_probe, + .remove = tsens_remove, + .driver = { + .name ="qcom-tsens" , + .pm = &tsens_pm_ops, + .of_match_table = tsens_table, + }, +}; +module_platform_driver (tsens_driver); + +MODULE_LICENSE ("GPL v2" ); +MODULE_DESCRIPTION ("QCOM Temperature Sensor driver" ); +MODULE_ALIAS ("platform:qcom-tsens" );drivers/thermal/qcom/tsens.h new file +29
-0@@ -0,0 +1,58 @@ +/* +* Copyright (c) 2015, The Linux Foundation. All rights reserved. +* +* This software is licensed under the terms of the GNU General Public +* License version 2, as published by the Free Software Foundation, and +* may be copied, distributed, and modified under those terms. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +*/ +#ifndef __QCOM_TSENS_H__ +#define __QCOM_TSENS_H__ + +struct tsens_device ; + +struct tsens_sensor { +struct tsens_device *tmdev; +struct thermal_zone_device *tzd; +int offset; +int id; +int hw_id; +u32 slope; +u32 status; +}; + +struct tsens_ops { +/* mandatory callbacks */
drivers/thermal/qcom/tsens.h line 39
Quoted 10 lines
drivers/thermal/qcom/tsens.h new file +10
-0+int (*init)(struct tsens_device *); +int (*calibrate)(struct tsens_device *); +int (*get_temp)(struct tsens_device *,int ,int *); +/* optional callbacks */ +int (*enable)(struct tsens_device *,int ); +void (*disable)(struct tsens_device *); +int (*suspend)(struct tsens_device *); +int (*resume)(struct tsens_device *); +int (*get_trend)(struct tsens_device *,int ,long *); +};
I know this is a set of internal data structures. But, given that you are creating a driver that supports a family of chips, and that I assume will be having additions on it in the future, it would be nice if you add kernel doc entries on these, so people know what to expect from them.
Quoted 23 lines
drivers/thermal/qcom/tsens.h new file +19
-0+ +/* Registers to be saved/restored across a context loss */ +struct tsens_context { +int threshold; +int control; +}; + +struct tsens_device { +struct device *dev; +u32 num_sensors; +struct regmap *map; +struct regmap_field *status_field; +struct tsens_context ctx; +bool trdy; +const struct tsens_ops *ops; +struct tsens_sensor sensor[0 ]; +}; + +#endif /* __QCOM_TSENS_H__ */ Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 1/8 thermal: qcom: tsens: Add a skeletal TSENS drivers
Quoted 46 lines · Eduardo Valentin
Hello Rajendra,
On Fri, Oct 09, 2015 at 03:11:03PM +0530, Rajendra Nayak wrote:
<cut>
Documentation/devicetree/bindings/thermal/qcom-tsens.txt line 23
Quoted 13 lines
+- #thermal-sensor-cells : Should be 1. See ./thermal.txt for a description. +- Refer to Documentation/devicetree/bindings/nvmem/nvmem.txt to know how to specifyDocumentation/devicetree/bindings/thermal/qcom-tsens.txt new file +11
-0+nvmem cells + +Optional properties: +- qcom,sensor-id: List of sensor instances used in a given SoC. A TSENS IP can + have a fixed number of sensors (like 11) but a given SoC can + use only 5 of these and they might not always the first 5. They + could be sensors 0, 1, 4, 8 and 9. This property is used to + describe the subset of the sensors used. If this property is + missing they are assumed to be the first 'n' sensors numbered + sequentially in which case the number of sensors defaults to + the number of slope values.Can you please elaborate a bit more on why you could not solve this using the thermal sensor descriptor id?
Documentation/devicetree/bindings/thermal/qcom-tsens.txt line 30
Quoted 7 lines
Documentation/devicetree/bindings/thermal/qcom-tsens.txt new file +7
-0+ +Example: +tsens: thermal-sensor at 900000 { + compatible = "qcom,msm8916-tsens"; + nvmem-cells = <&tsens_caldata>, <&tsens_calsel>; + nvmem-cell-names = "caldata", "calsel"; + qcom,tsens-slopes = <3200 3200 3200 3200 3200>;This property is not documented. Please, also consider my comment on Narendran's work: use the already existing thermal zone properties.
Have a look on the binding documentation:
Documentation/devicetree/bindings/thermal/thermal.txt<quote>
Optional property:- coefficients: An array of integers (one signed cell) containing Type: array coefficients to compose a linear relation between Elem size: one cell the sensors listed in the thermal-sensors property. Elem type: signed Coefficients defaults to 1, in case this propertyis not specified. A simple linear polynomial is used:
Z = c0 * x0 + c1 + x1 + ... + c(n-1) * x(n-1) + cn.
Quoted 7 lines
The coefficients are ordered and they match with sensors by means of sensor ID. Additional coefficients are interpreted as constant offset.
</quote>Today the code supports only slope + offset linear coefficients. Which I am assuming you could reuse in your case.
Sure, I'll take a look at these and see if I can reuse these bindings instead of creating new ones.
regards,
Rajendra
Quoted 384 lines
Documentation/devicetree/bindings/thermal/qcom-tsens.txt line 32
Quoted 5 lines
Documentation/devicetree/bindings/thermal/qcom-tsens.txt new file +2
-0+ qcom,sensor-id = <0 1 2 4 5>; + #thermal-sensor-cells = <1>;How about if you simply make the sensor driver expose all sensors, then in the thermal zone descriptor, you pick which sensor to use using the thermal sensor descriptor (quoting the binding again):
ocp { ... /* * A simple IC with several bandgap temperature sensors. */ bandgap0: bandgap at 0x0000ED00 { ... #thermal-sensor-cells = <1>; }; };thermal-zones { cpu_thermal: cpu-thermal { polling-delay-passive = <250>; /* milliseconds */ polling-delay = <1000>; /* milliseconds */ /* sensor ID */ thermal-sensors = <&bandgap0 0>; }; gpu_thermal: gpu-thermal { polling-delay-passive = <120>; /* milliseconds */ polling-delay = <1000>; /* milliseconds */ /* sensor ID */ thermal-sensors = <&bandgap0 1>; };};
Would that simplify ?
BR,
Eduardo Valentin
drivers/thermal/Kconfig config QCOM_SPMI_TEMP_ALARM · line 378
Quoted 11 lines
(quoted diff) +1
-0+ };drivers/thermal/Kconfig +2
-0@@ -374,4 +374,9 @@ config QCOM_SPMI_TEMP_ALARM real time die temperature if an ADC is present or an estimate of the temperature based upon the over temperature stage value. +menu "Qualcomm thermal drivers" +depends on ARCH_QCOM && OFPlease add compile test too.
Quoted 21 lines
drivers/thermal/Kconfig +3
-0+source "drivers/thermal/qcom/Kconfig" +endmenu + endifdrivers/thermal/Makefile +1
-0@@ -43,5 +43,6 @@ obj-$(CONFIG_TI_SOC_THERMAL) += ti-soc-thermal/ obj-$(CONFIG_INT340X_THERMAL) += int340x_thermal/ obj-$(CONFIG_INTEL_PCH_THERMAL) += intel_pch_thermal.o obj-$(CONFIG_ST_THERMAL) += st/ +obj-$(CONFIG_QCOM_TSENS) += qcom/ obj-$(CONFIG_TEGRA_SOCTHERM) += tegra_soctherm.o obj-$(CONFIG_HISI_THERMAL) += hisi_thermal.odrivers/thermal/qcom/Kconfig new file +0
-0drivers/thermal/qcom/Kconfig line 4
Quoted 4 lines
drivers/thermal/qcom/Kconfig new file +4
-0@@ -0,0 +1,10 @@ +config QCOM_TSENS + tristate "Qualcomm TSENS Temperature Alarm" + depends on THERMAL + depends on QCOM_QFPROMCompile test..
Quoted 256 lines
drivers/thermal/qcom/Kconfig new file +6
-0+ help + This enables the thermal sysfs driver for the TSENS device. It shows + up in Sysfs as a thermal zone with multiple trip points. Disabling the + thermal zone device via the mode file results in disabling the sensor. + Also able to set threshold temperature for both hot and cold and update + when a threshold is reached.drivers/thermal/qcom/Makefile new file +2
-0@@ -0,0 +1,2 @@ +obj-$(CONFIG_QCOM_TSENS) += qcom_tsens.o +qcom_tsens-y += tsens.odrivers/thermal/qcom/tsens.c new file +199
-0@@ -0,0 +1,199 @@ +/* +* Copyright (c) 2015, The Linux Foundation. All rights reserved. +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License version 2 and +* only version 2 as published by the Free Software Foundation. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +*/ + +#include <linux/err.h> +#include <linux/module.h> +#include <linux/of.h> +#include <linux/platform_device.h> +#include <linux/pm.h> +#include <linux/slab.h> +#include <linux/thermal.h> +#include "tsens.h" + +static int tsens_get_temp (void *data,int *temp) +{ +const struct tsens_sensor *s = data; +struct tsens_device *tmdev = s->tmdev; + +return tmdev->ops->get_temp (tmdev, s->id, temp); +} + +static int tsens_get_trend (void *data,long *temp) +{ +const struct tsens_sensor *s = data; +struct tsens_device *tmdev = s->tmdev; + +if (tmdev->ops->get_trend) +return tmdev->ops->get_trend (tmdev, s->id, temp); + +return -ENOSYS ; +} + +static int tsens_suspend (struct device *dev) +{ +struct tsens_device *tmdev =dev_get_drvdata (dev); + +if (tmdev->ops && tmdev->ops->suspend) +return tmdev->ops->suspend (tmdev); + +return 0 ; +} + +static int tsens_resume (struct device *dev) +{ +struct tsens_device *tmdev =dev_get_drvdata (dev); + +if (tmdev->ops && tmdev->ops->resume) +return tmdev->ops->resume (tmdev); + +return 0 ; +} + +static SIMPLE_DEV_PM_OPS(tsens_pm_ops, tsens_suspend, tsens_resume); + +static const struct of_device_id tsens_table[] = { + { + .compatible ="qcom,msm8916-tsens" , + }, { + .compatible ="qcom,msm8974-tsens" , + }, + {} +}; +MODULE_DEVICE_TABLE (of, tsens_table); + +static const struct thermal_zone_of_device_ops tsens_of_ops = { + .get_temp = tsens_get_temp, + .get_trend = tsens_get_trend, +}; + +static int tsens_register (struct tsens_device *tmdev) +{ +int i, ret; +struct thermal_zone_device *tzd; +u32 *hw_id, n = tmdev->num_sensors; +struct device_node *np = tmdev->dev->of_node; + + hw_id =devm_kcalloc (tmdev->dev, n,sizeof (u32),GFP_KERNEL ); +if (!hw_id) +return -ENOMEM ; + + ret =of_property_read_u32_array (np,"qcom,sensor-id" , hw_id, n); +for (i =0 ; i < tmdev->num_sensors; i++) { +if (ret) + tmdev->sensor[i].hw_id = i; +else + tmdev->sensor[i].hw_id = hw_id[i]; + tmdev->sensor[i].tmdev = tmdev; + tmdev->sensor[i].id = i; + tzd =thermal_zone_of_sensor_register (tmdev->dev, i, + &tmdev->sensor[i], + &tsens_of_ops); +if (IS_ERR (tzd)) +continue ; + tmdev->sensor[i].tzd = tzd; +if (tmdev->ops->enable) + tmdev->ops->enable (tmdev, i); + } +return 0 ; +} + +static int tsens_probe (struct platform_device *pdev) +{ +int ret, i, num; +struct device *dev; +struct device_node *np; +struct tsens_sensor *s; +struct tsens_device *tmdev; +const struct of_device_id *id; + + dev = &pdev->dev; + np = dev->of_node; + + num =of_property_count_u32_elems (np,"qcom,tsens-slopes" ); +if (num <=0 ) { +dev_err (dev,"invalid tsens slopes\n" ); +return -EINVAL ; + } + + tmdev =devm_kzalloc (dev,sizeof (*tmdev) + + num *sizeof (*s),GFP_KERNEL ); +if (!tmdev) +return -ENOMEM ; + + tmdev->dev = dev; + tmdev->num_sensors = num; + +for (i =0 , s = tmdev->sensor; i < tmdev->num_sensors; i++, s++) +of_property_read_u32_index (np,"qcom,tsens-slopes" , i, + &s->slope); + + id =of_match_node (tsens_table, np); +if (!id) +return -ENODEV ; + + tmdev->ops = id->data; +if (!tmdev->ops || !tmdev->ops->init || !tmdev->ops->calibrate || + !tmdev->ops->get_temp) +return -EINVAL ; + + ret = tmdev->ops->init (tmdev); +if (ret <0 ) { +dev_err (dev,"tsens init failed\n" ); +return ret; + } + + ret = tmdev->ops->calibrate (tmdev); +if (ret <0 ) { +dev_err (dev,"tsens calibration failed\n" ); +return ret; + } + + ret =tsens_register (tmdev); + +platform_set_drvdata (pdev, tmdev); + +return ret; +} + +static int tsens_remove (struct platform_device *pdev) +{ +int i; +struct tsens_device *tmdev =platform_get_drvdata (pdev); +struct thermal_zone_device *tzd; + +if (tmdev->ops->disable) + tmdev->ops->disable (tmdev); + +for (i =0 ; i < tmdev->num_sensors; i++) { + tzd = tmdev->sensor[i].tzd; +thermal_zone_of_sensor_unregister (&pdev->dev, tzd); + } + +return 0 ; +} + +static struct platform_driver tsens_driver = { + .probe = tsens_probe, + .remove = tsens_remove, + .driver = { + .name ="qcom-tsens" , + .pm = &tsens_pm_ops, + .of_match_table = tsens_table, + }, +}; +module_platform_driver (tsens_driver); + +MODULE_LICENSE ("GPL v2" ); +MODULE_DESCRIPTION ("QCOM Temperature Sensor driver" ); +MODULE_ALIAS ("platform:qcom-tsens" );drivers/thermal/qcom/tsens.h new file +29
-0@@ -0,0 +1,58 @@ +/* +* Copyright (c) 2015, The Linux Foundation. All rights reserved. +* +* This software is licensed under the terms of the GNU General Public +* License version 2, as published by the Free Software Foundation, and +* may be copied, distributed, and modified under those terms. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +*/ +#ifndef __QCOM_TSENS_H__ +#define __QCOM_TSENS_H__ + +struct tsens_device ; + +struct tsens_sensor { +struct tsens_device *tmdev; +struct thermal_zone_device *tzd; +int offset; +int id; +int hw_id; +u32 slope; +u32 status; +}; + +struct tsens_ops { +/* mandatory callbacks */ drivers/thermal/qcom/tsens.h line 39
Quoted 10 lines
drivers/thermal/qcom/tsens.h new file +10
-0+int (*init)(struct tsens_device *); +int (*calibrate)(struct tsens_device *); +int (*get_temp)(struct tsens_device *,int ,int *); +/* optional callbacks */ +int (*enable)(struct tsens_device *,int ); +void (*disable)(struct tsens_device *); +int (*suspend)(struct tsens_device *); +int (*resume)(struct tsens_device *); +int (*get_trend)(struct tsens_device *,int ,long *); +};I know this is a set of internal data structures. But, given that you are creating a driver that supports a family of chips, and that I assume will be having additions on it in the future, it would be nice if you add kernel doc entries on these, so people know what to expect from them.
Quoted 23 lines
drivers/thermal/qcom/tsens.h new file +19
-0+ +/* Registers to be saved/restored across a context loss */ +struct tsens_context { +int threshold; +int control; +}; + +struct tsens_device { +struct device *dev; +u32 num_sensors; +struct regmap *map; +struct regmap_field *status_field; +struct tsens_context ctx; +bool trdy; +const struct tsens_ops *ops; +struct tsens_sensor sensor[0 ]; +}; + +#endif /* __QCOM_TSENS_H__ */ Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
Signature · 2 lines
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 1/8 thermal: qcom: tsens: Add a skeletal TSENS drivers
[]..
Quoted 23 lines
Quoted 21 lines
Documentation/devicetree/bindings/thermal/qcom-tsens.txt line 23
Quoted 9 lines
Documentation/devicetree/bindings/thermal/qcom-tsens.txt new file +9
-0+Optional properties: +- qcom,sensor-id: List of sensor instances used in a given SoC. A TSENS IP can + have a fixed number of sensors (like 11) but a given SoC can + use only 5 of these and they might not always the first 5. They + could be sensors 0, 1, 4, 8 and 9. This property is used to + describe the subset of the sensors used. If this property is + missing they are assumed to be the first 'n' sensors numbered + sequentially in which case the number of sensors defaults to + the number of slope values.Can you please elaborate a bit more on why you could not solve this using the thermal sensor descriptor id?
Quoted 7 lines
Documentation/devicetree/bindings/thermal/qcom-tsens.txt new file +7
-0+ +Example: +tsens: thermal-sensor at 900000 { + compatible = "qcom,msm8916-tsens"; + nvmem-cells = <&tsens_caldata>, <&tsens_calsel>; + nvmem-cell-names = "caldata", "calsel"; + qcom,tsens-slopes = <3200 3200 3200 3200 3200>;
Quoted 6 lines
Quoted 6 lines
Documentation/devicetree/bindings/thermal/qcom-tsens.txt line 32
Quoted 2 lines
Documentation/devicetree/bindings/thermal/qcom-tsens.txt new file +2
-0+ qcom,sensor-id = <0 1 2 4 5>; + #thermal-sensor-cells = <1>;How about if you simply make the sensor driver expose all sensors, then in the thermal zone descriptor, you pick which sensor to use using the thermal sensor descriptor (quoting the binding again):
Hi Eduardo,
What you suggested would work, except for that the calibration data in eeprom would be available for only the _subset_ of sensors on the SoC. So the driver in some way would need to know which exact sensors the eeprom data corresponds to.
If this does not seem like something which needs to be described in DT, I can have the data embedded into the driver so it gets picked based on the right compatibles.
regards,
Rajendra
Quoted 36 lines
Quoted 36 lines
ocp { ... /* * A simple IC with several bandgap temperature sensors. */ bandgap0: bandgap at 0x0000ED00 { ... #thermal-sensor-cells = <1>; }; };thermal-zones { cpu_thermal: cpu-thermal { polling-delay-passive = <250>; /* milliseconds */ polling-delay = <1000>; /* milliseconds */ /* sensor ID */ thermal-sensors = <&bandgap0 0>; }; gpu_thermal: gpu-thermal { polling-delay-passive = <120>; /* milliseconds */ polling-delay = <1000>; /* milliseconds */ /* sensor ID */ thermal-sensors = <&bandgap0 1>; };};
Would that simplify ?
BR,
Eduardo Valentin
Signature · 2 lines
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 1/8 thermal: qcom: tsens: Add a skeletal TSENS drivers
Quoted 44 lines
[]..
Quoted 24 lines
Quoted 22 lines
Documentation/devicetree/bindings/thermal/qcom-tsens.txt line 23
Quoted 10 lines
+Optional properties:
+- qcom,sensor-id: List of sensor instances used in a given SoC. A TSENS IP canDocumentation/devicetree/bindings/thermal/qcom-tsens.txt new file +7
-0+ have a fixed number of sensors (like 11) but a given SoC can + use only 5 of these and they might not always the first 5. They + could be sensors 0, 1, 4, 8 and 9. This property is used to + describe the subset of the sensors used. If this property is + missing they are assumed to be the first 'n' sensors numbered + sequentially in which case the number of sensors defaults to + the number of slope values.Can you please elaborate a bit more on why you could not solve this using the thermal sensor descriptor id?
Quoted 7 lines
Documentation/devicetree/bindings/thermal/qcom-tsens.txt new file +7
-0+ +Example: +tsens: thermal-sensor at 900000 { + compatible = "qcom,msm8916-tsens"; + nvmem-cells = <&tsens_caldata>, <&tsens_calsel>; + nvmem-cell-names = "caldata", "calsel"; + qcom,tsens-slopes = <3200 3200 3200 3200 3200>;Quoted 8 lines
Quoted 8 lines
Documentation/devicetree/bindings/thermal/qcom-tsens.txt line 32
Quoted 2 lines
Documentation/devicetree/bindings/thermal/qcom-tsens.txt new file +2
-0+ qcom,sensor-id = <0 1 2 4 5>; + #thermal-sensor-cells = <1>;How about if you simply make the sensor driver expose all sensors, then in the
thermal zone descriptor, you pick which sensor to use using the thermal sensor
descriptor (quoting the binding again):Hi Eduardo,
What you suggested would work, except for that the calibration data in eeprom would
be available for only the _subset_ of sensors on the SoC. So the driver in some way would
need to know which exact sensors the eeprom data corresponds to.
Quoted 4 lines
If this does not seem like something which needs to be described in DT, I can have the
data embedded into the driver so it gets picked based on the right compatibles.
Hey Eduardo, any thoughts on this?
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 1/8 thermal: qcom: tsens: Add a skeletal TSENS drivers
In reply to Rajendra NayakQuoted 154 lines · Rajendra Nayak
TSENS is Qualcomms' thermal temperature sensor device. It supports reading temperatures from multiple thermal sensors present on various QCOM SoCs.
Calibration data is generally read from a non-volatile memory (eeprom) device.Add a skeleton driver with all the necessary abstractions so a variety of qcom device families which support TSENS can add driver extensions.
Also add the required device tree bindings which can be used to describe the TSENS device in DT.
Signed-off-by Rajendra Nayak <[email protected]>Reviewed-by Lina Iyer <[email protected]>--- .../devicetree/bindings/thermal/qcom-tsens.txt | 33 ++++ drivers/thermal/Kconfig | 5 + drivers/thermal/Makefile | 1 + drivers/thermal/qcom/Kconfig | 10 ++ drivers/thermal/qcom/Makefile | 2 + drivers/thermal/qcom/tsens.c | 199 +++++++++++++++++++++ drivers/thermal/qcom/tsens.h | 58 ++++++ 7 files changed, 308 insertions(+) create mode 100644 Documentation/devicetree/bindings/thermal/qcom-tsens.txt create mode 100644 drivers/thermal/qcom/Kconfig create mode 100644 drivers/thermal/qcom/Makefile create mode 100644 drivers/thermal/qcom/tsens.c create mode 100644 drivers/thermal/qcom/tsens.hDocumentation/devicetree/bindings/thermal/qcom-tsens.txt new file +33
-0@@ -0,0 +1,33 @@ +* QCOM SoC Temperature Sensor (TSENS) + +Required properties: +- compatible : + - "qcom,msm8916-tsens" : For 8916 Family of SoCs + - "qcom,msm8974-tsens" : For 8974 Family of SoCs + +- reg: Address range of the thermal registers +- qcom,tsens-slopes : Must contain slope value for each of the sensors controlled + by this device +- #thermal-sensor-cells : Should be 1. See ./thermal.txt for a description. +- Refer to Documentation/devicetree/bindings/nvmem/nvmem.txt to know how to specify +nvmem cells + +Optional properties: +- qcom,sensor-id: List of sensor instances used in a given SoC. A TSENS IP can + have a fixed number of sensors (like 11) but a given SoC can + use only 5 of these and they might not always the first 5. They + could be sensors 0, 1, 4, 8 and 9. This property is used to + describe the subset of the sensors used. If this property is + missing they are assumed to be the first 'n' sensors numbered + sequentially in which case the number of sensors defaults to + the number of slope values. + +Example: +tsens: thermal-sensor at 900000 { + compatible = "qcom,msm8916-tsens"; + nvmem-cells = <&tsens_caldata>, <&tsens_calsel>; + nvmem-cell-names = "caldata", "calsel"; + qcom,tsens-slopes = <3200 3200 3200 3200 3200>; + qcom,sensor-id = <0 1 2 4 5>; + #thermal-sensor-cells = <1>; + };drivers/thermal/Kconfig +5
-0@@ -374,4 +374,9 @@ config QCOM_SPMI_TEMP_ALARM real time die temperature if an ADC is present or an estimate of the temperature based upon the over temperature stage value. +menu "Qualcomm thermal drivers" +depends on ARCH_QCOM && OF +source "drivers/thermal/qcom/Kconfig" +endmenu + endifdrivers/thermal/Makefile +1
-0@@ -43,5 +43,6 @@ obj-$(CONFIG_TI_SOC_THERMAL) += ti-soc-thermal/ obj-$(CONFIG_INT340X_THERMAL) += int340x_thermal/ obj-$(CONFIG_INTEL_PCH_THERMAL) += intel_pch_thermal.o obj-$(CONFIG_ST_THERMAL) += st/ +obj-$(CONFIG_QCOM_TSENS) += qcom/ obj-$(CONFIG_TEGRA_SOCTHERM) += tegra_soctherm.o obj-$(CONFIG_HISI_THERMAL) += hisi_thermal.odrivers/thermal/qcom/Kconfig new file +10
-0@@ -0,0 +1,10 @@ +config QCOM_TSENS + tristate "Qualcomm TSENS Temperature Alarm" + depends on THERMAL + depends on QCOM_QFPROM + help + This enables the thermal sysfs driver for the TSENS device. It shows + up in Sysfs as a thermal zone with multiple trip points. Disabling the + thermal zone device via the mode file results in disabling the sensor. + Also able to set threshold temperature for both hot and cold and update + when a threshold is reached.drivers/thermal/qcom/Makefile new file +2
-0@@ -0,0 +1,2 @@ +obj-$(CONFIG_QCOM_TSENS) += qcom_tsens.o +qcom_tsens-y += tsens.odrivers/thermal/qcom/tsens.c new file +30
-0@@ -0,0 +1,199 @@ +/* +* Copyright (c) 2015, The Linux Foundation. All rights reserved. +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License version 2 and +* only version 2 as published by the Free Software Foundation. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +*/ + +#include <linux/err.h> +#include <linux/module.h> +#include <linux/of.h> +#include <linux/platform_device.h> +#include <linux/pm.h> +#include <linux/slab.h> +#include <linux/thermal.h> +#include "tsens.h" + +static int tsens_get_temp (void *data,int *temp) +{ +const struct tsens_sensor *s = data; +struct tsens_device *tmdev = s->tmdev; + +return tmdev->ops->get_temp (tmdev, s->id, temp); +}
drivers/thermal/qcom/tsens.c line 40
Quoted 10 lines
drivers/thermal/qcom/tsens.c new file +10
-0+ +static int tsens_get_trend (void *data,long *temp) +{ +const struct tsens_sensor *s = data; +struct tsens_device *tmdev = s->tmdev; + +if (tmdev->ops->get_trend) +return tmdev->ops->get_trend (tmdev, s->id, temp); + +return -ENOSYS ;
Are you sure you meant to say "system call number not supported"?
Maybe ENOTSUPP? Even though it is defined for nfsv3, the error code is in use all over, and I believe suits better.
Quoted 227 lines
drivers/thermal/qcom/tsens.c new file +159
-0+} + +static int tsens_suspend (struct device *dev) +{ +struct tsens_device *tmdev =dev_get_drvdata (dev); + +if (tmdev->ops && tmdev->ops->suspend) +return tmdev->ops->suspend (tmdev); + +return 0 ; +} + +static int tsens_resume (struct device *dev) +{ +struct tsens_device *tmdev =dev_get_drvdata (dev); + +if (tmdev->ops && tmdev->ops->resume) +return tmdev->ops->resume (tmdev); + +return 0 ; +} + +static SIMPLE_DEV_PM_OPS(tsens_pm_ops, tsens_suspend, tsens_resume); + +static const struct of_device_id tsens_table[] = { + { + .compatible ="qcom,msm8916-tsens" , + }, { + .compatible ="qcom,msm8974-tsens" , + }, + {} +}; +MODULE_DEVICE_TABLE (of, tsens_table); + +static const struct thermal_zone_of_device_ops tsens_of_ops = { + .get_temp = tsens_get_temp, + .get_trend = tsens_get_trend, +}; + +static int tsens_register (struct tsens_device *tmdev) +{ +int i, ret; +struct thermal_zone_device *tzd; +u32 *hw_id, n = tmdev->num_sensors; +struct device_node *np = tmdev->dev->of_node; + + hw_id =devm_kcalloc (tmdev->dev, n,sizeof (u32),GFP_KERNEL ); +if (!hw_id) +return -ENOMEM ; + + ret =of_property_read_u32_array (np,"qcom,sensor-id" , hw_id, n); +for (i =0 ; i < tmdev->num_sensors; i++) { +if (ret) + tmdev->sensor[i].hw_id = i; +else + tmdev->sensor[i].hw_id = hw_id[i]; + tmdev->sensor[i].tmdev = tmdev; + tmdev->sensor[i].id = i; + tzd =thermal_zone_of_sensor_register (tmdev->dev, i, + &tmdev->sensor[i], + &tsens_of_ops); +if (IS_ERR (tzd)) +continue ; + tmdev->sensor[i].tzd = tzd; +if (tmdev->ops->enable) + tmdev->ops->enable (tmdev, i); + } +return 0 ; +} + +static int tsens_probe (struct platform_device *pdev) +{ +int ret, i, num; +struct device *dev; +struct device_node *np; +struct tsens_sensor *s; +struct tsens_device *tmdev; +const struct of_device_id *id; + + dev = &pdev->dev; + np = dev->of_node; + + num =of_property_count_u32_elems (np,"qcom,tsens-slopes" ); +if (num <=0 ) { +dev_err (dev,"invalid tsens slopes\n" ); +return -EINVAL ; + } + + tmdev =devm_kzalloc (dev,sizeof (*tmdev) + + num *sizeof (*s),GFP_KERNEL ); +if (!tmdev) +return -ENOMEM ; + + tmdev->dev = dev; + tmdev->num_sensors = num; + +for (i =0 , s = tmdev->sensor; i < tmdev->num_sensors; i++, s++) +of_property_read_u32_index (np,"qcom,tsens-slopes" , i, + &s->slope); + + id =of_match_node (tsens_table, np); +if (!id) +return -ENODEV ; + + tmdev->ops = id->data; +if (!tmdev->ops || !tmdev->ops->init || !tmdev->ops->calibrate || + !tmdev->ops->get_temp) +return -EINVAL ; + + ret = tmdev->ops->init (tmdev); +if (ret <0 ) { +dev_err (dev,"tsens init failed\n" ); +return ret; + } + + ret = tmdev->ops->calibrate (tmdev); +if (ret <0 ) { +dev_err (dev,"tsens calibration failed\n" ); +return ret; + } + + ret =tsens_register (tmdev); + +platform_set_drvdata (pdev, tmdev); + +return ret; +} + +static int tsens_remove (struct platform_device *pdev) +{ +int i; +struct tsens_device *tmdev =platform_get_drvdata (pdev); +struct thermal_zone_device *tzd; + +if (tmdev->ops->disable) + tmdev->ops->disable (tmdev); + +for (i =0 ; i < tmdev->num_sensors; i++) { + tzd = tmdev->sensor[i].tzd; +thermal_zone_of_sensor_unregister (&pdev->dev, tzd); + } + +return 0 ; +} + +static struct platform_driver tsens_driver = { + .probe = tsens_probe, + .remove = tsens_remove, + .driver = { + .name ="qcom-tsens" , + .pm = &tsens_pm_ops, + .of_match_table = tsens_table, + }, +}; +module_platform_driver (tsens_driver); + +MODULE_LICENSE ("GPL v2" ); +MODULE_DESCRIPTION ("QCOM Temperature Sensor driver" ); +MODULE_ALIAS ("platform:qcom-tsens" );drivers/thermal/qcom/tsens.h new file +58
-0@@ -0,0 +1,58 @@ +/* +* Copyright (c) 2015, The Linux Foundation. All rights reserved. +* +* This software is licensed under the terms of the GNU General Public +* License version 2, as published by the Free Software Foundation, and +* may be copied, distributed, and modified under those terms. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +*/ +#ifndef __QCOM_TSENS_H__ +#define __QCOM_TSENS_H__ + +struct tsens_device ; + +struct tsens_sensor { +struct tsens_device *tmdev; +struct thermal_zone_device *tzd; +int offset; +int id; +int hw_id; +u32 slope; +u32 status; +}; + +struct tsens_ops { +/* mandatory callbacks */ +int (*init)(struct tsens_device *); +int (*calibrate)(struct tsens_device *); +int (*get_temp)(struct tsens_device *,int ,int *); +/* optional callbacks */ +int (*enable)(struct tsens_device *,int ); +void (*disable)(struct tsens_device *); +int (*suspend)(struct tsens_device *); +int (*resume)(struct tsens_device *); +int (*get_trend)(struct tsens_device *,int ,long *); +}; + +/* Registers to be saved/restored across a context loss */ +struct tsens_context { +int threshold; +int control; +}; + +struct tsens_device { +struct device *dev; +u32 num_sensors; +struct regmap *map; +struct regmap_field *status_field; +struct tsens_context ctx; +bool trdy; +const struct tsens_ops *ops; +struct tsens_sensor sensor[0 ]; +}; + +#endif /* __QCOM_TSENS_H__ */ Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 2/8 thermal: qcom: tsens-8916: Add support for 8916 family of SoCs
In reply to Rajendra NayakAdd support to calibrate sensors on 8916 family and also add common functions to read temperature from sensors (This can be reused on other SoCs having similar TSENS device)
The calibration data is read from eeprom using the generic nvmem framework apis.
Based on the original code by Siddartha Mohanadoss and Stephen Boyd.
--- drivers/thermal/qcom/Makefile | 2 +- drivers/thermal/qcom/tsens-8916.c | 107 +++++++++++++++++++++++++++++ drivers/thermal/qcom/tsens-common.c | 130 ++++++++++++++++++++++++++++++++++++ drivers/thermal/qcom/tsens.c | 1 + drivers/thermal/qcom/tsens.h | 11 +++ 5 files changed, 250 insertions(+), 1 deletion(-) create mode 100644 drivers/thermal/qcom/tsens-8916.c create mode 100644 drivers/thermal/qcom/tsens-common.c
drivers/thermal/qcom/Makefile +1 -1
@@ -1,2 +1,2 @@ obj-$(CONFIG_QCOM_TSENS) += qcom_tsens.o -qcom_tsens-y += tsens.o +qcom_tsens-y += tsens.o tsens-common.o tsens-8916.o
drivers/thermal/qcom/tsens-8916.c new file +107 -0
107 lines not on this page · raw message
drivers/thermal/qcom/tsens-common.c new file +130 -0
130 lines not on this page · raw message
drivers/thermal/qcom/tsens.c +1 -0
@@ -65,6 +65,7 @@ static SIMPLE_DEV_PM_OPS(tsens_pm_ops, tsens_suspend, tsens_resume);static const struct of_device_id tsens_table[] = { { .compatible ="qcom,msm8916-tsens" , + .data = &ops_8916, }, { .compatible ="qcom,msm8974-tsens" , },
drivers/thermal/qcom/tsens.h +11 -0
@@ -13,6 +13,10 @@#ifndef __QCOM_TSENS_H__#define __QCOM_TSENS_H__ +#define ONE_PT_CALIB 0x1 +#define ONE_PT_CALIB2 0x2 +#define TWO_PT_CALIB 0x3 +struct tsens_device ; struct tsens_sensor {
@@ -55,4 +59,11 @@ struct tsens_device { struct tsens_sensor sensor[0]; }; +char *qfprom_read (struct device *,const char *); +void compute_intercept_slope (struct tsens_device *,u32 *,u32 *,u32 ); +int init_common (struct tsens_device *); +int get_temp_common (struct tsens_device *,int ,int *); + +extern const struct tsens_ops ops_8916; +#endif /* __QCOM_TSENS_H__ */
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 2/8 thermal: qcom: tsens-8916: Add support for 8916 family of SoCs
Quoted 6 lines · Rajendra Nayak
Add support to calibrate sensors on 8916 family and also add common functions to read temperature from sensors (This can be reused on other SoCs having similar TSENS device)
The calibration data is read from eeprom using the generic nvmem framework apis.
Quoted 7 lines
Based on the original code by Siddartha Mohanadoss and Stephen Boyd.
Signed-off-by Rajendra Nayak <[email protected]>--- drivers/thermal/qcom/Makefile | 2 +- drivers/thermal/qcom/tsens-8916.c | 107 +++++++++++++++++++++++++++++ drivers/thermal/qcom/tsens-common.c | 130 ++++++++++++++++++++++++++++++++++++
Just a small comment on organization, does it make sense to move tsens-common addition to the first patch, and then leave this patch only with the support for 8916 (like you did for the other chips)?
Quoted 110 lines
drivers/thermal/qcom/tsens.c | 1 + drivers/thermal/qcom/tsens.h | 11 +++ 5 files changed, 250 insertions(+), 1 deletion(-) create mode 100644 drivers/thermal/qcom/tsens-8916.c create mode 100644 drivers/thermal/qcom/tsens-common.cdrivers/thermal/qcom/Makefile +1
-1@@ -1,2 +1,2 @@ obj-$(CONFIG_QCOM_TSENS) += qcom_tsens.o -qcom_tsens-y += tsens.o +qcom_tsens-y += tsens.o tsens-common.o tsens-8916.odrivers/thermal/qcom/tsens-8916.c new file +90
-0@@ -0,0 +1,107 @@ +/* +* Copyright (c) 2015, The Linux Foundation. All rights reserved. +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License version 2 and +* only version 2 as published by the Free Software Foundation. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +*/ + +#include <linux/platform_device.h> +#include "tsens.h" + +/* eeprom layout data for 8916 */ +#define BASE0_MASK 0x0000007f +#define BASE1_MASK 0xfe000000 +#define BASE0_SHIFT 0 +#define BASE1_SHIFT 25 + +#define S0_P1_MASK 0x00000f80 +#define S1_P1_MASK 0x003e0000 +#define S2_P1_MASK 0xf8000000 +#define S3_P1_MASK 0x000003e0 +#define S4_P1_MASK 0x000f8000 + +#define S0_P2_MASK 0x0001f000 +#define S1_P2_MASK 0x07c00000 +#define S2_P2_MASK 0x0000001f +#define S3_P2_MASK 0x00007c00 +#define S4_P2_MASK 0x01f00000 + +#define S0_P1_SHIFT 7 +#define S1_P1_SHIFT 17 +#define S2_P1_SHIFT 27 +#define S3_P1_SHIFT 5 +#define S4_P1_SHIFT 15 + +#define S0_P2_SHIFT 12 +#define S1_P2_SHIFT 22 +#define S2_P2_SHIFT 0 +#define S3_P2_SHIFT 10 +#define S4_P2_SHIFT 20 + +#define CAL_SEL_MASK 0xe0000000 +#define CAL_SEL_SHIFT 29 + +static int calibrate_8916 (struct tsens_device *tmdev) +{ +int base0 =0 , base1 =0 , i; +u32 p1[5 ], p2[5 ]; +int mode =0 ; +u32 *qfprom_cdata, *qfprom_csel; + + qfprom_cdata = (u32 *)qfprom_read (tmdev->dev,"calib" ); +if (IS_ERR (qfprom_cdata)) +return PTR_ERR (qfprom_cdata); + + qfprom_csel = (u32 *)qfprom_read (tmdev->dev,"calib_sel" ); +if (IS_ERR (qfprom_csel)) +return PTR_ERR (qfprom_csel); + + mode = (qfprom_csel[0 ] &CAL_SEL_MASK ) >>CAL_SEL_SHIFT ; +dev_dbg (tmdev->dev,"calibration mode is %d\n" , mode); + +switch (mode) { +case TWO_PT_CALIB : + base1 = (qfprom_cdata[1 ] &BASE1_MASK ) >>BASE1_SHIFT ; + p2[0 ] = (qfprom_cdata[0 ] &S0_P2_MASK ) >>S0_P2_SHIFT ; + p2[1 ] = (qfprom_cdata[0 ] &S1_P2_MASK ) >>S1_P2_SHIFT ; + p2[2 ] = (qfprom_cdata[1 ] &S2_P2_MASK ) >>S2_P2_SHIFT ; + p2[3 ] = (qfprom_cdata[1 ] &S3_P2_MASK ) >>S3_P2_SHIFT ; + p2[4 ] = (qfprom_cdata[1 ] &S4_P2_MASK ) >>S4_P2_SHIFT ; +for (i =0 ; i < tmdev->num_sensors; i++) + p2[i] = ((base1 + p2[i]) <<3 ); +/* Fall through */ +case ONE_PT_CALIB2 : + base0 = (qfprom_cdata[0 ] &BASE0_MASK ); + p1[0 ] = (qfprom_cdata[0 ] &S0_P1_MASK ) >>S0_P1_SHIFT ; + p1[1 ] = (qfprom_cdata[0 ] &S1_P1_MASK ) >>S1_P1_SHIFT ; + p1[2 ] = (qfprom_cdata[0 ] &S2_P1_MASK ) >>S2_P1_SHIFT ; + p1[3 ] = (qfprom_cdata[1 ] &S3_P1_MASK ) >>S3_P1_SHIFT ; + p1[4 ] = (qfprom_cdata[1 ] &S4_P1_MASK ) >>S4_P1_SHIFT ; +for (i =0 ; i < tmdev->num_sensors; i++) + p1[i] = (((base0) + p1[i]) <<3 ); +break ; +default :
drivers/thermal/qcom/tsens-8916.c line 100
Quoted 10 lines
drivers/thermal/qcom/tsens-8916.c new file +10
-0+for (i =0 ; i < tmdev->num_sensors; i++) { + p1[i] =500 ; + p2[i] =780 ; + } +break ; + } + +compute_intercept_slope (tmdev, p1, p2, mode); + +return 0 ;
Can calibration fail ? In which cases?
Quoted 44 lines
drivers/thermal/qcom/tsens-8916.c new file +7
-0+} + +const struct tsens_ops ops_8916 = { + .init = init_common, + .calibrate = calibrate_8916, + .get_temp = get_temp_common, +};drivers/thermal/qcom/tsens-common.c new file +31
-0@@ -0,0 +1,130 @@ +/* +* Copyright (c) 2015, The Linux Foundation. All rights reserved. +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License version 2 and +* only version 2 as published by the Free Software Foundation. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +*/ + +#include <linux/platform_device.h> +#include <linux/nvmem-consumer.h> +#include <linux/err.h> +#include <linux/io.h> +#include <linux/of_address.h> +#include <linux/regmap.h> +#include "tsens.h" + +#define S0_ST_ADDR 0x1030 +#define SN_ADDR_OFFSET 0x4 +#define SN_ST_TEMP_MASK 0x3ff +#define CAL_DEGC_PT1 30 +#define CAL_DEGC_PT2 120 +#define SLOPE_FACTOR 1000 + +char *qfprom_read (struct device *dev,const char *cname) +{
drivers/thermal/qcom/tsens-common.c line 41
Quoted 10 lines
drivers/thermal/qcom/tsens-common.c new file +10
-0+struct nvmem_cell *cell; +ssize_t data; +char *ret; + + cell =nvmem_cell_get (dev, cname); +if (IS_ERR (cell)) +return ERR_CAST (cell); + + ret =nvmem_cell_read (cell, &data); +nvmem_cell_put (cell);
nip: add a blank line here.
Quoted 74 lines
drivers/thermal/qcom/tsens-common.c new file +74
-0+return ret; +} + +void compute_intercept_slope (struct tsens_device *tmdev,u32 *p1, +u32 *p2,u32 mode) +{ +int i; +int num, den; + +for (i =0 ; i < tmdev->num_sensors; i++) { +dev_dbg (tmdev->dev, +"sensor%d - data_point1:%#x data_point2:%#x\n" , + i, p1[i], p2[i]); + +if (mode ==TWO_PT_CALIB ) { +/* +* slope (m) = adc_code2 - adc_code1 (y2 - y1)/ +* temp_120_degc - temp_30_degc (x2 - x1) +*/ + num = p2[i] - p1[i]; + num *=SLOPE_FACTOR ; + den =CAL_DEGC_PT2 -CAL_DEGC_PT1 ; + tmdev->sensor[i].slope = num / den; + } + + tmdev->sensor[i].offset = (p1[i] *SLOPE_FACTOR ) - + (CAL_DEGC_PT1 * + tmdev->sensor[i].slope); +dev_dbg (tmdev->dev,"offset:%d\n" , tmdev->sensor[i].offset); + } +} + +static inline int code_to_degc (u32 adc_code,const struct tsens_sensor *s) +{ +int degc, num, den; + + num = (adc_code *SLOPE_FACTOR ) - s->offset; + den = s->slope; + +if (num >0 ) + degc = num + (den /2 ); +else if (num <0 ) + degc = num - (den /2 ); +else + degc = num; + + degc /= den; + +return degc; +} + +int get_temp_common (struct tsens_device *tmdev,int id,int *temp) +{ +struct tsens_sensor *s = &tmdev->sensor[id]; +u32 code; +unsigned int sensor_addr; +int last_temp =0 , ret; + + sensor_addr =S0_ST_ADDR + s->hw_id *SN_ADDR_OFFSET ; + ret =regmap_read (tmdev->map, sensor_addr, &code); +if (ret) +return ret; + last_temp = code &SN_ST_TEMP_MASK ; + + *temp =code_to_degc (last_temp, s) *1000 ; + +return 0 ; +} + +static const struct regmap_config tsens_config = { + .reg_bits =32 , + .val_bits =32 , + .reg_stride =4 , +};
drivers/thermal/qcom/tsens-common.c line 125
Quoted 10 lines
drivers/thermal/qcom/tsens-common.c new file +10
-0+ +int init_common (struct tsens_device *tmdev) +{ +void __iomem *base; + + base =of_iomap (tmdev->dev->of_node,0 ); +if (IS_ERR (base)) +return -EINVAL ; + + tmdev->map =devm_regmap_init_mmio (tmdev->dev, base, &tsens_config);
Should this function be marked as __init so devm_* works?
drivers/thermal/qcom/tsens-common.c line 127
Quoted 2 lines
drivers/thermal/qcom/tsens-common.c new file +2
-0+if (!tmdev->map) +return -ENODEV ;
Should you do iounmap?
Quoted 46 lines
drivers/thermal/qcom/tsens-common.c new file +3
-0+ +return 0 ; +}drivers/thermal/qcom/tsens.c +1
-0@@ -65,6 +65,7 @@ static SIMPLE_DEV_PM_OPS(tsens_pm_ops, tsens_suspend, tsens_resume);static const struct of_device_id tsens_table[] = { { .compatible ="qcom,msm8916-tsens" , + .data = &ops_8916, }, { .compatible ="qcom,msm8974-tsens" , },drivers/thermal/qcom/tsens.h +11
-0@@ -13,6 +13,10 @@#ifndef __QCOM_TSENS_H__#define __QCOM_TSENS_H__ +#define ONE_PT_CALIB 0x1 +#define ONE_PT_CALIB2 0x2 +#define TWO_PT_CALIB 0x3 +struct tsens_device ; struct tsens_sensor {@@ -55,4 +59,11 @@ struct tsens_device { struct tsens_sensor sensor[0]; }; +char *qfprom_read (struct device *,const char *); +void compute_intercept_slope (struct tsens_device *,u32 *,u32 *,u32 ); +int init_common (struct tsens_device *); +int get_temp_common (struct tsens_device *,int ,int *); + +extern const struct tsens_ops ops_8916; +#endif /* __QCOM_TSENS_H__ */ Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 2/8 thermal: qcom: tsens-8916: Add support for 8916 family of SoCs
Quoted 15 lines · Eduardo Valentin
Quoted 6 lines · Rajendra Nayak
Add support to calibrate sensors on 8916 family and also add common functions to read temperature from sensors (This can be reused on other SoCs having similar TSENS device)
The calibration data is read from eeprom using the generic nvmem framework apis.Quoted 7 lines
Based on the original code by Siddartha Mohanadoss and Stephen Boyd.
Signed-off-by Rajendra Nayak <[email protected]>--- drivers/thermal/qcom/Makefile | 2 +- drivers/thermal/qcom/tsens-8916.c | 107 +++++++++++++++++++++++++++++ drivers/thermal/qcom/tsens-common.c | 130 ++++++++++++++++++++++++++++++++++++
Quoted 3 lines
Just a small comment on organization, does it make sense to move tsens-common addition to the first patch, and then leave this patch only with the support for 8916 (like you did for the other chips)?
So the common code gets used for 8916 and hence I added it here as part of this patch. I can as well move it to the first patch in the series, should not be an issue.
Quoted 115 lines
Quoted 115 lines
drivers/thermal/qcom/tsens.c | 1 + drivers/thermal/qcom/tsens.h | 11 +++ 5 files changed, 250 insertions(+), 1 deletion(-) create mode 100644 drivers/thermal/qcom/tsens-8916.c create mode 100644 drivers/thermal/qcom/tsens-common.cdrivers/thermal/qcom/Makefile +1
-1@@ -1,2 +1,2 @@ obj-$(CONFIG_QCOM_TSENS) += qcom_tsens.o -qcom_tsens-y += tsens.o +qcom_tsens-y += tsens.o tsens-common.o tsens-8916.odrivers/thermal/qcom/tsens-8916.c new file +94
-0@@ -0,0 +1,107 @@ +/* +* Copyright (c) 2015, The Linux Foundation. All rights reserved. +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License version 2 and +* only version 2 as published by the Free Software Foundation. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +*/ + +#include <linux/platform_device.h> +#include "tsens.h" + +/* eeprom layout data for 8916 */ +#define BASE0_MASK 0x0000007f +#define BASE1_MASK 0xfe000000 +#define BASE0_SHIFT 0 +#define BASE1_SHIFT 25 + +#define S0_P1_MASK 0x00000f80 +#define S1_P1_MASK 0x003e0000 +#define S2_P1_MASK 0xf8000000 +#define S3_P1_MASK 0x000003e0 +#define S4_P1_MASK 0x000f8000 + +#define S0_P2_MASK 0x0001f000 +#define S1_P2_MASK 0x07c00000 +#define S2_P2_MASK 0x0000001f +#define S3_P2_MASK 0x00007c00 +#define S4_P2_MASK 0x01f00000 + +#define S0_P1_SHIFT 7 +#define S1_P1_SHIFT 17 +#define S2_P1_SHIFT 27 +#define S3_P1_SHIFT 5 +#define S4_P1_SHIFT 15 + +#define S0_P2_SHIFT 12 +#define S1_P2_SHIFT 22 +#define S2_P2_SHIFT 0 +#define S3_P2_SHIFT 10 +#define S4_P2_SHIFT 20 + +#define CAL_SEL_MASK 0xe0000000 +#define CAL_SEL_SHIFT 29 + +static int calibrate_8916 (struct tsens_device *tmdev) +{ +int base0 =0 , base1 =0 , i; +u32 p1[5 ], p2[5 ]; +int mode =0 ; +u32 *qfprom_cdata, *qfprom_csel; + + qfprom_cdata = (u32 *)qfprom_read (tmdev->dev,"calib" ); +if (IS_ERR (qfprom_cdata)) +return PTR_ERR (qfprom_cdata); + + qfprom_csel = (u32 *)qfprom_read (tmdev->dev,"calib_sel" ); +if (IS_ERR (qfprom_csel)) +return PTR_ERR (qfprom_csel); + + mode = (qfprom_csel[0 ] &CAL_SEL_MASK ) >>CAL_SEL_SHIFT ; +dev_dbg (tmdev->dev,"calibration mode is %d\n" , mode); + +switch (mode) { +case TWO_PT_CALIB : + base1 = (qfprom_cdata[1 ] &BASE1_MASK ) >>BASE1_SHIFT ; + p2[0 ] = (qfprom_cdata[0 ] &S0_P2_MASK ) >>S0_P2_SHIFT ; + p2[1 ] = (qfprom_cdata[0 ] &S1_P2_MASK ) >>S1_P2_SHIFT ; + p2[2 ] = (qfprom_cdata[1 ] &S2_P2_MASK ) >>S2_P2_SHIFT ; + p2[3 ] = (qfprom_cdata[1 ] &S3_P2_MASK ) >>S3_P2_SHIFT ; + p2[4 ] = (qfprom_cdata[1 ] &S4_P2_MASK ) >>S4_P2_SHIFT ; +for (i =0 ; i < tmdev->num_sensors; i++) + p2[i] = ((base1 + p2[i]) <<3 ); +/* Fall through */ +case ONE_PT_CALIB2 : + base0 = (qfprom_cdata[0 ] &BASE0_MASK ); + p1[0 ] = (qfprom_cdata[0 ] &S0_P1_MASK ) >>S0_P1_SHIFT ; + p1[1 ] = (qfprom_cdata[0 ] &S1_P1_MASK ) >>S1_P1_SHIFT ; + p1[2 ] = (qfprom_cdata[0 ] &S2_P1_MASK ) >>S2_P1_SHIFT ; + p1[3 ] = (qfprom_cdata[1 ] &S3_P1_MASK ) >>S3_P1_SHIFT ; + p1[4 ] = (qfprom_cdata[1 ] &S4_P1_MASK ) >>S4_P1_SHIFT ; +for (i =0 ; i < tmdev->num_sensors; i++) + p1[i] = (((base0) + p1[i]) <<3 ); +break ; +default : +for (i =0 ; i < tmdev->num_sensors; i++) { + p1[i] =500 ; + p2[i] =780 ; + }
Quoted 8 lines
drivers/thermal/qcom/tsens-8916.c line 100
Quoted 6 lines
drivers/thermal/qcom/tsens-8916.c new file +6
-0+break ; + } + +compute_intercept_slope (tmdev, p1, p2, mode); + +return 0 ;Can calibration fail ? In which cases?
yes, it can if the eeprom reads fail for instance.
Quoted 143 lines
Quoted 45 lines
drivers/thermal/qcom/tsens-8916.c new file +7
-0+} + +const struct tsens_ops ops_8916 = { + .init = init_common, + .calibrate = calibrate_8916, + .get_temp = get_temp_common, +};drivers/thermal/qcom/tsens-common.c new file +31
-0@@ -0,0 +1,130 @@ +/* +* Copyright (c) 2015, The Linux Foundation. All rights reserved. +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License version 2 and +* only version 2 as published by the Free Software Foundation. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +*/ + +#include <linux/platform_device.h> +#include <linux/nvmem-consumer.h> +#include <linux/err.h> +#include <linux/io.h> +#include <linux/of_address.h> +#include <linux/regmap.h> +#include "tsens.h" + +#define S0_ST_ADDR 0x1030 +#define SN_ADDR_OFFSET 0x4 +#define SN_ST_TEMP_MASK 0x3ff +#define CAL_DEGC_PT1 30 +#define CAL_DEGC_PT2 120 +#define SLOPE_FACTOR 1000 + +char *qfprom_read (struct device *dev,const char *cname) +{drivers/thermal/qcom/tsens-common.c line 41
Quoted 10 lines
drivers/thermal/qcom/tsens-common.c new file +10
-0+struct nvmem_cell *cell; +ssize_t data; +char *ret; + + cell =nvmem_cell_get (dev, cname); +if (IS_ERR (cell)) +return ERR_CAST (cell); + + ret =nvmem_cell_read (cell, &data); +nvmem_cell_put (cell);nip: add a blank line here.
Quoted 74 lines
drivers/thermal/qcom/tsens-common.c new file +74
-0+return ret; +} + +void compute_intercept_slope (struct tsens_device *tmdev,u32 *p1, +u32 *p2,u32 mode) +{ +int i; +int num, den; + +for (i =0 ; i < tmdev->num_sensors; i++) { +dev_dbg (tmdev->dev, +"sensor%d - data_point1:%#x data_point2:%#x\n" , + i, p1[i], p2[i]); + +if (mode ==TWO_PT_CALIB ) { +/* +* slope (m) = adc_code2 - adc_code1 (y2 - y1)/ +* temp_120_degc - temp_30_degc (x2 - x1) +*/ + num = p2[i] - p1[i]; + num *=SLOPE_FACTOR ; + den =CAL_DEGC_PT2 -CAL_DEGC_PT1 ; + tmdev->sensor[i].slope = num / den; + } + + tmdev->sensor[i].offset = (p1[i] *SLOPE_FACTOR ) - + (CAL_DEGC_PT1 * + tmdev->sensor[i].slope); +dev_dbg (tmdev->dev,"offset:%d\n" , tmdev->sensor[i].offset); + } +} + +static inline int code_to_degc (u32 adc_code,const struct tsens_sensor *s) +{ +int degc, num, den; + + num = (adc_code *SLOPE_FACTOR ) - s->offset; + den = s->slope; + +if (num >0 ) + degc = num + (den /2 ); +else if (num <0 ) + degc = num - (den /2 ); +else + degc = num; + + degc /= den; + +return degc; +} + +int get_temp_common (struct tsens_device *tmdev,int id,int *temp) +{ +struct tsens_sensor *s = &tmdev->sensor[id]; +u32 code; +unsigned int sensor_addr; +int last_temp =0 , ret; + + sensor_addr =S0_ST_ADDR + s->hw_id *SN_ADDR_OFFSET ; + ret =regmap_read (tmdev->map, sensor_addr, &code); +if (ret) +return ret; + last_temp = code &SN_ST_TEMP_MASK ; + + *temp =code_to_degc (last_temp, s) *1000 ; + +return 0 ; +} + +static const struct regmap_config tsens_config = { + .reg_bits =32 , + .val_bits =32 , + .reg_stride =4 , +};drivers/thermal/qcom/tsens-common.c line 125
Quoted 10 lines
drivers/thermal/qcom/tsens-common.c new file +10
-0+ +int init_common (struct tsens_device *tmdev) +{ +void __iomem *base; + + base =of_iomap (tmdev->dev->of_node,0 ); +if (IS_ERR (base)) +return -EINVAL ; + + tmdev->map =devm_regmap_init_mmio (tmdev->dev, base, &tsens_config);Should this function be marked as
__initso devm_* works?
Quoted 4 lines
drivers/thermal/qcom/tsens-common.c line 127
Quoted 2 lines
drivers/thermal/qcom/tsens-common.c new file +2
-0+if (!tmdev->map) +return -ENODEV ;Should you do iounmap?
yes, will fix these.
thanks,
Rajendra
Quoted 47 lines
Quoted 47 lines
drivers/thermal/qcom/tsens-common.c new file +3
-0+ +return 0 ; +}drivers/thermal/qcom/tsens.c +1
-0@@ -65,6 +65,7 @@ static SIMPLE_DEV_PM_OPS(tsens_pm_ops, tsens_suspend, tsens_resume);static const struct of_device_id tsens_table[] = { { .compatible ="qcom,msm8916-tsens" , + .data = &ops_8916, }, { .compatible ="qcom,msm8974-tsens" , },drivers/thermal/qcom/tsens.h +11
-0@@ -13,6 +13,10 @@#ifndef __QCOM_TSENS_H__#define __QCOM_TSENS_H__ +#define ONE_PT_CALIB 0x1 +#define ONE_PT_CALIB2 0x2 +#define TWO_PT_CALIB 0x3 +struct tsens_device ; struct tsens_sensor {@@ -55,4 +59,11 @@ struct tsens_device { struct tsens_sensor sensor[0]; }; +char *qfprom_read (struct device *,const char *); +void compute_intercept_slope (struct tsens_device *,u32 *,u32 *,u32 ); +int init_common (struct tsens_device *); +int get_temp_common (struct tsens_device *,int ,int *); + +extern const struct tsens_ops ops_8916; +#endif /* __QCOM_TSENS_H__ */ Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
Signature · 2 lines
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 3/8 thermal: qcom: tsens-8974: Add support for 8974 family of SoCs
In reply to Rajendra NayakAdd .calibrate support for 8974 family as part of tsens_ops.
Based on the original code by Siddartha Mohanadoss and Stephen Boyd.
--- drivers/thermal/qcom/Makefile | 2 +- drivers/thermal/qcom/tsens-8974.c | 239 ++++++++++++++++++++++++++++++++++++++ drivers/thermal/qcom/tsens.c | 1 + drivers/thermal/qcom/tsens.h | 2 +- 4 files changed, 242 insertions(+), 2 deletions(-) create mode 100644 drivers/thermal/qcom/tsens-8974.c
drivers/thermal/qcom/Makefile +1 -1
@@ -1,2 +1,2 @@ obj-$(CONFIG_QCOM_TSENS) += qcom_tsens.o -qcom_tsens-y += tsens.o tsens-common.o tsens-8916.o +qcom_tsens-y += tsens.o tsens-common.o tsens-8916.o tsens-8974.o
drivers/thermal/qcom/tsens-8974.c new file +239 -0
239 lines not on this page · raw message
drivers/thermal/qcom/tsens.c +1 -0
@@ -68,6 +68,7 @@ static const struct of_device_id tsens_table[] = { .data = &ops_8916, }, { .compatible = "qcom,msm8974-tsens", + .data = &ops_8974, }, {} };
drivers/thermal/qcom/tsens.h +1 -1
@@ -64,6 +64,6 @@ void compute_intercept_slope(struct tsens_device *, u32 *, u32 *, u32);int init_common (struct tsens_device *);int get_temp_common (struct tsens_device *,int ,int *); -extern const struct tsens_ops ops_8916; +extern const struct tsens_ops ops_8916, ops_8974;#endif /* __QCOM_TSENS_H__ */
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 4/8 thermal: qcom: tsens-8960: Add support for 8960 family of SoCs
In reply to Rajendra Nayak8960 family of SoCs have the TSENS device as part of GCC, hence the driver probes the virtual child device created by GCC and uses the parent to extract all DT properties and reuses the GCC regmap.
Also GCC/TSENS are part of a domain thats not always ON. Hence add .suspend and .resume hooks to save and restore some of the inited register context.
Also 8960 family have some of the TSENS init sequence thats required to be done by the HLOS driver (some later versions of TSENS do not export these registers to non-secure world, and hence need these initializations to be done by secure bootloaders)
8660 from the same family has just one sensor and hence some register offset/layout differences which need special handling in the driver.
Based on the original code from Siddartha Mohanadoss, Stephen Boyd and Narendran Rajan.
--- drivers/thermal/qcom/Makefile | 2 +- drivers/thermal/qcom/tsens-8960.c | 291 ++++++++++++++++++++++++++++++++++++++ drivers/thermal/qcom/tsens.c | 13 +- drivers/thermal/qcom/tsens.h | 2 +- 4 files changed, 302 insertions(+), 6 deletions(-) create mode 100644 drivers/thermal/qcom/tsens-8960.c
drivers/thermal/qcom/Makefile +1 -1
@@ -1,2 +1,2 @@ obj-$(CONFIG_QCOM_TSENS) += qcom_tsens.o -qcom_tsens-y += tsens.o tsens-common.o tsens-8916.o tsens-8974.o +qcom_tsens-y += tsens.o tsens-common.o tsens-8916.o tsens-8974.o tsens-8960.o
drivers/thermal/qcom/tsens-8960.c new file +291 -0
291 lines not on this page · raw message
drivers/thermal/qcom/tsens.c +9 -4
@@ -119,7 +119,11 @@ static int tsens_probe(struct platform_device *pdev)struct tsens_device *tmdev;const struct of_device_id *id; - dev = &pdev->dev; +if (pdev->dev.of_node) + dev = &pdev->dev; +else + dev = pdev->dev.parent; + np = dev->of_node; num =of_property_count_u32_elems (np,"qcom,tsens-slopes" );
@@ -141,10 +145,11 @@ static int tsens_probe(struct platform_device *pdev) &s->slope); id =of_match_node (tsens_table, np); -if (!id) -return -ENODEV ; +if (id) + tmdev->ops = id->data; +else + tmdev->ops = &ops_8960; - tmdev->ops = id->data;if (!tmdev->ops || !tmdev->ops->init || !tmdev->ops->calibrate || !tmdev->ops->get_temp)return -EINVAL ;
drivers/thermal/qcom/tsens.h +1 -1
@@ -64,6 +64,6 @@ void compute_intercept_slope(struct tsens_device *, u32 *, u32 *, u32);int init_common (struct tsens_device *);int get_temp_common (struct tsens_device *,int ,int *); -extern const struct tsens_ops ops_8916, ops_8974; +extern const struct tsens_ops ops_8960, ops_8916, ops_8974;#endif /* __QCOM_TSENS_H__ */
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 4/8 thermal: qcom: tsens-8960: Add support for 8960 family of SoCs
Quoted 156 lines · Rajendra Nayak
8960 family of SoCs have the TSENS device as part of GCC, hence the driver probes the virtual child device created by GCC and uses the parent to extract all DT properties and reuses the GCC regmap.
Also GCC/TSENS are part of a domain thats not always ON. Hence add .suspend and .resume hooks to save and restore some of the inited register context.
Also 8960 family have some of the TSENS init sequence thats required to be done by the HLOS driver (some later versions of TSENS do not export these registers to non-secure world, and hence need these initializations to be done by secure bootloaders)
8660 from the same family has just one sensor and hence some register offset/layout differences which need special handling in the driver.
Based on the original code from Siddartha Mohanadoss, Stephen Boyd and Narendran Rajan.
Signed-off-by Rajendra Nayak <[email protected]>--- drivers/thermal/qcom/Makefile | 2 +- drivers/thermal/qcom/tsens-8960.c | 291 ++++++++++++++++++++++++++++++++++++++ drivers/thermal/qcom/tsens.c | 13 +- drivers/thermal/qcom/tsens.h | 2 +- 4 files changed, 302 insertions(+), 6 deletions(-) create mode 100644 drivers/thermal/qcom/tsens-8960.cdrivers/thermal/qcom/Makefile +1
-1@@ -1,2 +1,2 @@ obj-$(CONFIG_QCOM_TSENS) += qcom_tsens.o -qcom_tsens-y += tsens.o tsens-common.o tsens-8916.o tsens-8974.o +qcom_tsens-y += tsens.o tsens-common.o tsens-8916.o tsens-8974.o tsens-8960.odrivers/thermal/qcom/tsens-8960.c new file +113
-0@@ -0,0 +1,291 @@ +/* +* Copyright (c) 2015, The Linux Foundation. All rights reserved. +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License version 2 and +* only version 2 as published by the Free Software Foundation. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +*/ + +#include <linux/platform_device.h> +#include <linux/delay.h> +#include <linux/bitops.h> +#include <linux/regmap.h> +#include "tsens.h" + +#define CAL_MDEGC 30000 + +#define CONFIG_ADDR 0x3640 +#define CONFIG_ADDR_8660 0x3620 +/* CONFIG_ADDR bitmasks */ +#define CONFIG 0x9b +#define CONFIG_MASK 0xf +#define CONFIG_8660 1 +#define CONFIG_SHIFT_8660 28 +#define CONFIG_MASK_8660 (3 << CONFIG_SHIFT_8660) + +#define STATUS_CNTL_ADDR_8064 0x3660 +#define CNTL_ADDR 0x3620 +/* CNTL_ADDR bitmasks */ +#define EN BIT(0) +#define SW_RST BIT(1) +#define SENSOR0_EN BIT(3) +#define SLP_CLK_ENA BIT(26) +#define SLP_CLK_ENA_8660 BIT(24) +#define MEASURE_PERIOD 1 +#define SENSOR0_SHIFT 3 + +/* INT_STATUS_ADDR bitmasks */ +#define MIN_STATUS_MASK BIT(0) +#define LOWER_STATUS_CLR BIT(1) +#define UPPER_STATUS_CLR BIT(2) +#define MAX_STATUS_MASK BIT(3) + +#define THRESHOLD_ADDR 0x3624 +/* THRESHOLD_ADDR bitmasks */ +#define THRESHOLD_MAX_LIMIT_SHIFT 24 +#define THRESHOLD_MIN_LIMIT_SHIFT 16 +#define THRESHOLD_UPPER_LIMIT_SHIFT 8 +#define THRESHOLD_LOWER_LIMIT_SHIFT 0 + +/* Initial temperature threshold values */ +#define LOWER_LIMIT_TH 0x50 +#define UPPER_LIMIT_TH 0xdf +#define MIN_LIMIT_TH 0x0 +#define MAX_LIMIT_TH 0xff + +#define S0_STATUS_ADDR 0x3628 +#define INT_STATUS_ADDR 0x363c +#define TRDY_MASK BIT(7) + +static int suspend_8960 (struct tsens_device *tmdev) +{ +int ret; +unsigned int mask; +struct regmap *map = tmdev->map; + + ret =regmap_read (map,THRESHOLD_ADDR , &tmdev->ctx.threshold); +if (ret) +return ret; + + ret =regmap_read (map,CNTL_ADDR , &tmdev->ctx.control); +if (ret) +return ret; + +if (tmdev->num_sensors >1 ) + mask =SLP_CLK_ENA |EN ; +else + mask =SLP_CLK_ENA_8660 |EN ; + + ret =regmap_update_bits (map,CNTL_ADDR , mask,0 ); +if (ret) +return ret; + + tmdev->trdy = false; + +return 0 ; +} + +static int resume_8960 (struct tsens_device *tmdev) +{ +int ret; +unsigned long reg_cntl; +struct regmap *map = tmdev->map; + + ret =regmap_update_bits (map,CNTL_ADDR ,SW_RST ,SW_RST ); +if (ret) +return ret; + +/* +* Separate CONFIG restore is not needed only for 8660 as +* config is part of CTRL Addr and its restored as such +*/ +if (tmdev->num_sensors >1 ) { + ret =regmap_update_bits (map,CONFIG_ADDR ,CONFIG_MASK ,CONFIG ); +if (ret) +return ret; + } +
drivers/thermal/qcom/tsens-8960.c line 123
Quoted 10 lines
drivers/thermal/qcom/tsens-8960.c new file +10
-0+ ret =regmap_write (map,THRESHOLD_ADDR , tmdev->ctx.threshold); +if (ret) +return ret; + + ret =regmap_write (map,CNTL_ADDR , tmdev->ctx.control); +if (ret) +return ret; + + reg_cntl = tmdev->ctx.control; + reg_cntl >>=SENSOR0_SHIFT ;
What the above two lines are doing? are they no-ops?
Quoted 108 lines
drivers/thermal/qcom/tsens-8960.c new file +108
-0+ +return 0 ; +} + +static int enable_8960 (struct tsens_device *tmdev,int id) +{ +int ret; +u32 reg, mask; + + ret =regmap_read (tmdev->map,CNTL_ADDR , ®); +if (ret) +return ret; + + mask =BIT (id +SENSOR0_SHIFT ); + ret =regmap_write (tmdev->map,CNTL_ADDR , reg |SW_RST ); +if (ret) +return ret; + +if (tmdev->num_sensors >1 ) + reg |= mask |SLP_CLK_ENA |EN ; +else + reg |= mask |SLP_CLK_ENA_8660 |EN ; + + tmdev->trdy = false; + ret =regmap_write (tmdev->map,CNTL_ADDR , reg); +if (ret) +return ret; + +return 0 ; +} + +static void disable_8960 (struct tsens_device *tmdev) +{ +int ret; +u32 reg_cntl; +u32 mask; + + mask =GENMASK (tmdev->num_sensors -1 ,0 ); + mask <<=SENSOR0_SHIFT ; + mask |=EN ; + + ret =regmap_read (tmdev->map,CNTL_ADDR , ®_cntl); +if (ret) +return ; + + reg_cntl &= ~mask; + +if (tmdev->num_sensors >1 ) + reg_cntl &= ~SLP_CLK_ENA ; +else + reg_cntl &= ~SLP_CLK_ENA_8660 ; + +regmap_write (tmdev->map,CNTL_ADDR , reg_cntl); +} + +static int init_8960 (struct tsens_device *tmdev) +{ +int ret, i; +u32 reg_cntl; + + tmdev->map =dev_get_regmap (tmdev->dev,NULL ); +if (!tmdev->map) +return -ENODEV ; + +/* +* The status registers for each sensor are discontiguous +* because some SoCs have 5 sensors while others have more +* but the control registers stay in the same place, i.e +* directly after the first 5 status registers. +*/ +for (i =0 ; i < tmdev->num_sensors; i++) { +if (i >=5 ) + tmdev->sensor[i].status =S0_STATUS_ADDR +40 ; + tmdev->sensor[i].status += i *4 ; + } + + reg_cntl =SW_RST ; + ret =regmap_update_bits (tmdev->map,CNTL_ADDR ,SW_RST , reg_cntl); +if (ret) +return ret; + +if (tmdev->num_sensors >1 ) { + reg_cntl |=SLP_CLK_ENA | (MEASURE_PERIOD <<18 ); + reg_cntl &= ~SW_RST ; + ret =regmap_update_bits (tmdev->map,CONFIG_ADDR , +CONFIG_MASK ,CONFIG ); + }else { + reg_cntl |=SLP_CLK_ENA_8660 | (MEASURE_PERIOD <<16 ); + reg_cntl &= ~CONFIG_MASK_8660 ; + reg_cntl |=CONFIG_8660 <<CONFIG_SHIFT_8660 ; + } + + reg_cntl |=GENMASK (tmdev->num_sensors -1 ,0 ) <<SENSOR0_SHIFT ; + ret =regmap_write (tmdev->map,CNTL_ADDR , reg_cntl); +if (ret) +return ret; + + reg_cntl |=EN ; + ret =regmap_write (tmdev->map,CNTL_ADDR , reg_cntl); +if (ret) +return ret; + +return 0 ; +} + +static int calibrate_8960 (struct tsens_device *tmdev) +{ +int i;
drivers/thermal/qcom/tsens-8960.c line 241
Quoted 10 lines
drivers/thermal/qcom/tsens-8960.c new file +10
-0+char *data; + +ssize_t num_read = tmdev->num_sensors; +struct tsens_sensor *s = tmdev->sensor; + + data =qfprom_read (tmdev->dev,"calib" ); +if (IS_ERR (data)) + data =qfprom_read (tmdev->dev,"calib_backup" ); +if (IS_ERR (data)) +return PTR_ERR (data);
Oh.. so calibration can fail on prom reads...
Quoted 16 lines
drivers/thermal/qcom/tsens-8960.c new file +16
-0+ +for (i =0 ; i < num_read; i++, s++) + s->offset =CAL_MDEGC - s->slope * data[i]; + +return 0 ; +} + +/* Temperature on y axis and ADC-code on x-axis */ +static inline int code_to_mdegC (u32 adc_code,const struct tsens_sensor *s) +{ +return adc_code * s->slope + s->offset; +} + +static int get_temp_8960 (struct tsens_device *tmdev,int id,int *temp) +{ +int ret;
drivers/thermal/qcom/tsens-8960.c line 267
Quoted 10 lines
drivers/thermal/qcom/tsens-8960.c new file +10
-0+u32 code, trdy; +const struct tsens_sensor *s = &tmdev->sensor[id]; + +if (!tmdev->trdy) { + ret =regmap_read (tmdev->map,INT_STATUS_ADDR , &trdy); +if (ret) +return ret; +while (!(trdy &TRDY_MASK )) { +usleep_range (1000 ,1100 ); +regmap_read (tmdev->map,INT_STATUS_ADDR , &trdy);
Is there a maximum amount of tries?
Would that be any case in which this would be stuck busy looping ?
drivers/thermal/qcom/tsens-8960.c line 278
Quoted 11 lines
drivers/thermal/qcom/tsens-8960.c new file +11
-0+ } + tmdev->trdy = true; + } + + ret =regmap_read (tmdev->map, s->status, &code); +if (ret) +return ret; + + *temp =code_to_mdegC (code, s); + +dev_dbg (tmdev->dev,"Sensor%d temp is: %d" , id, *temp);
I suppose the thermal tracing could be probably better than a dev_dbg?
Quoted 18 lines
drivers/thermal/qcom/tsens-8960.c new file +13
-0+ +return 0 ; +} + +const struct tsens_ops ops_8960 = { + .init = init_8960, + .calibrate = calibrate_8960, + .get_temp = get_temp_8960, + .enable = enable_8960, + .disable = disable_8960, + .suspend = suspend_8960, + .resume = resume_8960, +};drivers/thermal/qcom/tsens.c +0
-0
drivers/thermal/qcom/tsens.c static int tsens_probe(struct platform_device *pdev) · line 126
Quoted 9 lines
drivers/thermal/qcom/tsens.c +5
-1@@ -119,7 +119,11 @@ static int tsens_probe(struct platform_device *pdev)struct tsens_device *tmdev;const struct of_device_id *id; - dev = &pdev->dev; +if (pdev->dev.of_node) + dev = &pdev->dev; +else + dev = pdev->dev.parent; +
Should this be part of the patch that adds tsens.c?
Quoted 34 lines
drivers/thermal/qcom/tsens.c +4
-3np = dev->of_node; num =of_property_count_u32_elems (np,"qcom,tsens-slopes" );@@ -141,10 +145,11 @@ static int tsens_probe(struct platform_device *pdev) &s->slope); id =of_match_node (tsens_table, np); -if (!id) -return -ENODEV ; +if (id) + tmdev->ops = id->data; +else + tmdev->ops = &ops_8960; - tmdev->ops = id->data;if (!tmdev->ops || !tmdev->ops->init || !tmdev->ops->calibrate || !tmdev->ops->get_temp)return -EINVAL ;drivers/thermal/qcom/tsens.h +1
-1@@ -64,6 +64,6 @@ void compute_intercept_slope(struct tsens_device *, u32 *, u32 *, u32);int init_common (struct tsens_device *);int get_temp_common (struct tsens_device *,int ,int *); -extern const struct tsens_ops ops_8916, ops_8974; +extern const struct tsens_ops ops_8960, ops_8916, ops_8974;#endif /* __QCOM_TSENS_H__ */ Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 4/8 thermal: qcom: tsens-8960: Add support for 8960 family of SoCs
Quoted 161 lines · Eduardo Valentin
Quoted 160 lines · Rajendra Nayak
8960 family of SoCs have the TSENS device as part of GCC, hence the driver probes the virtual child device created by GCC and uses the parent to extract all DT properties and reuses the GCC regmap.
Also GCC/TSENS are part of a domain thats not always ON. Hence add .suspend and .resume hooks to save and restore some of the inited register context.
Also 8960 family have some of the TSENS init sequence thats required to be done by the HLOS driver (some later versions of TSENS do not export these registers to non-secure world, and hence need these initializations to be done by secure bootloaders)
8660 from the same family has just one sensor and hence some register offset/layout differences which need special handling in the driver.
Based on the original code from Siddartha Mohanadoss, Stephen Boyd and Narendran Rajan.
Signed-off-by Rajendra Nayak <[email protected]>--- drivers/thermal/qcom/Makefile | 2 +- drivers/thermal/qcom/tsens-8960.c | 291 ++++++++++++++++++++++++++++++++++++++ drivers/thermal/qcom/tsens.c | 13 +- drivers/thermal/qcom/tsens.h | 2 +- 4 files changed, 302 insertions(+), 6 deletions(-) create mode 100644 drivers/thermal/qcom/tsens-8960.cdrivers/thermal/qcom/Makefile +1
-1@@ -1,2 +1,2 @@ obj-$(CONFIG_QCOM_TSENS) += qcom_tsens.o -qcom_tsens-y += tsens.o tsens-common.o tsens-8916.o tsens-8974.o +qcom_tsens-y += tsens.o tsens-common.o tsens-8916.o tsens-8974.o tsens-8960.odrivers/thermal/qcom/tsens-8960.c new file +117
-0@@ -0,0 +1,291 @@ +/* +* Copyright (c) 2015, The Linux Foundation. All rights reserved. +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License version 2 and +* only version 2 as published by the Free Software Foundation. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +*/ + +#include <linux/platform_device.h> +#include <linux/delay.h> +#include <linux/bitops.h> +#include <linux/regmap.h> +#include "tsens.h" + +#define CAL_MDEGC 30000 + +#define CONFIG_ADDR 0x3640 +#define CONFIG_ADDR_8660 0x3620 +/* CONFIG_ADDR bitmasks */ +#define CONFIG 0x9b +#define CONFIG_MASK 0xf +#define CONFIG_8660 1 +#define CONFIG_SHIFT_8660 28 +#define CONFIG_MASK_8660 (3 << CONFIG_SHIFT_8660) + +#define STATUS_CNTL_ADDR_8064 0x3660 +#define CNTL_ADDR 0x3620 +/* CNTL_ADDR bitmasks */ +#define EN BIT(0) +#define SW_RST BIT(1) +#define SENSOR0_EN BIT(3) +#define SLP_CLK_ENA BIT(26) +#define SLP_CLK_ENA_8660 BIT(24) +#define MEASURE_PERIOD 1 +#define SENSOR0_SHIFT 3 + +/* INT_STATUS_ADDR bitmasks */ +#define MIN_STATUS_MASK BIT(0) +#define LOWER_STATUS_CLR BIT(1) +#define UPPER_STATUS_CLR BIT(2) +#define MAX_STATUS_MASK BIT(3) + +#define THRESHOLD_ADDR 0x3624 +/* THRESHOLD_ADDR bitmasks */ +#define THRESHOLD_MAX_LIMIT_SHIFT 24 +#define THRESHOLD_MIN_LIMIT_SHIFT 16 +#define THRESHOLD_UPPER_LIMIT_SHIFT 8 +#define THRESHOLD_LOWER_LIMIT_SHIFT 0 + +/* Initial temperature threshold values */ +#define LOWER_LIMIT_TH 0x50 +#define UPPER_LIMIT_TH 0xdf +#define MIN_LIMIT_TH 0x0 +#define MAX_LIMIT_TH 0xff + +#define S0_STATUS_ADDR 0x3628 +#define INT_STATUS_ADDR 0x363c +#define TRDY_MASK BIT(7) + +static int suspend_8960 (struct tsens_device *tmdev) +{ +int ret; +unsigned int mask; +struct regmap *map = tmdev->map; + + ret =regmap_read (map,THRESHOLD_ADDR , &tmdev->ctx.threshold); +if (ret) +return ret; + + ret =regmap_read (map,CNTL_ADDR , &tmdev->ctx.control); +if (ret) +return ret; + +if (tmdev->num_sensors >1 ) + mask =SLP_CLK_ENA |EN ; +else + mask =SLP_CLK_ENA_8660 |EN ; + + ret =regmap_update_bits (map,CNTL_ADDR , mask,0 ); +if (ret) +return ret; + + tmdev->trdy = false; + +return 0 ; +} + +static int resume_8960 (struct tsens_device *tmdev) +{ +int ret; +unsigned long reg_cntl; +struct regmap *map = tmdev->map; + + ret =regmap_update_bits (map,CNTL_ADDR ,SW_RST ,SW_RST ); +if (ret) +return ret; + +/* +* Separate CONFIG restore is not needed only for 8660 as +* config is part of CTRL Addr and its restored as such +*/ +if (tmdev->num_sensors >1 ) { + ret =regmap_update_bits (map,CONFIG_ADDR ,CONFIG_MASK ,CONFIG ); +if (ret) +return ret; + } + + ret =regmap_write (map,THRESHOLD_ADDR , tmdev->ctx.threshold); +if (ret) +return ret; +
Quoted 8 lines
drivers/thermal/qcom/tsens-8960.c line 123
Quoted 6 lines
drivers/thermal/qcom/tsens-8960.c new file +6
-0+ ret =regmap_write (map,CNTL_ADDR , tmdev->ctx.control); +if (ret) +return ret; + + reg_cntl = tmdev->ctx.control; + reg_cntl >>=SENSOR0_SHIFT ;What the above two lines are doing? are they no-ops?
Looks like some leftover bits which I should have removed. Will remove it.
Quoted 150 lines
Quoted 109 lines
drivers/thermal/qcom/tsens-8960.c new file +108
-0+ +return 0 ; +} + +static int enable_8960 (struct tsens_device *tmdev,int id) +{ +int ret; +u32 reg, mask; + + ret =regmap_read (tmdev->map,CNTL_ADDR , ®); +if (ret) +return ret; + + mask =BIT (id +SENSOR0_SHIFT ); + ret =regmap_write (tmdev->map,CNTL_ADDR , reg |SW_RST ); +if (ret) +return ret; + +if (tmdev->num_sensors >1 ) + reg |= mask |SLP_CLK_ENA |EN ; +else + reg |= mask |SLP_CLK_ENA_8660 |EN ; + + tmdev->trdy = false; + ret =regmap_write (tmdev->map,CNTL_ADDR , reg); +if (ret) +return ret; + +return 0 ; +} + +static void disable_8960 (struct tsens_device *tmdev) +{ +int ret; +u32 reg_cntl; +u32 mask; + + mask =GENMASK (tmdev->num_sensors -1 ,0 ); + mask <<=SENSOR0_SHIFT ; + mask |=EN ; + + ret =regmap_read (tmdev->map,CNTL_ADDR , ®_cntl); +if (ret) +return ; + + reg_cntl &= ~mask; + +if (tmdev->num_sensors >1 ) + reg_cntl &= ~SLP_CLK_ENA ; +else + reg_cntl &= ~SLP_CLK_ENA_8660 ; + +regmap_write (tmdev->map,CNTL_ADDR , reg_cntl); +} + +static int init_8960 (struct tsens_device *tmdev) +{ +int ret, i; +u32 reg_cntl; + + tmdev->map =dev_get_regmap (tmdev->dev,NULL ); +if (!tmdev->map) +return -ENODEV ; + +/* +* The status registers for each sensor are discontiguous +* because some SoCs have 5 sensors while others have more +* but the control registers stay in the same place, i.e +* directly after the first 5 status registers. +*/ +for (i =0 ; i < tmdev->num_sensors; i++) { +if (i >=5 ) + tmdev->sensor[i].status =S0_STATUS_ADDR +40 ; + tmdev->sensor[i].status += i *4 ; + } + + reg_cntl =SW_RST ; + ret =regmap_update_bits (tmdev->map,CNTL_ADDR ,SW_RST , reg_cntl); +if (ret) +return ret; + +if (tmdev->num_sensors >1 ) { + reg_cntl |=SLP_CLK_ENA | (MEASURE_PERIOD <<18 ); + reg_cntl &= ~SW_RST ; + ret =regmap_update_bits (tmdev->map,CONFIG_ADDR , +CONFIG_MASK ,CONFIG ); + }else { + reg_cntl |=SLP_CLK_ENA_8660 | (MEASURE_PERIOD <<16 ); + reg_cntl &= ~CONFIG_MASK_8660 ; + reg_cntl |=CONFIG_8660 <<CONFIG_SHIFT_8660 ; + } + + reg_cntl |=GENMASK (tmdev->num_sensors -1 ,0 ) <<SENSOR0_SHIFT ; + ret =regmap_write (tmdev->map,CNTL_ADDR , reg_cntl); +if (ret) +return ret; + + reg_cntl |=EN ; + ret =regmap_write (tmdev->map,CNTL_ADDR , reg_cntl); +if (ret) +return ret; + +return 0 ; +} + +static int calibrate_8960 (struct tsens_device *tmdev) +{ +int i;drivers/thermal/qcom/tsens-8960.c line 241
Quoted 10 lines
drivers/thermal/qcom/tsens-8960.c new file +10
-0+char *data; + +ssize_t num_read = tmdev->num_sensors; +struct tsens_sensor *s = tmdev->sensor; + + data =qfprom_read (tmdev->dev,"calib" ); +if (IS_ERR (data)) + data =qfprom_read (tmdev->dev,"calib_backup" ); +if (IS_ERR (data)) +return PTR_ERR (data);Oh.. so calibration can fail on prom reads...
Quoted 16 lines
drivers/thermal/qcom/tsens-8960.c new file +16
-0+ +for (i =0 ; i < num_read; i++, s++) + s->offset =CAL_MDEGC - s->slope * data[i]; + +return 0 ; +} + +/* Temperature on y axis and ADC-code on x-axis */ +static inline int code_to_mdegC (u32 adc_code,const struct tsens_sensor *s) +{ +return adc_code * s->slope + s->offset; +} + +static int get_temp_8960 (struct tsens_device *tmdev,int id,int *temp) +{ +int ret;drivers/thermal/qcom/tsens-8960.c line 267
Quoted 10 lines
drivers/thermal/qcom/tsens-8960.c new file +10
-0+u32 code, trdy; +const struct tsens_sensor *s = &tmdev->sensor[id]; + +if (!tmdev->trdy) { + ret =regmap_read (tmdev->map,INT_STATUS_ADDR , &trdy); +if (ret) +return ret; +while (!(trdy &TRDY_MASK )) { +usleep_range (1000 ,1100 ); +regmap_read (tmdev->map,INT_STATUS_ADDR , &trdy);Is there a maximum amount of tries?
Quoted 2 lines
Would that be any case in which this would be stuck busy looping ?
right, I'll put some sensible timeout in.
Quoted 5 lines
Quoted 5 lines
drivers/thermal/qcom/tsens-8960.c new file +5
-0+ } + tmdev->trdy = true; + } + + ret =regmap_read (tmdev->map, s->status, &code);
Quoted 8 lines
drivers/thermal/qcom/tsens-8960.c line 278
Quoted 6 lines
drivers/thermal/qcom/tsens-8960.c new file +6
-0+if (ret) +return ret; + + *temp =code_to_mdegC (code, s); + +dev_dbg (tmdev->dev,"Sensor%d temp is: %d" , id, *temp);I suppose the thermal tracing could be probably better than a
dev_dbg?
Okay, I'll take a look at thermal tracing.
Quoted 22 lines
Quoted 22 lines
drivers/thermal/qcom/tsens-8960.c new file +13
-0+ +return 0 ; +} + +const struct tsens_ops ops_8960 = { + .init = init_8960, + .calibrate = calibrate_8960, + .get_temp = get_temp_8960, + .enable = enable_8960, + .disable = disable_8960, + .suspend = suspend_8960, + .resume = resume_8960, +};drivers/thermal/qcom/tsens.c +0
-0@@ -119,7 +119,11 @@ static int tsens_probe(struct platform_device *pdev)struct tsens_device *tmdev;const struct of_device_id *id;
Quoted 8 lines
drivers/thermal/qcom/tsens.c static int tsens_probe(struct platform_device *pdev) · line 126
Quoted 6 lines
drivers/thermal/qcom/tsens.c +5
-1- dev = &pdev->dev; +if (pdev->dev.of_node) + dev = &pdev->dev; +else + dev = pdev->dev.parent; +Should this be part of the patch that adds
tsens.c?
This is needed only because tsens is part of gcc in 8960. So I kept the change here so its easier to co-relate why its needed.
regards,
Rajendra
Quoted 35 lines
Quoted 35 lines
drivers/thermal/qcom/tsens.c +4
-3np = dev->of_node; num =of_property_count_u32_elems (np,"qcom,tsens-slopes" );@@ -141,10 +145,11 @@ static int tsens_probe(struct platform_device *pdev) &s->slope); id =of_match_node (tsens_table, np); -if (!id) -return -ENODEV ; +if (id) + tmdev->ops = id->data; +else + tmdev->ops = &ops_8960; - tmdev->ops = id->data;if (!tmdev->ops || !tmdev->ops->init || !tmdev->ops->calibrate || !tmdev->ops->get_temp)return -EINVAL ;drivers/thermal/qcom/tsens.h +1
-1@@ -64,6 +64,6 @@ void compute_intercept_slope(struct tsens_device *, u32 *, u32 *, u32);int init_common (struct tsens_device *);int get_temp_common (struct tsens_device *,int ,int *); -extern const struct tsens_ops ops_8916, ops_8974; +extern const struct tsens_ops ops_8960, ops_8916, ops_8974;#endif /* __QCOM_TSENS_H__ */ Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
Signature · 2 lines
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 5/8 arm: dts: msm8974: Add thermal zones, tsens and qfprom nodes
In reply to Rajendra NayakAdd thermal zones, tsens and qfprom nodes
--- arch/arm/boot/dts/qcom-msm8974.dtsi | 105 ++++++++++++++++++++++++++++++++++++ 1 file changed, 105 insertions(+)
arch/arm/boot/dts/qcom-msm8974.dtsi +105 -0
@@ -86,6 +86,88 @@ }; }; + thermal-zones { + cpu-thermal0 { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens 5>; + + trips { + cpu_alert0: trip at 0 { + temperature = <75000>; + hysteresis = <2000>; + type = "passive"; + }; + cpu_crit0: trip at 1 { + temperature = <95000>; + hysteresis = <2000>; + type = "critical"; + }; + }; + }; + + cpu-thermal1 { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens 6>; + + trips { + cpu_alert1: trip at 0 { + temperature = <75000>; + hysteresis = <2000>; + type = "passive"; + }; + cpu_crit1: trip at 1 { + temperature = <95000>; + hysteresis = <2000>; + type = "critical"; + }; + }; + }; + + cpu-thermal2 { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens 7>; + + trips { + cpu_alert2: trip at 0 { + temperature = <75000>; + hysteresis = <2000>; + type = "passive"; + }; + cpu_crit2: trip at 1 { + temperature = <95000>; + hysteresis = <2000>; + type = "critical"; + }; + }; + }; + + cpu-thermal3 { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens 8>; + + trips { + cpu_alert3: trip at 0 { + temperature = <75000>; + hysteresis = <2000>; + type = "passive"; + }; + cpu_crit3: trip at 1 { + temperature = <95000>; + hysteresis = <2000>; + type = "critical"; + }; + }; + }; + }; + cpu-pmu { compatible = "qcom,krait-pmu"; interrupts = <1 7 0xf04>;
@@ -114,6 +196,29 @@ <0xf9002000 0x1000>; }; + qfprom: qfprom at fc4bc000 { + #address-cells = <1>; + #size-cells = <1>; + compatible = "qcom,qfprom"; + reg = <0xfc4bc000 0x1000>; + tsens_calib: calib at d0 { + reg = <0xd0 0x18>; + }; + tsens_backup: backup at 440 { + reg = <0x440 0x10>; + }; + }; + + tsens: thermal-sensor at fc4a8000 { + compatible = "qcom,msm8974-tsens"; + reg = <0xfc4a8000 0x2000>; + nvmem-cells = <&tsens_calib>, <&tsens_backup>; + nvmem-cell-names = "calib", "calib_backup"; + qcom,tsens-slopes = <3200 3200 3200 3200 3200 3200 + 3200 3200 3200 3200 3200>; + #thermal-sensor-cells = <1>; + }; + timer at f9020000 { #address-cells = <1>; #size-cells = <1>;
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 6/8 arm: dts: apq8064: Add thermal zones, tsens and qfprom nodes
In reply to Rajendra NayakTSENS is part of GCC, hence add TSENS properties as part of GCC node. Also add thermal zones and qfprom nodes.
Update GCC bindings doc to mention the possibility of optional TSENS properties that can be part of GCC node.
--- .../devicetree/bindings/clock/qcom,gcc.txt | 20 ++++ arch/arm/boot/dts/qcom-apq8064.dtsi | 101 +++++++++++++++++++++ 2 files changed, 121 insertions(+)
Documentation/devicetree/bindings/clock/qcom,gcc.txt +20 -0
@@ -18,6 +18,13 @@ Required properties : - #clock-cells : shall contain 1 - #reset-cells : shall contain 1 +Optional properties: +- Qualcomm TSENS (thermal sensor device) on some devices can +be part of GCC and hence the TSENS properties can also be +part of the GCC/clock-controller node. +For more details on the TSENS properties please refer +Documentation/devicetree/bindings/thermal/qcom-tsens.txt + Example: clock-controller at 900000 { compatible = "qcom,gcc-msm8960";
@@ -25,3 +32,16 @@ Example: #clock-cells = <1>; #reset-cells = <1>; }; + +Example of GCC with TSENS properties: + clock-controller at 900000 { + compatible = "qcom,gcc-apq8064"; + reg = <0x00900000 0x4000>; + nvmem-cells = <&tsens_calib>, <&tsens_backup>; + nvmem-cell-names = "calib", "calib_backup"; + qcom,tsens-slopes = <1176 1176 1154 1176 1111 + 1132 1132 1199 1132 1199 1132>; + #clock-cells = <1>; + #reset-cells = <1>; + #thermal-sensor-cells = <1>; + };
arch/arm/boot/dts/qcom-apq8064.dtsi +101 -0
118 lines not on this page · raw message
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 7/8 arm: dts: apq8084: Add thermal zones, tsens and qfprom nodes
In reply to Rajendra NayakAdd thermal zones, tsens and qfprom nodes
--- arch/arm/boot/dts/qcom-apq8084.dtsi | 105 ++++++++++++++++++++++++++++++++++++ 1 file changed, 105 insertions(+)
arch/arm/boot/dts/qcom-apq8084.dtsi +105 -0
@@ -75,6 +75,88 @@ }; }; + thermal-zones { + cpu-thermal0 { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens 5>; + + trips { + cpu_alert0: trip at 0 { + temperature = <75000>; + hysteresis = <2000>; + type = "passive"; + }; + cpu_crit0: trip at 1 { + temperature = <95000>; + hysteresis = <2000>; + type = "critical"; + }; + }; + }; + + cpu-thermal1 { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens 6>; + + trips { + cpu_alert1: trip at 0 { + temperature = <75000>; + hysteresis = <2000>; + type = "passive"; + }; + cpu_crit1: trip at 1 { + temperature = <95000>; + hysteresis = <2000>; + type = "critical"; + }; + }; + }; + + cpu-thermal2 { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens 7>; + + trips { + cpu_alert2: trip at 0 { + temperature = <75000>; + hysteresis = <2000>; + type = "passive"; + }; + cpu_crit2: trip at 1 { + temperature = <95000>; + hysteresis = <2000>; + type = "critical"; + }; + }; + }; + + cpu-thermal3 { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens 8>; + + trips { + cpu_alert3: trip at 0 { + temperature = <75000>; + hysteresis = <2000>; + type = "passive"; + }; + cpu_crit3: trip at 1 { + temperature = <95000>; + hysteresis = <2000>; + type = "critical"; + }; + }; + }; + }; + cpu-pmu { compatible = "qcom,krait-pmu"; interrupts = <1 7 0xf04>;
@@ -103,6 +185,29 @@ <0xf9002000 0x1000>; }; + qfprom: qfprom at fc4bc000 { + #address-cells = <1>; + #size-cells = <1>; + compatible = "qcom,qfprom"; + reg = <0xfc4bc000 0x1000>; + tsens_calib: calib at d0 { + reg = <0xd0 0x18>; + }; + tsens_backup: backup at 440 { + reg = <0x440 0x10>; + }; + }; + + tsens: thermal-sensor at fc4a8000 { + compatible = "qcom,msm8974-tsens"; + reg = <0xfc4a8000 0x2000>; + nvmem-cells = <&tsens_calib>, <&tsens_backup>; + nvmem-cell-names = "calib", "calib_backup"; + qcom,tsens-slopes = <3200 3200 3200 3200 3200 3200 + 3200 3200 3200 3200 3200>; + #thermal-sensor-cells = <1>; + }; + timer at f9020000 { #address-cells = <1>; #size-cells = <1>;
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v4 8/8 arm64: dts: msm8916: Add thermal zones, tsens and qfprom nodes
In reply to Rajendra NayakAdd thermal zones, tsens and qfprom nodes
--- arch/arm64/boot/dts/qcom/msm8916.dtsi | 66 +++++++++++++++++++++++++++++++++++ 1 file changed, 66 insertions(+)
arch/arm64/boot/dts/qcom/msm8916.dtsi +66 -0
@@ -68,6 +68,49 @@ }; }; + thermal-zones { + cpu-thermal0 { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens 4>; + + trips { + cpu_alert0: trip at 0 { + temperature = <100000>; + hysteresis = <2000>; + type = "passive"; + }; + cpu_crit0: trip at 1 { + temperature = <125000>; + hysteresis = <2000>; + type = "critical"; + }; + }; + }; + + cpu-thermal1 { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens 3>; + + trips { + cpu_alert1: trip at 0 { + temperature = <100000>; + hysteresis = <2000>; + type = "passive"; + }; + cpu_crit1: trip at 1 { + temperature = <125000>; + hysteresis = <2000>; + type = "critical"; + }; + }; + }; + + }; + timer { compatible = "arm,armv8-timer"; interrupts = <GIC_PPI 2 (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>,
@@ -392,6 +435,29 @@ interrupt-controller; #interrupt-cells = <4>; }; + + qfprom: qfprom at 5c000 { + compatible = "qcom,qfprom"; + reg = <0x5c000 0x1000>; + #address-cells = <1>; + #size-cells = <1>; + tsens_caldata: caldata at d0 { + reg = <0xd0 0x8>; + }; + tsens_calsel: calsel at ec { + reg = <0xec 0x4>; + }; + }; + + tsens: thermal-sensor at 4a8000 { + compatible = "qcom,msm8916-tsens"; + reg = <0x4a8000 0x2000>; + nvmem-cells = <&tsens_caldata>, <&tsens_calsel>; + nvmem-cell-names = "calib", "calib_sel"; + qcom,tsens-slopes = <3200 3200 3200 3200 3200>; + qcom,sensor-id = <0 1 2 4 5>; + #thermal-sensor-cells = <1>; + }; }; };
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
v4 cover qcom: Add support for TSENS driver
In reply to Rajendra NayakRajendra,
Quoted 6 lines · Rajendra Nayak
Patches 1/8 to 4/8 will need to go via the thermal tree/Eduardo. Patches 5/8 to 8/8 will need to go via qcom-msm tree/Andy.
Eduardo, can you please take a look at the patches and let me know if you see any issues.
Thanks for your taking this over. I am assuming this superseeds the work by Narendran.
Thanks.
Quoted 76 lines
Current set of patches apply on 4.3-rc4. Need to pull in clk-next (for a dependent patch) to be able to test on ifc6410 board.
Changes since v3:
* Dropped 'clk: qcom: create virtual child device for TSENS' which is picked up by Stephen
* Updated GCC bindings with optional TSENS propertiesChanges since v2:
* Minor review fixes from Stephen/Punit and rebase on 4.3-rc4Changes since v1:
* Created virtual tsens device from gcc driver for 8960, with DT having a single node for gcc and tsens
* Minor fixes with rebasing on 4.3-rc1Changes since RFC:
* Added support for 8916 and 8084
* Based off the latest nvmem framework patches [1]
* Minor review fixes for comments mostly from LinaThis is an attempt to have a single TSENS driver for the different versions of the TSENS IP that exist, on different qcom msm/apq SoCs'
Support is added for msm8916, msm8960 and msm8974 families.A lot of the work is based of original code from Stephen Boyd and Siddartha Mohanadoss. I have also picked some of what Narendran Rajan did in his attempt to upstream the support for 8960 family. I could not keep the original authorship on any of the patches because I ended up moving the code around quite a bit in an effort to have a single driver for the various devices. I would be glad to change the authorship for any of the patches if needed.
Rajendra Nayak (8):
thermal: qcom: tsens: Add a skeletal TSENS drivers
thermal: qcom: tsens-8916: Add support for 8916 family of SoCs
thermal: qcom: tsens-8974: Add support for 8974 family of SoCs
thermal: qcom: tsens-8960: Add support for 8960 family of SoCs
arm: dts: msm8974: Add thermal zones, tsens and qfprom nodes
arm: dts: apq8064: Add thermal zones, tsens and qfprom nodes
arm: dts: apq8084: Add thermal zones, tsens and qfprom nodes
arm64: dts: msm8916: Add thermal zones, tsens and qfprom nodes.../devicetree/bindings/clock/qcom,gcc.txt | 20 ++ .../devicetree/bindings/thermal/qcom-tsens.txt | 33 +++ arch/arm/boot/dts/qcom-apq8064.dtsi | 101 +++++++ arch/arm/boot/dts/qcom-apq8084.dtsi | 105 ++++++++ arch/arm/boot/dts/qcom-msm8974.dtsi | 105 ++++++++ arch/arm64/boot/dts/qcom/msm8916.dtsi | 66 +++++ drivers/thermal/Kconfig | 5 + drivers/thermal/Makefile | 1 + drivers/thermal/qcom/Kconfig | 10 + drivers/thermal/qcom/Makefile | 2 + drivers/thermal/qcom/tsens-8916.c | 107 ++++++++ drivers/thermal/qcom/tsens-8960.c | 291 +++++++++++++++++++++ drivers/thermal/qcom/tsens-8974.c | 239 +++++++++++++++++ drivers/thermal/qcom/tsens-common.c | 130 +++++++++ drivers/thermal/qcom/tsens.c | 206 +++++++++++++++ drivers/thermal/qcom/tsens.h | 69 +++++ 16 files changed, 1490 insertions(+) create mode 100644 Documentation/devicetree/bindings/thermal/qcom-tsens.txt create mode 100644 drivers/thermal/qcom/Kconfig create mode 100644 drivers/thermal/qcom/Makefile create mode 100644 drivers/thermal/qcom/tsens-8916.c create mode 100644 drivers/thermal/qcom/tsens-8960.c create mode 100644 drivers/thermal/qcom/tsens-8974.c create mode 100644 drivers/thermal/qcom/tsens-common.c create mode 100644 drivers/thermal/qcom/tsens.c create mode 100644 drivers/thermal/qcom/tsens.hSignature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
v4 cover qcom: Add support for TSENS driver
Quoted 6 lines · Eduardo Valentin
Rajendra,
Quoted 3 lines · Rajendra Nayak
Patches 1/8 to 4/8 will need to go via the thermal tree/Eduardo. Patches 5/8 to 8/8 will need to go via qcom-msm tree/Andy.
Quoted 6 lines
Quoted 3 lines
Eduardo, can you please take a look at the patches and let me know if you see any issues.
Thanks for your taking this over. I am assuming this superseeds the work by Narendran.
https://patchwork.kernel.org/patch/5870241/
Quoted 79 lines
Thanks.
Quoted 76 lines
Current set of patches apply on 4.3-rc4. Need to pull in clk-next (for a dependent patch) to be able to test on ifc6410 board.
Changes since v3:
* Dropped 'clk: qcom: create virtual child device for TSENS' which is picked up by Stephen
* Updated GCC bindings with optional TSENS propertiesChanges since v2:
* Minor review fixes from Stephen/Punit and rebase on 4.3-rc4Changes since v1:
* Created virtual tsens device from gcc driver for 8960, with DT having a single node for gcc and tsens
* Minor fixes with rebasing on 4.3-rc1Changes since RFC:
* Added support for 8916 and 8084
* Based off the latest nvmem framework patches [1]
* Minor review fixes for comments mostly from LinaThis is an attempt to have a single TSENS driver for the different versions of the TSENS IP that exist, on different qcom msm/apq SoCs'
Support is added for msm8916, msm8960 and msm8974 families.A lot of the work is based of original code from Stephen Boyd and Siddartha Mohanadoss. I have also picked some of what Narendran Rajan did in his attempt to upstream the support for 8960 family. I could not keep the original authorship on any of the patches because I ended up moving the code around quite a bit in an effort to have a single driver for the various devices. I would be glad to change the authorship for any of the patches if needed.
Rajendra Nayak (8):
thermal: qcom: tsens: Add a skeletal TSENS drivers
thermal: qcom: tsens-8916: Add support for 8916 family of SoCs
thermal: qcom: tsens-8974: Add support for 8974 family of SoCs
thermal: qcom: tsens-8960: Add support for 8960 family of SoCs
arm: dts: msm8974: Add thermal zones, tsens and qfprom nodes
arm: dts: apq8064: Add thermal zones, tsens and qfprom nodes
arm: dts: apq8084: Add thermal zones, tsens and qfprom nodes
arm64: dts: msm8916: Add thermal zones, tsens and qfprom nodes.../devicetree/bindings/clock/qcom,gcc.txt | 20 ++ .../devicetree/bindings/thermal/qcom-tsens.txt | 33 +++ arch/arm/boot/dts/qcom-apq8064.dtsi | 101 +++++++ arch/arm/boot/dts/qcom-apq8084.dtsi | 105 ++++++++ arch/arm/boot/dts/qcom-msm8974.dtsi | 105 ++++++++ arch/arm64/boot/dts/qcom/msm8916.dtsi | 66 +++++ drivers/thermal/Kconfig | 5 + drivers/thermal/Makefile | 1 + drivers/thermal/qcom/Kconfig | 10 + drivers/thermal/qcom/Makefile | 2 + drivers/thermal/qcom/tsens-8916.c | 107 ++++++++ drivers/thermal/qcom/tsens-8960.c | 291 +++++++++++++++++++++ drivers/thermal/qcom/tsens-8974.c | 239 +++++++++++++++++ drivers/thermal/qcom/tsens-common.c | 130 +++++++++ drivers/thermal/qcom/tsens.c | 206 +++++++++++++++ drivers/thermal/qcom/tsens.h | 69 +++++ 16 files changed, 1490 insertions(+) create mode 100644 Documentation/devicetree/bindings/thermal/qcom-tsens.txt create mode 100644 drivers/thermal/qcom/Kconfig create mode 100644 drivers/thermal/qcom/Makefile create mode 100644 drivers/thermal/qcom/tsens-8916.c create mode 100644 drivers/thermal/qcom/tsens-8960.c create mode 100644 drivers/thermal/qcom/tsens-8974.c create mode 100644 drivers/thermal/qcom/tsens-common.c create mode 100644 drivers/thermal/qcom/tsens.c create mode 100644 drivers/thermal/qcom/tsens.hSignature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
v4 cover qcom: Add support for TSENS driver
In reply to Eduardo ValentinHi Eduardo,
Quoted 6 lines · Eduardo Valentin
Rajendra,
Quoted 3 lines · Rajendra Nayak
Patches 1/8 to 4/8 will need to go via the thermal tree/Eduardo. Patches 5/8 to 8/8 will need to go via qcom-msm tree/Andy.
Quoted 6 lines
Quoted 3 lines
Eduardo, can you please take a look at the patches and let me know if you see any issues.
Thanks for your taking this over. I am assuming this superseeds the work by Narendran.
Yes, thats correct. I took Naren's work to add support for msm8960 family and created a single driver to work across msm8960 and msm8974/8916/8084 SoCs.
regards,
Rajendra
v4 cover qcom: Add support for TSENS driver
In reply to Rajendra NayakQuoted 5 lines · Rajendra Nayak
Patches 1/8 to 4/8 will need to go via the thermal tree/Eduardo. Patches 5/8 to 8/8 will need to go via qcom-msm tree/Andy.
Eduardo, can you please take a look at the patches and let me know if you see any issues.
I have sent a couple of comments, most of them are not a big deal. But please, have a look on what concerns the thermal bindings. I want to reuse what we have as much as possible.
The other point is regarding locking. Given that you have several sensors, per device, is there any need to have extra locking on top of what the thermal framework provides? Say, in the case a single device gets in use in different thermal zones, would the accesses to the thermal zone attempt to read registers shared by the sensors within the device?
Quoted 77 lines
Current set of patches apply on 4.3-rc4. Need to pull in clk-next (for a dependent patch) to be able to test on ifc6410 board.
Changes since v3:
* Dropped 'clk: qcom: create virtual child device for TSENS' which is picked up by Stephen
* Updated GCC bindings with optional TSENS propertiesChanges since v2:
* Minor review fixes from Stephen/Punit and rebase on 4.3-rc4Changes since v1:
* Created virtual tsens device from gcc driver for 8960, with DT having a single node for gcc and tsens
* Minor fixes with rebasing on 4.3-rc1Changes since RFC:
* Added support for 8916 and 8084
* Based off the latest nvmem framework patches [1]
* Minor review fixes for comments mostly from LinaThis is an attempt to have a single TSENS driver for the different versions of the TSENS IP that exist, on different qcom msm/apq SoCs'
Support is added for msm8916, msm8960 and msm8974 families.A lot of the work is based of original code from Stephen Boyd and Siddartha Mohanadoss. I have also picked some of what Narendran Rajan did in his attempt to upstream the support for 8960 family. I could not keep the original authorship on any of the patches because I ended up moving the code around quite a bit in an effort to have a single driver for the various devices. I would be glad to change the authorship for any of the patches if needed.
Rajendra Nayak (8):
thermal: qcom: tsens: Add a skeletal TSENS drivers
thermal: qcom: tsens-8916: Add support for 8916 family of SoCs
thermal: qcom: tsens-8974: Add support for 8974 family of SoCs
thermal: qcom: tsens-8960: Add support for 8960 family of SoCs
arm: dts: msm8974: Add thermal zones, tsens and qfprom nodes
arm: dts: apq8064: Add thermal zones, tsens and qfprom nodes
arm: dts: apq8084: Add thermal zones, tsens and qfprom nodes
arm64: dts: msm8916: Add thermal zones, tsens and qfprom nodes.../devicetree/bindings/clock/qcom,gcc.txt | 20 ++ .../devicetree/bindings/thermal/qcom-tsens.txt | 33 +++ arch/arm/boot/dts/qcom-apq8064.dtsi | 101 +++++++ arch/arm/boot/dts/qcom-apq8084.dtsi | 105 ++++++++ arch/arm/boot/dts/qcom-msm8974.dtsi | 105 ++++++++ arch/arm64/boot/dts/qcom/msm8916.dtsi | 66 +++++ drivers/thermal/Kconfig | 5 + drivers/thermal/Makefile | 1 + drivers/thermal/qcom/Kconfig | 10 + drivers/thermal/qcom/Makefile | 2 + drivers/thermal/qcom/tsens-8916.c | 107 ++++++++ drivers/thermal/qcom/tsens-8960.c | 291 +++++++++++++++++++++ drivers/thermal/qcom/tsens-8974.c | 239 +++++++++++++++++ drivers/thermal/qcom/tsens-common.c | 130 +++++++++ drivers/thermal/qcom/tsens.c | 206 +++++++++++++++ drivers/thermal/qcom/tsens.h | 69 +++++ 16 files changed, 1490 insertions(+) create mode 100644 Documentation/devicetree/bindings/thermal/qcom-tsens.txt create mode 100644 drivers/thermal/qcom/Kconfig create mode 100644 drivers/thermal/qcom/Makefile create mode 100644 drivers/thermal/qcom/tsens-8916.c create mode 100644 drivers/thermal/qcom/tsens-8960.c create mode 100644 drivers/thermal/qcom/tsens-8974.c create mode 100644 drivers/thermal/qcom/tsens-common.c create mode 100644 drivers/thermal/qcom/tsens.c create mode 100644 drivers/thermal/qcom/tsens.hSignature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
v4 cover qcom: Add support for TSENS driver
Quoted 10 lines · Eduardo Valentin
Quoted 5 lines · Rajendra Nayak
Patches 1/8 to 4/8 will need to go via the thermal tree/Eduardo. Patches 5/8 to 8/8 will need to go via qcom-msm tree/Andy.
Eduardo, can you please take a look at the patches and let me know if you see any issues.
I have sent a couple of comments, most of them are not a big deal. But please, have a look on what concerns the thermal bindings. I want to reuse what we have as much as possible.
Sure, I'll take a look at the existing bindings.
Quoted 7 lines
The other point is regarding locking. Given that you have several sensors, per device, is there any need to have extra locking on top of what the thermal framework provides? Say, in the case a single device gets in use in different thermal zones, would the accesses to the thermal zone attempt to read registers shared by the sensors within the device?
I don't see a case where this should happen, but I will check again to see if there a possibility of ending up with a situation like this and if it needs additional locking.
Thanks Eduardo for the review.
regards,
Rajendra
Quoted 78 lines
Quoted 78 lines
Current set of patches apply on 4.3-rc4. Need to pull in clk-next (for a dependent patch) to be able to test on ifc6410 board.
Changes since v3:
* Dropped 'clk: qcom: create virtual child device for TSENS' which is picked up by Stephen
* Updated GCC bindings with optional TSENS propertiesChanges since v2:
* Minor review fixes from Stephen/Punit and rebase on 4.3-rc4Changes since v1:
* Created virtual tsens device from gcc driver for 8960, with DT having a single node for gcc and tsens
* Minor fixes with rebasing on 4.3-rc1Changes since RFC:
* Added support for 8916 and 8084
* Based off the latest nvmem framework patches [1]
* Minor review fixes for comments mostly from LinaThis is an attempt to have a single TSENS driver for the different versions of the TSENS IP that exist, on different qcom msm/apq SoCs'
Support is added for msm8916, msm8960 and msm8974 families.A lot of the work is based of original code from Stephen Boyd and Siddartha Mohanadoss. I have also picked some of what Narendran Rajan did in his attempt to upstream the support for 8960 family. I could not keep the original authorship on any of the patches because I ended up moving the code around quite a bit in an effort to have a single driver for the various devices. I would be glad to change the authorship for any of the patches if needed.
Rajendra Nayak (8):
thermal: qcom: tsens: Add a skeletal TSENS drivers
thermal: qcom: tsens-8916: Add support for 8916 family of SoCs
thermal: qcom: tsens-8974: Add support for 8974 family of SoCs
thermal: qcom: tsens-8960: Add support for 8960 family of SoCs
arm: dts: msm8974: Add thermal zones, tsens and qfprom nodes
arm: dts: apq8064: Add thermal zones, tsens and qfprom nodes
arm: dts: apq8084: Add thermal zones, tsens and qfprom nodes
arm64: dts: msm8916: Add thermal zones, tsens and qfprom nodes.../devicetree/bindings/clock/qcom,gcc.txt | 20 ++ .../devicetree/bindings/thermal/qcom-tsens.txt | 33 +++ arch/arm/boot/dts/qcom-apq8064.dtsi | 101 +++++++ arch/arm/boot/dts/qcom-apq8084.dtsi | 105 ++++++++ arch/arm/boot/dts/qcom-msm8974.dtsi | 105 ++++++++ arch/arm64/boot/dts/qcom/msm8916.dtsi | 66 +++++ drivers/thermal/Kconfig | 5 + drivers/thermal/Makefile | 1 + drivers/thermal/qcom/Kconfig | 10 + drivers/thermal/qcom/Makefile | 2 + drivers/thermal/qcom/tsens-8916.c | 107 ++++++++ drivers/thermal/qcom/tsens-8960.c | 291 +++++++++++++++++++++ drivers/thermal/qcom/tsens-8974.c | 239 +++++++++++++++++ drivers/thermal/qcom/tsens-common.c | 130 +++++++++ drivers/thermal/qcom/tsens.c | 206 +++++++++++++++ drivers/thermal/qcom/tsens.h | 69 +++++ 16 files changed, 1490 insertions(+) create mode 100644 Documentation/devicetree/bindings/thermal/qcom-tsens.txt create mode 100644 drivers/thermal/qcom/Kconfig create mode 100644 drivers/thermal/qcom/Makefile create mode 100644 drivers/thermal/qcom/tsens-8916.c create mode 100644 drivers/thermal/qcom/tsens-8960.c create mode 100644 drivers/thermal/qcom/tsens-8974.c create mode 100644 drivers/thermal/qcom/tsens-common.c create mode 100644 drivers/thermal/qcom/tsens.c create mode 100644 drivers/thermal/qcom/tsens.hSignature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
Signature · 2 lines
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation