From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Zhang Rui" <rui.zhang@intel.com>,
"Lukasz Luba" <lukasz.luba@arm.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Alexandre Mergnat" <amergnat@baylibre.com>,
"Balsam CHIHI" <bchihi@baylibre.com>
Cc: kernel@collabora.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
"Hsin-Te Yuan" <yuanhsinte@chromium.org>,
"Chen-Yu Tsai" <wenst@chromium.org>,
"Bernhard Rosenkränzer" <bero@baylibre.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/5] thermal/drivers/mediatek/lvts: Disable monitor mode during suspend
Date: Tue, 26 Nov 2024 10:43:55 +0100 [thread overview]
Message-ID: <600f9d78-bdc8-4133-bb43-06d798bcd543@collabora.com> (raw)
In-Reply-To: <20241125-mt8192-lvts-filtered-suspend-fix-v1-1-42e3c0528c6c@collabora.com>
Il 25/11/24 22:20, Nícolas F. R. A. Prado ha scritto:
> When configured in filtered mode, the LVTS thermal controller will
> monitor the temperature from the sensors and trigger an interrupt once a
> thermal threshold is crossed.
>
> Currently this is true even during suspend and resume. The problem with
> that is that when enabling the internal clock of the LVTS controller in
> lvts_ctrl_set_enable() during resume, the temperature reading can glitch
> and appear much higher than the real one, resulting in a spurious
> interrupt getting generated.
>
> Disable the temperature monitoring and give some time for the signals to
> stabilize during suspend in order to prevent such spurious interrupts.
>
> Cc: stable@vger.kernel.org
> Reported-by: Hsin-Te Yuan <yuanhsinte@chromium.org>
> Closes: https://lore.kernel.org/all/20241108-lvts-v1-1-eee339c6ca20@chromium.org/
> Fixes: 8137bb90600d ("thermal/drivers/mediatek/lvts_thermal: Add suspend and resume")
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> ---
> drivers/thermal/mediatek/lvts_thermal.c | 36 +++++++++++++++++++++++++++++++--
> 1 file changed, 34 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/thermal/mediatek/lvts_thermal.c b/drivers/thermal/mediatek/lvts_thermal.c
> index 1997e91bb3be94a3059db619238aa5787edc7675..a92ff2325c40704adc537af6995b34f93c3b0650 100644
> --- a/drivers/thermal/mediatek/lvts_thermal.c
> +++ b/drivers/thermal/mediatek/lvts_thermal.c
> @@ -860,6 +860,32 @@ static int lvts_ctrl_init(struct device *dev, struct lvts_domain *lvts_td,
> return 0;
> }
>
> +static void lvts_ctrl_monitor_enable(struct device *dev, struct lvts_ctrl *lvts_ctrl, bool enable)
> +{
> + /*
> + * Bitmaps to enable each sensor on filtered mode in the MONCTL0
> + * register.
> + */
> + u32 sensor_filt_bitmap[] = { BIT(0), BIT(1), BIT(2), BIT(3) };
> + u32 sensor_map = 0;
> + int i;
> +
> + if (lvts_ctrl->mode != LVTS_MSR_FILTERED_MODE)
> + return;
> +
That's easier and shorter:
static void lvts_ctrl_monitor_enable( .... )
{
/* Bitmap to enable each sensor on filtered mode in the MONCTL0 register */
const u32 sensor_map = GENMASK(3, 0);
if (lvts_ctrl->mode != LVTS_MSR_FILTERED_MODE)
return;
/* Bits 0-3: Sensing points - Bit 9: Single point access flow */
if (enable)
writel(sensor_map | BIT(9), LVTS_MONCTL0(lvts_ctrl->base));
else
writel(BIT(9), LVTS_MONCTL0 ....
}
Cheers,
Angelo
> + if (enable) {
> + lvts_for_each_valid_sensor(i, lvts_ctrl)
> + sensor_map |= sensor_filt_bitmap[i];
> + }
> +
> + /*
> + * Bits:
> + * 9: Single point access flow
> + * 0-3: Enable sensing point 0-3
> + */
> + writel(sensor_map | BIT(9), LVTS_MONCTL0(lvts_ctrl->base));
> +}
> +
> /*
> * At this point the configuration register is the only place in the
> * driver where we write multiple values. Per hardware constraint,
> @@ -1381,8 +1407,11 @@ static int lvts_suspend(struct device *dev)
>
> lvts_td = dev_get_drvdata(dev);
>
> - for (i = 0; i < lvts_td->num_lvts_ctrl; i++)
> + for (i = 0; i < lvts_td->num_lvts_ctrl; i++) {
> + lvts_ctrl_monitor_enable(dev, &lvts_td->lvts_ctrl[i], false);
> + usleep_range(100, 200);
> lvts_ctrl_set_enable(&lvts_td->lvts_ctrl[i], false);
> + }
>
> clk_disable_unprepare(lvts_td->clk);
>
> @@ -1400,8 +1429,11 @@ static int lvts_resume(struct device *dev)
> if (ret)
> return ret;
>
> - for (i = 0; i < lvts_td->num_lvts_ctrl; i++)
> + for (i = 0; i < lvts_td->num_lvts_ctrl; i++) {
> lvts_ctrl_set_enable(&lvts_td->lvts_ctrl[i], true);
> + usleep_range(100, 200);
> + lvts_ctrl_monitor_enable(dev, &lvts_td->lvts_ctrl[i], true);
> + }
>
> return 0;
> }
>
next prev parent reply other threads:[~2024-11-26 9:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 21:20 [PATCH 0/5] thermal/drivers/mediatek/lvts: Fixes for suspend and IRQ storm, and cleanups Nícolas F. R. A. Prado
2024-11-25 21:20 ` [PATCH 1/5] thermal/drivers/mediatek/lvts: Disable monitor mode during suspend Nícolas F. R. A. Prado
2024-11-26 8:00 ` Hsin-Te Yuan
2024-11-26 13:37 ` Nícolas F. R. A. Prado
2024-11-27 7:27 ` Hsin-Te Yuan
2024-11-26 9:43 ` AngeloGioacchino Del Regno [this message]
2024-11-26 13:19 ` Nícolas F. R. A. Prado
2024-11-26 14:38 ` AngeloGioacchino Del Regno
2024-11-25 21:20 ` [PATCH 2/5] thermal/drivers/mediatek/lvts: Disable Stage 3 thermal threshold Nícolas F. R. A. Prado
2024-11-26 9:43 ` AngeloGioacchino Del Regno
2024-11-25 21:20 ` [PATCH 3/5] thermal/drivers/mediatek/lvts: Disable low offset IRQ for minimum threshold Nícolas F. R. A. Prado
2024-11-26 9:43 ` AngeloGioacchino Del Regno
2024-11-25 21:20 ` [PATCH 4/5] thermal/drivers/mediatek/lvts: Start sensor interrupts disabled Nícolas F. R. A. Prado
2024-11-26 9:43 ` AngeloGioacchino Del Regno
2024-11-25 21:20 ` [PATCH 5/5] thermal/drivers/mediatek/lvts: Only update IRQ enable for valid sensors Nícolas F. R. A. Prado
2024-11-26 9:43 ` AngeloGioacchino Del Regno
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=600f9d78-bdc8-4133-bb43-06d798bcd543@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=amergnat@baylibre.com \
--cc=bchihi@baylibre.com \
--cc=bero@baylibre.com \
--cc=daniel.lezcano@linaro.org \
--cc=kernel@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.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=stable@vger.kernel.org \
--cc=wenst@chromium.org \
--cc=yuanhsinte@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