From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM mailing list <linux-pm@vger.kernel.org>,
Lukasz Luba <Lukasz.Luba@arm.com>
Subject: Re: Trip points crossed not detected when no cooling device bound
Date: Thu, 27 Jun 2024 00:24:45 +0200 [thread overview]
Message-ID: <025ac119-e940-4dfb-aff6-9bd6121eb5c6@linaro.org> (raw)
In-Reply-To: <a1600a02-18e1-4e5c-bb64-6b1058a09fe5@linaro.org>
On 26/06/2024 23:21, Daniel Lezcano wrote:
[ ... ]
>> Oh, I see where the problem can be. If the zone is polling only, it
>> will not rearm the timer when the current zone temperature is invalid
>> after the above commit, so does the attached patch help?
>
> At this point, I went far when bisecting another problem and I ended up
> screwing my config file. So I had to generate a new one from the default
> config. Since then the issue is no longer happening which sounds very
> strange to me.
>
> I'm still investigating but if you have a suggestion coming in mind, it
> would be welcome because I'm failing to find out what is going on ... :/
I finally reproduced the issue. That happens when there is *no* cooling
device bound on *any* thermal zones.
Your patch seems to fix the problem but I'm not sure to understand the
conditions of the bug
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2024-06-26 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 6:50 Trip points crossed not detected when no cooling device bound Daniel Lezcano
2024-06-26 10:38 ` Rafael J. Wysocki
2024-06-26 21:21 ` Daniel Lezcano
2024-06-26 22:24 ` Daniel Lezcano [this message]
2024-06-27 9:54 ` Rafael J. Wysocki
2024-06-27 16:30 ` Daniel Lezcano
2024-06-27 18:23 ` Rafael J. Wysocki
2024-06-28 8:04 ` Daniel Lezcano
2024-06-28 10:49 ` Rafael J. Wysocki
2024-06-28 12:26 ` Rafael J. Wysocki
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=025ac119-e940-4dfb-aff6-9bd6121eb5c6@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=Lukasz.Luba@arm.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.