From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Priyansh Jain <priyansh.jain@oss.qualcomm.com>,
Amit Kucheria <amitk@kernel.org>,
Thara Gopinath <thara.gopinath@gmail.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>
Cc: linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, manaf.pallikunhi@oss.qualcomm.com
Subject: Re: [PATCH 1/2] thermal: qcom: tsens: atomic temperature read with hardware-guided retries
Date: Tue, 5 May 2026 09:43:31 +0200 [thread overview]
Message-ID: <0d95cd5b-01a8-44b6-bd4c-a7e5fa81e181@oss.qualcomm.com> (raw)
In-Reply-To: <e473e26b-f4bc-4044-a893-c0f255de6cb8@oss.qualcomm.com>
On 5/5/26 08:11, Priyansh Jain wrote:
[ ... ]
>>> + .valid_bit = BIT(14),
>>> + .last_temp_mask = 0x3FF,
>>
>> This is GENMASK(9, 0)
>>
>>> + .last_temp_resolution = 9,
>>
>> Please comply with the SSOT, in the init function compute the mask with:
>>
>> ->last_temp_mask = GENMASK(9, 0);
>>
>> and remove the initialization here
> Thanks for pointing this out — yes, this approach looks better.
> If I understand correctly, you’re suggesting that the mask should simply
> be defined in the init function as follows:
> priv->feat->last_temp_mask = GENMASK(priv->feat->last_temp_resolution, 0);
> ?
Yes, that's correct
>>> };
>>> static struct tsens_features ipq8074_feat = {
>>> @@ -125,8 +128,7 @@ static const struct reg_field
>>> tsens_v2_regfields[MAX_REGFIELDS] = {
>>> [WDOG_BARK_COUNT] = REG_FIELD(TM_WDOG_LOG_OFF, 0,
>>> 7),
>>> /* Sn_STATUS */
>>> - REG_FIELD_FOR_EACH_SENSOR16(LAST_TEMP, TM_Sn_STATUS_OFF,
>>> 0, 11),
>>> - REG_FIELD_FOR_EACH_SENSOR16(VALID, TM_Sn_STATUS_OFF,
>>> 21, 21),
>>> + REG_FIELD_FOR_EACH_SENSOR16(LAST_TEMP, TM_Sn_STATUS_OFF,
>>> 0, 21),
>>> /* xxx_STATUS bits: 1 == threshold violated */
>>> REG_FIELD_FOR_EACH_SENSOR16(MIN_STATUS, TM_Sn_STATUS_OFF,
>>> 16, 16),
>>> REG_FIELD_FOR_EACH_SENSOR16(LOWER_STATUS, TM_Sn_STATUS_OFF,
>>> 17, 17),
>>> diff --git a/drivers/thermal/qcom/tsens.c b/drivers/thermal/qcom/tsens.c
>>> index a2422ebee816..15392a17ef41 100644
>>> --- a/drivers/thermal/qcom/tsens.c
>>> +++ b/drivers/thermal/qcom/tsens.c
>>> @@ -315,10 +315,66 @@ static inline int code_to_degc(u32 adc_code,
>>> const struct tsens_sensor *s)
>>> return degc;
>>> }
>>> +static inline enum tsens_ver tsens_version(struct tsens_priv *priv)
>>> +{
>>> + return priv->feat->ver_major;
>>> +}
>>
>> I agree putting accessor functions is a good practice but here as it
>> results in duplicating the function, the benefit is discutable.
>>
> I did not introduce this new function; it was already present and I only
> moved it from the bottom of the file to the top since it was being used
> in tsens_read_temp().
> However, this change is no longer required as I am removing the use of
> tsens_version() in tsens_read_temp(). As discussed earlier with Konrad,
> it makes more sense to check for valid‑bit support rather than relying
> on the TSENS version check in tsens_read_temp().
Ah yes, makes sense
[ ... ]
>>> + }
>>> +
>>> + if (temp_val[0] == temp_val[1])
>>> + *temp = temp_val[1];
>>> + else if (temp_val[1] == temp_val[2])
>>> + *temp = temp_val[2];
>>> + else
>>> + return -EAGAIN;
>>
>> We have a, b and c.
>>
>> if a == b, then return b
>> else b == c, then return c
>> else return -EAGAIN
>>
>> It is like we have two consecutives successful read. IMO that could be
>> simplified to:
>>
>> int prev = INTMAX;
>>
>> /*
>> * An explanation ...
>> */
>>
>> for (i = 0; i < max_retry; i++) {
>>
>> int value, valid;
>>
>> ret = regmap_field_read(priv->rf[field], &status);
>> if (ret)
>> return ret;
>>
>> value = FIELD_GET(priv->feat->last_temp_mask, status);
>>
>> valid = FIELD_GET(priv->feat->valid_bit, status)
>> if (valid)
>> return value;
>>
>> if (value == prev)
>> return value;
>>
>> prev = value;
>> }
>>
>> return -EAGAIN;
>>
>> (Not tested)
> This approach has some misalignment with the HW recommendations.
> As per the HW guidelines, 3 back‑to‑back reads must be performed until a
> valid read is observed.
> b or c should be returned only if none of the three reads(a,b,c) report
> the valid bit not set.
Right I missed the point the HW recommendations is to read 3 times in
any case. Maybe replace if (value == prev) continue; ?
next prev parent reply other threads:[~2026-05-05 7:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 5:44 [PATCH 0/2] thermal: qcom: tsens: fix temperature handling Priyansh Jain
2026-04-30 5:44 ` [PATCH 1/2] thermal: qcom: tsens: atomic temperature read with hardware-guided retries Priyansh Jain
2026-04-30 15:51 ` Konrad Dybcio
[not found] ` <10c07347-a0df-42d3-b216-5150817b9ed2@oss.qualcomm.com>
2026-05-04 9:59 ` Konrad Dybcio
2026-05-04 10:34 ` Priyansh Jain
2026-04-30 16:00 ` Konrad Dybcio
[not found] ` <fc027ab4-695b-4622-b30e-8a79ce6e1781@oss.qualcomm.com>
2026-05-04 9:46 ` Konrad Dybcio
2026-05-04 17:29 ` Daniel Lezcano
2026-05-05 6:11 ` Priyansh Jain
2026-05-05 7:43 ` Daniel Lezcano [this message]
2026-05-05 8:48 ` Priyansh Jain
2026-05-05 9:35 ` Daniel Lezcano
2026-05-05 9:39 ` Priyansh Jain
2026-04-30 5:44 ` [PATCH 2/2] thermal: qcom: tsens: widen temperature limits to match hardware range Priyansh Jain
2026-04-30 16:01 ` Konrad Dybcio
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=0d95cd5b-01a8-44b6-bd4c-a7e5fa81e181@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=manaf.pallikunhi@oss.qualcomm.com \
--cc=priyansh.jain@oss.qualcomm.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--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