devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Amit Kucheria <amitk@kernel.org>,
	Thara Gopinath <thara.gopinath@gmail.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Zhang Rui <rui.zhang@intel.com>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Shawn Guo <shawn.guo@linaro.org>,
	linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v5 09/20] thermal/drivers/tsens: Support using nvmem cells for calibration data
Date: Thu, 29 Dec 2022 13:23:16 +0100	[thread overview]
Message-ID: <ecd974a7-6e46-b8c4-8c3d-70712a13400c@linaro.org> (raw)
In-Reply-To: <CAA8EJpoCT1fDb-aeeq=V28HWq=wkcTN9tVC98y0iCDvdk8JKkA@mail.gmail.com>



On 29.12.2022 12:52, Dmitry Baryshkov wrote:
> On Thu, 29 Dec 2022 at 13:47, Konrad Dybcio <konrad.dybcio@linaro.org> wrote:
>> On 29.12.2022 12:42, Dmitry Baryshkov wrote:
>>> On Thu, 29 Dec 2022 at 12:47, Konrad Dybcio <konrad.dybcio@linaro.org> wrote:
>>>> On 29.12.2022 04:00, Dmitry Baryshkov wrote:
>>>>> Add a unified function using nvmem cells for parsing the calibration
>>>>> data rather than parsing the calibration blob manually.
>>>>>
>>>>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>>>> ---
>>>>>  drivers/thermal/qcom/tsens-v0_1.c | 15 ++++++
>>>>>  drivers/thermal/qcom/tsens-v1.c   | 11 ++++-
>>>>>  drivers/thermal/qcom/tsens.c      | 76 +++++++++++++++++++++++++++++++
>>>>>  drivers/thermal/qcom/tsens.h      |  5 ++
>>>>>  4 files changed, 106 insertions(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/drivers/thermal/qcom/tsens-v0_1.c b/drivers/thermal/qcom/tsens-v0_1.c
>>>>> index 579028ea48f4..6c9e491f9559 100644
>>>>> --- a/drivers/thermal/qcom/tsens-v0_1.c
>>>>> +++ b/drivers/thermal/qcom/tsens-v0_1.c
>>>>> @@ -229,6 +229,11 @@ static int calibrate_8916(struct tsens_priv *priv)
>>>>>       u32 p1[5], p2[5];
>>>>>       int mode = 0;
>>>>>       u32 *qfprom_cdata, *qfprom_csel;
>>>>> +     int ret;
>>>>> +
>>>>> +     ret = tsens_calibrate_nvmem(priv, 3);
>>>>> +     if (!ret)
>>>>> +             return 0;
>>>>>
>>>>>       qfprom_cdata = (u32 *)qfprom_read(priv->dev, "calib");
>>>>>       if (IS_ERR(qfprom_cdata))
>>>>> @@ -286,6 +291,11 @@ static int calibrate_8939(struct tsens_priv *priv)
>>>>>       int mode = 0;
>>>>>       u32 *qfprom_cdata;
>>>>>       u32 cdata[4];
>>>>> +     int ret;
>>>>> +
>>>>> +     ret = tsens_calibrate_common(priv);
>>>>> +     if (!ret)
>>>>> +             return 0;
>>>>>
>>>>>       qfprom_cdata = (u32 *)qfprom_read(priv->dev, "calib");
>>>>>       if (IS_ERR(qfprom_cdata))
>>>>> @@ -486,6 +496,11 @@ static int calibrate_9607(struct tsens_priv *priv)
>>>>>       u32 p1[5], p2[5];
>>>>>       int mode = 0;
>>>>>       u32 *qfprom_cdata;
>>>>> +     int ret;
>>>>> +
>>>>> +     ret = tsens_calibrate_common(priv);
>>>>> +     if (!ret)
>>>>> +             return 0;
>>>>>
>>>>>       qfprom_cdata = (u32 *)qfprom_read(priv->dev, "calib");
>>>>>       if (IS_ERR(qfprom_cdata))
>>>>> diff --git a/drivers/thermal/qcom/tsens-v1.c b/drivers/thermal/qcom/tsens-v1.c
>>>>> index 83c2853546d0..5bba75a845c5 100644
>>>>> --- a/drivers/thermal/qcom/tsens-v1.c
>>>>> +++ b/drivers/thermal/qcom/tsens-v1.c
>>>>> @@ -143,7 +143,11 @@ static int calibrate_v1(struct tsens_priv *priv)
>>>>>       u32 p1[10], p2[10];
>>>>>       u32 mode = 0, lsb = 0, msb = 0;
>>>>>       u32 *qfprom_cdata;
>>>>> -     int i;
>>>>> +     int i, ret;
>>>>> +
>>>>> +     ret = tsens_calibrate_common(priv);
>>>>> +     if (!ret)
>>>>> +             return 0;
>>>>>
>>>>>       qfprom_cdata = (u32 *)qfprom_read(priv->dev, "calib");
>>>>>       if (IS_ERR(qfprom_cdata))
>>>>> @@ -209,6 +213,11 @@ static int calibrate_8976(struct tsens_priv *priv)
>>>>>       u32 p1[11], p2[11];
>>>>>       int mode = 0, tmp = 0;
>>>>>       u32 *qfprom_cdata;
>>>>> +     int ret;
>>>>> +
>>>>> +     ret = tsens_calibrate_common(priv);
>>>>> +     if (!ret)
>>>>> +             return 0;
>>>>>
>>>>>       qfprom_cdata = (u32 *)qfprom_read(priv->dev, "calib");
>>>>>       if (IS_ERR(qfprom_cdata))
>>>>> diff --git a/drivers/thermal/qcom/tsens.c b/drivers/thermal/qcom/tsens.c
>>>>> index b191e19df93d..ce568a68de4a 100644
>>>>> --- a/drivers/thermal/qcom/tsens.c
>>>>> +++ b/drivers/thermal/qcom/tsens.c
>>>>> @@ -70,6 +70,82 @@ char *qfprom_read(struct device *dev, const char *cname)
>>>>>       return ret;
>>>>>  }
>>>>>
>>>>> +int tsens_calibrate_nvmem(struct tsens_priv *priv, int shift)
>>>>> +{
>>>>> +     u32 mode;
>>>>> +     u32 base1, base2;
>>>>> +     u32 p1[MAX_SENSORS], p2[MAX_SENSORS];
>>>>> +     char name[] = "sXX_pY"; /* s10_p1 */
>>>>> +     int i, ret;
>>>>> +
>>>>> +     if (priv->num_sensors > MAX_SENSORS)
>>>>> +             return -EINVAL;
>>>>> +
>>>>> +     ret = nvmem_cell_read_variable_le_u32(priv->dev, "mode", &mode);
>>>>> +     if (ret == -ENOENT)
>>>>> +             dev_warn(priv->dev, "Please migrate to separate nvmem cells for calibration data\n");
>>>>> +     if (ret < 0)
>>>>> +             return ret;
>>>>> +
>>>>> +     dev_dbg(priv->dev, "calibration mode is %d\n", mode);
>>>>> +
>>>>> +     ret = nvmem_cell_read_variable_le_u32(priv->dev, "base1", &base1);
>>>>> +     if (ret < 0)
>>>>> +             return ret;
>>>>> +
>>>>> +     ret = nvmem_cell_read_variable_le_u32(priv->dev, "base2", &base2);
>>>>> +     if (ret < 0)
>>>>> +             return ret;
>>>>> +
>>>>> +     for (i = 0; i < priv->num_sensors; i++) {
>>>>> +             ret = snprintf(name, sizeof(name), "s%d_p1", priv->sensor[i].hw_id);
>>>> I think you forgot to update the underscore to a hyphen here
>>>> (unless the nvmem api does some magic internally).
>>>
>>> No. Please see the nvmem-cell-names property of the tsens nodes. It
>>> uses underscores. Then OF code translates this sX_pY string into an
>>> index in the nvmem-cells array or phandles. The sX-pY@ZZ node name is
>>> not used during lookups at all.
>> Right, I overlooked that!
>>
>>>
>>>>
>>>> Konrad
>>>>> +             if (ret < 0)
>>>>> +                     return ret;
>>>>> +
>>>>> +             ret = nvmem_cell_read_variable_le_u32(priv->dev, name, &p1[i]);
>>>>> +             if (ret)
>>>>> +                     return ret;
>>>>> +
>>>>> +             ret = snprintf(name, sizeof(name), "s%d_p2", priv->sensor[i].hw_id);
>>>>> +             if (ret < 0)
>>>>> +                     return ret;
>>>>> +
>>>>> +             ret = nvmem_cell_read_variable_le_u32(priv->dev, name, &p2[i]);
>>>>> +             if (ret)
>>>>> +                     return ret;
>>>>> +     }
>>>>> +
>>>>> +     switch (mode) {
>>>>> +     case ONE_PT_CALIB:
>>>>> +             for (i = 0; i < priv->num_sensors; i++)
>>>>> +                     p1[i] = p1[i] + (base1 << shift);
>>>>> +             break;
>>>>> +     case TWO_PT_CALIB:
>>>>> +             for (i = 0; i < priv->num_sensors; i++)
>>>>> +                     p2[i] = (p2[i] + base2) << shift;
>>>>> +             fallthrough;
>>>>> +     case ONE_PT_CALIB2:
>>>>> +             for (i = 0; i < priv->num_sensors; i++)
>>>>> +                     p1[i] = (p1[i] + base1) << shift;
>>>>> +             break;
>>>>> +     default:
>>>>> +             dev_dbg(priv->dev, "calibrationless mode\n");
>> This could be a dev_warn, as we usually don't expect it to happen.
> 
> I'm not so sure here. Current code handles this case without any
> warnings, as one of the expected cases So, I don't think the rework
> should start emitting warnings.
Right, perhaps that's something to consider at a different time.

Konrad
> 
>> Other than that:
>>
>> Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>>
>> Konrad
>>>>> +             for (i = 0; i < priv->num_sensors; i++) {
>>>>> +                     p1[i] = 500;
>>>>> +                     p2[i] = 780;
>>>>> +             }
>>>>> +     }
>>>>> +
>>>>> +     compute_intercept_slope(priv, p1, p2, mode);
>>>>> +
>>>>> +     return 0;
>>>>> +}
>>>>> +
>>>>> +int tsens_calibrate_common(struct tsens_priv *priv)
>>>>> +{
>>>>> +     return tsens_calibrate_nvmem(priv, 2);
>>>>> +}
>>>>> +
>>>>>  /*
>>>>>   * Use this function on devices where slope and offset calculations
>>>>>   * depend on calibration data read from qfprom. On others the slope
>>>>> diff --git a/drivers/thermal/qcom/tsens.h b/drivers/thermal/qcom/tsens.h
>>>>> index 7dd5fc246894..645ae02438fa 100644
>>>>> --- a/drivers/thermal/qcom/tsens.h
>>>>> +++ b/drivers/thermal/qcom/tsens.h
>>>>> @@ -6,6 +6,7 @@
>>>>>  #ifndef __QCOM_TSENS_H__
>>>>>  #define __QCOM_TSENS_H__
>>>>>
>>>>> +#define NO_PT_CALIB          0x0
>>>>>  #define ONE_PT_CALIB         0x1
>>>>>  #define ONE_PT_CALIB2                0x2
>>>>>  #define TWO_PT_CALIB         0x3
>>>>> @@ -17,6 +18,8 @@
>>>>>  #define THRESHOLD_MAX_ADC_CODE       0x3ff
>>>>>  #define THRESHOLD_MIN_ADC_CODE       0x0
>>>>>
>>>>> +#define MAX_SENSORS 16
>>>>> +
>>>>>  #include <linux/interrupt.h>
>>>>>  #include <linux/thermal.h>
>>>>>  #include <linux/regmap.h>
>>>>> @@ -582,6 +585,8 @@ struct tsens_priv {
>>>>>  };
>>>>>
>>>>>  char *qfprom_read(struct device *dev, const char *cname);
>>>>> +int tsens_calibrate_nvmem(struct tsens_priv *priv, int shift);
>>>>> +int tsens_calibrate_common(struct tsens_priv *priv);
>>>>>  void compute_intercept_slope(struct tsens_priv *priv, u32 *pt1, u32 *pt2, u32 mode);
>>>>>  int init_common(struct tsens_priv *priv);
>>>>>  int get_temp_tsens_valid(const struct tsens_sensor *s, int *temp);
>>>
>>>
>>>
> 
> 
> 

  reply	other threads:[~2022-12-29 12:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-29  3:00 [PATCH v5 00/20] thermal/drivers/tsens: specify nvmem cells in DT rather than parsing them manually Dmitry Baryshkov
2022-12-29  3:00 ` [PATCH v5 01/20] dt-bindings: thermal: tsens: add msm8956 compat Dmitry Baryshkov
2022-12-29  3:00 ` [PATCH v5 02/20] dt-bindings: thermal: tsens: support per-sensor calibration cells Dmitry Baryshkov
2022-12-29  8:35   ` Krzysztof Kozlowski
2022-12-29 11:49     ` Dmitry Baryshkov
2023-01-01 15:56       ` Krzysztof Kozlowski
2023-01-01 19:18         ` Dmitry Baryshkov
2023-01-02  8:32           ` Krzysztof Kozlowski
2022-12-29  3:00 ` [PATCH v5 03/20] dt-bindings: thermal: tsens: add per-sensor cells for msm8974 Dmitry Baryshkov
2022-12-29  3:00 ` [PATCH v5 04/20] thermal/drivers/tsens: Drop unnecessary hw_ids Dmitry Baryshkov
2022-12-29  3:00 ` [PATCH v5 05/20] thermal/drivers/tsens: Drop msm8976-specific defines Dmitry Baryshkov
2022-12-29  3:00 ` [PATCH v5 06/20] thermal/drivers/tsens: Sort out msm8976 vs msm8956 data Dmitry Baryshkov
2022-12-29  3:00 ` [PATCH v5 07/20] thermal/drivers/tsens: fix slope values for msm8939 Dmitry Baryshkov
2022-12-29 12:05   ` Shawn Guo
2022-12-29  3:00 ` [PATCH v5 08/20] thermal/drivers/tsens: limit num_sensors to 9 " Dmitry Baryshkov
2022-12-29 12:22   ` Shawn Guo
2022-12-29  3:00 ` [PATCH v5 09/20] thermal/drivers/tsens: Support using nvmem cells for calibration data Dmitry Baryshkov
2022-12-29 10:47   ` Konrad Dybcio
2022-12-29 11:42     ` Dmitry Baryshkov
2022-12-29 11:47       ` Konrad Dybcio
2022-12-29 11:52         ` Dmitry Baryshkov
2022-12-29 12:23           ` Konrad Dybcio [this message]
2022-12-29  3:00 ` [PATCH v5 10/20] thermal/drivers/tsens: Support using nvmem cells for msm8974 calibration Dmitry Baryshkov
2022-12-29  3:00 ` [PATCH v5 11/20] thermal/drivers/tsens: Rework legacy calibration data parsers Dmitry Baryshkov
2022-12-29  3:00 ` [PATCH v5 12/20] thermal/drivers/tsens: Drop single-cell code for mdm9607 Dmitry Baryshkov
2022-12-29  3:00 ` [PATCH v5 13/20] thermal/drivers/tsens: Drop single-cell code for msm8939 Dmitry Baryshkov
2022-12-29 11:27   ` Konrad Dybcio
2022-12-29 12:27   ` Shawn Guo
2022-12-29  3:01 ` [PATCH v5 14/20] thermal/drivers/tsens: Drop single-cell code for msm8976/msm8956 Dmitry Baryshkov
2022-12-29 11:27   ` Konrad Dybcio
2022-12-29  3:01 ` [PATCH v5 15/20] arm64: dts: qcom: msm8956: use SoC-specific compat for tsens Dmitry Baryshkov
2022-12-29  3:01 ` [PATCH v5 16/20] arm64: dts: qcom: msm8916: specify per-sensor calibration cells Dmitry Baryshkov
2022-12-29  3:01 ` [PATCH v5 17/20] arm64: dts: qcom: msm8976: " Dmitry Baryshkov
2022-12-29  3:01 ` [PATCH v5 18/20] arm64: dts: qcom: qcs404: " Dmitry Baryshkov
2022-12-29  3:01 ` [PATCH v5 19/20] ARM: dts: qcom-msm8974: " Dmitry Baryshkov
2022-12-29  3:01 ` [PATCH v5 20/20] ARM: dts: qcom-apq8084: " Dmitry Baryshkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ecd974a7-6e46-b8c4-8c3d-70712a13400c@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=agross@kernel.org \
    --cc=amitk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=shawn.guo@linaro.org \
    --cc=thara.gopinath@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).