From: Laura Nao <laura.nao@collabora.com>
To: daniel.lezcano@linaro.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,
devicetree@vger.kernel.org, frank-w@public-files.de,
fshao@chromium.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,
wenst@chromium.org
Subject: Re: [PATCH v4 3/9] thermal/drivers/mediatek/lvts: Fail probe if temp_factor is zero
Date: Tue, 25 Nov 2025 12:08:48 +0100 [thread overview]
Message-ID: <20251125110848.23483-1-laura.nao@collabora.com> (raw)
In-Reply-To: <190003b6-2931-406a-a8f6-ec8909c65162@linaro.org>
On 11/24/25 18:56, Daniel Lezcano wrote:
> On 11/21/25 12:16, Laura Nao wrote:
>> temp_factor is used in lvts_temp_to_raw() and lvts_raw_to_temp(). If
>> platform data is incorrect and temp_factor is zero, it could cause a
>> division by zero. Fail the probe early to prevent a kernel crash.
>>
>> Signed-off-by: Laura Nao <laura.nao@collabora.com>
>> ---
>> drivers/thermal/mediatek/lvts_thermal.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/thermal/mediatek/lvts_thermal.c b/drivers/thermal/mediatek/lvts_thermal.c
>> index 1c54d0b75b1a..b49441d82ffd 100644
>> --- a/drivers/thermal/mediatek/lvts_thermal.c
>> +++ b/drivers/thermal/mediatek/lvts_thermal.c
>> @@ -1346,6 +1346,11 @@ static int lvts_probe(struct platform_device *pdev)
>> if (irq < 0)
>> return irq;
>> + if (!lvts_data->temp_factor)
>> + return dev_err_probe(
>> + dev, -EINVAL,
>> + "temp_factor should never be zero; check platform data.\n");
>> +
>
> From my POV, this is not really useful. The temp_factor is set for each version statically in the code. The scope is limited to the driver, IOW it is not a parameter other subsystems passes to the driver.
>
> If it is NULL, then shame on the submitter who did not test the driver before sending ;)
>
Ack - I'll drop the patch in the next revision.
Thanks,
Laura
next prev parent reply other threads:[~2025-11-25 11:09 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
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 [this message]
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=20251125110848.23483-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=frank-w@public-files.de \
--cc=fshao@chromium.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