From: Laura Nao <laura.nao@collabora.com>
To: wenst@chromium.org
Cc: andrew-ct.chen@mediatek.com,
angelogioacchino.delregno@collabora.com, arnd@arndb.de,
bchihi@baylibre.com, colin.i.king@gmail.com, conor+dt@kernel.org,
daniel.lezcano@linaro.org, devicetree@vger.kernel.org,
kernel@collabora.com, krzk+dt@kernel.org, lala.lin@mediatek.com,
laura.nao@collabora.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-pm@vger.kernel.org, lukasz.luba@arm.com,
matthias.bgg@gmail.com, nfraprado@collabora.com,
rafael@kernel.org, robh@kernel.org, rui.zhang@intel.com,
srini@kernel.org, u.kleine-koenig@baylibre.com
Subject: Re: [PATCH 5/9] thermal/drivers/mediatek/lvts: Add lvts_temp_to_raw variant for positive temp_factor
Date: Tue, 22 Jul 2025 12:26:53 +0200 [thread overview]
Message-ID: <20250722102653.30851-1-laura.nao@collabora.com> (raw)
In-Reply-To: <CAGXv+5F9NwJ7uGFPWZM-Dywbbk4f6aiYS5M4m6_VFETVGEwr9A@mail.gmail.com>
On 7/21/25 13:12, Chen-Yu Tsai wrote:
> On Mon, Jul 21, 2025 at 4:31 PM Laura Nao <laura.nao@collabora.com> wrote:
>>
>> The current lvts_temp_to_raw() implementation assumes a negative
>> temperature-to-raw slope (temp_factor), which holds for the SoCs
>> currently supported by the driver. However, this assumption breaks on
>> MT8196/MT6991, where the slope is positive.
>
> I don't think that's really a problem. The formula is:
>
> temp = (raw * factor) >> 14 + golden
>
> If we move the terms around we get
>
> ((temp - golden) << 14) / factor = raw
>
> Or
>
> raw = ((golden - temp) << 14) / -factor
>
>
> The calculations should work regardless of whether the factor is positive
> or negative, as long as the intermediate and final values are within
> the range of s64.
>
>> Add a variant of the function that inverts the calculation logic
>> accordingly. This ensures accurate raw value generation for temperature
>> thresholds,avoiding spurious thermal interrupts or unintended hardware
>> resets on MT8196/MT6991.
>>
>> Signed-off-by: Laura Nao <laura.nao@collabora.com>
>> ---
>> drivers/thermal/mediatek/lvts_thermal.c | 12 ++++++++++++
>> 1 file changed, 12 insertions(+)
>>
>> diff --git a/drivers/thermal/mediatek/lvts_thermal.c b/drivers/thermal/mediatek/lvts_thermal.c
>> index db83137c7537..3c34956e37c1 100644
>> --- a/drivers/thermal/mediatek/lvts_thermal.c
>> +++ b/drivers/thermal/mediatek/lvts_thermal.c
>> @@ -296,6 +296,18 @@ static u32 lvts_temp_to_raw(int temperature, int temp_factor)
>> return div_s64(raw_temp, -temp_factor);
>> }
>>
>> +static u32 lvts_temp_to_raw_v2(int temperature, int temp_factor)
>> +{
>> + u32 raw_temp;
>> +
>> + if (temp_factor == 0)
>> + return temperature;
>> +
>> + raw_temp = temperature - golden_temp_offset;
>> +
>> + return div_s64((s64)temp_factor << 14, raw_temp);
>> +}
>
> Here you have
>
> raw = (factor << 14) / (temp - golden)
>
> which, barring integer arithmetic limitations, is actually the
> multiplicative inverse of the original version.
>
> So I think the commit message is misleading. It's not negative or
> positive that matters, but that the hardware expects the
> multiplicative inverse in this version.
>
> (or the downstream code is just botched.)
>
Right - the positive temp_factor on MT8196 is one distinction from older
SoCs, and I initially assumed that was the reason a different conversion
formula was needed. That assumption was partly based on the original
lvts_temp_to_raw() implementation, which assigns
((s64)(golden_temp_offset - temperature) << 14) to a u32, losing the
sign when golden_temp_offset is negative. However, even correcting that
to preserve the sign doesn't make the function work on MT8196 as it
still requires using the multiplicative inverse form of the formula.
I'll reword the commit message to clarify this.
Thanks!
Laura
> ChenYu
>
>> +
>> static int lvts_get_temp(struct thermal_zone_device *tz, int *temp)
>> {
>> struct lvts_sensor *lvts_sensor = thermal_zone_device_priv(tz);
>> --
>> 2.39.5
>>
>>
next prev parent reply other threads:[~2025-07-22 10:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 8:14 [PATCH 0/9] Add thermal sensor driver support for Mediatek MT8196 Laura Nao
2025-07-21 8:14 ` [PATCH 1/9] dt-bindings: thermal: mediatek: Add LVTS thermal controller support for MT8196 Laura Nao
2025-07-22 7:20 ` Krzysztof Kozlowski
2025-07-21 8:14 ` [PATCH 2/9] thermal/drivers/mediatek/lvts: Make number of calibration offsets configurable Laura Nao
2025-07-21 8:14 ` [PATCH 3/9] thermal/drivers/mediatek/lvts: Guard against zero temp_factor in lvts_raw_to_temp Laura Nao
2025-07-21 10:08 ` Chen-Yu Tsai
2025-07-22 9:57 ` Laura Nao
2025-07-21 8:14 ` [PATCH 4/9] thermal: mediatek: lvts: Add platform ops to support alternative conversion logic Laura Nao
2025-07-21 8:14 ` [PATCH 5/9] thermal/drivers/mediatek/lvts: Add lvts_temp_to_raw variant for positive temp_factor Laura Nao
2025-07-21 11:12 ` Chen-Yu Tsai
2025-07-22 10:26 ` Laura Nao [this message]
2025-07-21 8:14 ` [PATCH 6/9] thermal/drivers/mediatek/lvts: Add support for ATP mode Laura Nao
2025-07-21 11:09 ` Chen-Yu Tsai
2025-07-21 8:14 ` [PATCH 7/9] thermal/drivers/mediatek/lvts: Support MSR offset for 16-bit calibration data Laura Nao
2025-07-21 8:14 ` [PATCH 8/9] thermal/drivers/mediatek/lvts_thermal: Add MT8196 support Laura Nao
2025-07-21 8:14 ` [PATCH 9/9] dt-bindings: nvmem: mediatek: efuse: Add support for MT8196 Laura Nao
2025-07-22 7:23 ` Krzysztof Kozlowski
2025-07-22 9:04 ` AngeloGioacchino Del Regno
2025-07-22 10:37 ` Laura Nao
2025-07-22 7:40 ` [PATCH 0/9] Add thermal sensor driver support for Mediatek MT8196 Chen-Yu Tsai
2025-07-22 9:50 ` 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=20250722102653.30851-1-laura.nao@collabora.com \
--to=laura.nao@collabora.com \
--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=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=lala.lin@mediatek.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
all inboxes | Powered by JetHome®