From: Matthias Kaehlcke <mka@chromium.org>
To: Ansuel Smith <ansuelsmth@gmail.com>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Amit Kucheria <amitk@kernel.org>,
Thara Gopinath <thara.gopinath@linaro.org>,
Zhang Rui <rui.zhang@intel.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] drivers: thermal: tsens: add timeout to get_tem_tsens_valid
Date: Tue, 7 Sep 2021 14:57:18 -0700 [thread overview]
Message-ID: <YTfgPmp5gzP6FyqR@google.com> (raw)
In-Reply-To: <20210907212543.20220-2-ansuelsmth@gmail.com>
On Tue, Sep 07, 2021 at 11:25:43PM +0200, Ansuel Smith wrote:
> The function can loop and lock the system if for whatever reason the bit
> for the target sensor is NEVER valid. This is the case if a sensor is
> disabled by the factory and the valid bit is never reported as actually
> valid. Add a timeout check and exit if a timeout occurs. As this is
> a very rare condition, handle the timeout only if the first read fails.
> While at it also rework the function to improve readability.
>
> Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
> ---
> drivers/thermal/qcom/tsens.c | 40 +++++++++++++++++++++++-------------
> 1 file changed, 26 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/thermal/qcom/tsens.c b/drivers/thermal/qcom/tsens.c
> index b1162e566a70..1ff244176beb 100644
> --- a/drivers/thermal/qcom/tsens.c
> +++ b/drivers/thermal/qcom/tsens.c
> @@ -599,26 +599,38 @@ int get_temp_tsens_valid(const struct tsens_sensor *s, int *temp)
> int hw_id = s->hw_id;
> u32 temp_idx = LAST_TEMP_0 + hw_id;
> u32 valid_idx = VALID_0 + hw_id;
> + unsigned long timeout;
> u32 valid;
> int ret;
>
> /* VER_0 doesn't have VALID bit */
> - if (tsens_version(priv) >= VER_0_1) {
> + if (tsens_version(priv) == VER_0)
> + goto get_temp;
> +
> + ret = regmap_field_read(priv->rf[valid_idx], &valid);
> + if (ret || valid)
> + goto check_valid;
> +
> + timeout = jiffies + msecs_to_jiffies(20);
> + do {
> + /* Valid bit is 0 for 6 AHB clock cycles.
> + * At 19.2MHz, 1 AHB clock is ~60ns.
> + * We should enter this loop very, very rarely.
> + */
> + ndelay(400);
> ret = regmap_field_read(priv->rf[valid_idx], &valid);
> - if (ret)
> - return ret;
> - while (!valid) {
> - /* Valid bit is 0 for 6 AHB clock cycles.
> - * At 19.2MHz, 1 AHB clock is ~60ns.
> - * We should enter this loop very, very rarely.
> - */
> - ndelay(400);
> - ret = regmap_field_read(priv->rf[valid_idx], &valid);
> - if (ret)
> - return ret;
> - }
> - }
> + if (ret || valid)
> + goto check_valid;
> + } while (time_before(jiffies, timeout));
> +
> + return -ETIMEDOUT;
> +
> +check_valid:
> + /* Check ret of valid bit read */
> + if (ret)
> + return ret;
>
> +get_temp:
> /* Valid bit is set, OK to read the temperature */
> *temp = tsens_hw_to_mC(s, temp_idx);
I still think that something like this would be clearer than the
multiple jumps to 'check_valid':
ret = regmap_field_read(priv->rf[valid_idx], &valid);
if (ret)
return ret;
timeout = jiffies + msecs_to_jiffies(20);
while (!valid) {
/* Valid bit is 0 for 6 AHB clock cycles.
* At 19.2MHz, 1 AHB clock is ~60ns.
* We should enter this loop very, very rarely.
*/
ndelay(400);
ret = regmap_field_read(priv->rf[valid_idx], &valid);
if (ret)
return ret;
if (time_after(jiffies, timeout))
return -ETIMEDOUT;
};
That said, I'm just a random dude, so my opinion isn't really important,
as long as the maintainers are happy with the change :)
next prev parent reply other threads:[~2021-09-07 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 21:25 [PATCH v2 1/2] drivers: thermal: tsens: fix wrong check for tzd in irq handlers Ansuel Smith
2021-09-07 21:25 ` [PATCH v2 2/2] drivers: thermal: tsens: add timeout to get_tem_tsens_valid Ansuel Smith
2021-09-07 21:57 ` Matthias Kaehlcke [this message]
2021-09-17 9:08 ` Daniel Lezcano
2021-09-17 11:06 ` Ansuel Smith
2021-09-17 9:08 ` [PATCH v2 1/2] drivers: thermal: tsens: fix wrong check for tzd in irq handlers Daniel Lezcano
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=YTfgPmp5gzP6FyqR@google.com \
--to=mka@chromium.org \
--cc=agross@kernel.org \
--cc=amitk@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=thara.gopinath@linaro.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;
as well as URLs for NNTP newsgroup(s).