From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Laura Nao <laura.nao@collabora.com>,
srini@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, rafael@kernel.org, rui.zhang@intel.com,
lukasz.luba@arm.com, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com
Cc: nfraprado@collabora.com, arnd@arndb.de, colin.i.king@gmail.com,
u.kleine-koenig@baylibre.com, andrew-ct.chen@mediatek.com,
lala.lin@mediatek.com, bchihi@baylibre.com,
frank-w@public-files.de, wenst@chromium.org, fshao@chromium.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v4 2/9] thermal/drivers/mediatek/lvts: Make number of calibration offsets configurable
Date: Mon, 24 Nov 2025 19:25:14 +0100 [thread overview]
Message-ID: <24a5bd31-a79f-4f18-a190-6a4d886a29b2@linaro.org> (raw)
In-Reply-To: <20251121-mt8196-lvts-v4-v4-2-357f955a3176@collabora.com>
On 11/21/25 12:16, Laura Nao wrote:
> MT8196/MT6991 use 2-byte eFuse calibration data, whereas other SoCs
> supported by the driver rely on 3 bytes. Make the number of calibration
> bytes per sensor configurable, enabling support for SoCs with varying
> calibration formats.
>
> Reviewed-by: Fei Shao <fshao@chromium.org>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Tested-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Tested-by: Frank Wunderlich <frank-w@public-files.de>
> Signed-off-by: Laura Nao <laura.nao@collabora.com>
> ---
> drivers/thermal/mediatek/lvts_thermal.c | 32 ++++++++++++++++++++++----------
> 1 file changed, 22 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/thermal/mediatek/lvts_thermal.c b/drivers/thermal/mediatek/lvts_thermal.c
> index ab55b20cda47..1c54d0b75b1a 100644
> --- a/drivers/thermal/mediatek/lvts_thermal.c
> +++ b/drivers/thermal/mediatek/lvts_thermal.c
> @@ -96,12 +96,14 @@
>
> #define LVTS_MINIMUM_THRESHOLD 20000
>
> +#define LVTS_MAX_CAL_OFFSETS 3
I suggest LVTS_NUM_CAL_OFFSETS then below,
> +
> static int golden_temp = LVTS_GOLDEN_TEMP_DEFAULT;
> static int golden_temp_offset;
>
> struct lvts_sensor_data {
> int dt_id;
> - u8 cal_offsets[3];
> + u8 cal_offsets[LVTS_MAX_CAL_OFFSETS];
> };
>
> struct lvts_ctrl_data {
> @@ -127,6 +129,7 @@ struct lvts_data {
> const struct lvts_ctrl_data *lvts_ctrl;
> const u32 *conn_cmd;
> const u32 *init_cmd;
> + int num_cal_offsets;
> int num_lvts_ctrl;
> int num_conn_cmd;
> int num_init_cmd;
> @@ -711,7 +714,7 @@ static int lvts_calibration_init(struct device *dev, struct lvts_ctrl *lvts_ctrl
> u8 *efuse_calibration,
> size_t calib_len)
> {
> - int i;
> + int i, j;
> u32 gt;
>
> /* A zero value for gt means that device has invalid efuse data */
> @@ -720,17 +723,18 @@ static int lvts_calibration_init(struct device *dev, struct lvts_ctrl *lvts_ctrl
> lvts_for_each_valid_sensor(i, lvts_ctrl_data) {
> const struct lvts_sensor_data *sensor =
> &lvts_ctrl_data->lvts_sensor[i];
> + u32 calib = 0;
>
> - if (sensor->cal_offsets[0] >= calib_len ||
> - sensor->cal_offsets[1] >= calib_len ||
> - sensor->cal_offsets[2] >= calib_len)
> - return -EINVAL;
> + for (j = 0; j < lvts_ctrl->lvts_data->num_cal_offsets; j++) {
> + u8 offset = sensor->cal_offsets[j];
> +
> + if (offset >= calib_len)
> + return -EINVAL;
> + calib |= efuse_calibration[offset] << (8 * j);
May be worth for a comment here, ideally a separate function to clarify
the code
> + }
>
> if (gt) {
> - lvts_ctrl->calibration[i] =
> - (efuse_calibration[sensor->cal_offsets[0]] << 0) +
> - (efuse_calibration[sensor->cal_offsets[1]] << 8) +
> - (efuse_calibration[sensor->cal_offsets[2]] << 16);
> + lvts_ctrl->calibration[i] = calib;
> } else if (lvts_ctrl->lvts_data->def_calibration) {
> lvts_ctrl->calibration[i] = lvts_ctrl->lvts_data->def_calibration;
> } else {
> @@ -1763,6 +1767,7 @@ static const struct lvts_data mt7988_lvts_ap_data = {
> .temp_factor = LVTS_COEFF_A_MT7988,
> .temp_offset = LVTS_COEFF_B_MT7988,
> .gt_calib_bit_offset = 24,
> + .num_cal_offsets = 3,
LVTS_NUM_CAL_OFFSETS
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2025-11-24 18:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 11:16 [PATCH v4 0/9] Add thermal sensor driver support for Mediatek MT8196 Laura Nao
2025-11-21 11:16 ` [PATCH v4 1/9] dt-bindings: thermal: mediatek: Add LVTS thermal controller support for MT8196 Laura Nao
2025-11-21 11:16 ` [PATCH v4 2/9] thermal/drivers/mediatek/lvts: Make number of calibration offsets configurable Laura Nao
2025-11-24 18:25 ` Daniel Lezcano [this message]
2025-11-25 11:06 ` Laura Nao
2025-11-21 11:16 ` [PATCH v4 3/9] thermal/drivers/mediatek/lvts: Fail probe if temp_factor is zero Laura Nao
2025-11-21 13:00 ` AngeloGioacchino Del Regno
2025-11-24 17:56 ` Daniel Lezcano
2025-11-25 11:08 ` Laura Nao
2025-11-21 11:16 ` [PATCH v4 4/9] thermal: mediatek: lvts: Add platform ops to support alternative conversion logic Laura Nao
2025-11-21 13:00 ` AngeloGioacchino Del Regno
2025-11-21 13:02 ` Frank Wunderlich
2025-11-25 11:10 ` Laura Nao
2025-11-21 11:16 ` [PATCH v4 5/9] thermal/drivers/mediatek/lvts: Add lvts_temp_to_raw variant Laura Nao
2025-11-21 11:16 ` [PATCH v4 6/9] thermal/drivers/mediatek/lvts: Add support for ATP mode Laura Nao
2025-11-21 11:16 ` [PATCH v4 7/9] thermal/drivers/mediatek/lvts: Support MSR offset for 16-bit calibration data Laura Nao
2025-11-21 11:16 ` [PATCH v4 8/9] thermal/drivers/mediatek/lvts_thermal: Add MT8196 support Laura Nao
2025-11-21 11:16 ` [PATCH v4 9/9] dt-bindings: nvmem: mediatek: efuse: Add support for MT8196 Laura Nao
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=24a5bd31-a79f-4f18-a190-6a4d886a29b2@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=andrew-ct.chen@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=bchihi@baylibre.com \
--cc=colin.i.king@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=fshao@chromium.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=lala.lin@mediatek.com \
--cc=laura.nao@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
--cc=srini@kernel.org \
--cc=u.kleine-koenig@baylibre.com \
--cc=wenst@chromium.org \
/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