From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>, Tony Lindgren <tony@atomide.com>
Cc: edubezval@gmail.com, j-keerthy@ti.com, aford173@gmail.com,
linux-pm@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, andreas@kemnade.info
Subject: Re: [PATCH] thermal: ti-soc-thermal: Disable the CPU PM notifier for OMAP4430
Date: Thu, 12 Nov 2020 12:31:18 +0100 [thread overview]
Message-ID: <77940e9a-0e1a-f389-645a-071db5e1fcb5@linaro.org> (raw)
In-Reply-To: <b05f4bae-c285-828b-d5f1-fbf8613b4ca4@ti.com>
On 03/11/2020 07:42, Peter Ujfalusi wrote:
> Eduardo, Keerthy,
>
> On 29/10/2020 12.51, Tony Lindgren wrote:
>> * Peter Ujfalusi <peter.ujfalusi@ti.com> [201029 10:03]:
>>> Disabling the notifier fixes the random shutdowns on OMAP4430 (ES2.0 and ES2.1)
>>> but it does not cause any issues on OMAP4460 (PandaES) or OMAP3630 (BeagleXM).
>>> Tony's duovero with OMAP4430 ES2.3 did not ninja-shutdown, but he also have
>>> constant and steady stream of:
>>> thermal thermal_zone0: failed to read out thermal zone (-5)
>>
>> Works for me and I've verified duovero still keeps hitting core ret idle:
>
> Can you pick this one up for 5.10 to make omap4430-sdp to be usable (to
> not shut down randomly).
> The regression was introduced in 5.10-rc1.
>
>> Tested-by: Tony Lindgren <tony@atomide.com>
Applied as a fix for v5.10-rc
--
<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
prev parent reply other threads:[~2020-11-12 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 10:03 [PATCH] thermal: ti-soc-thermal: Disable the CPU PM notifier for OMAP4430 Peter Ujfalusi
2020-10-29 10:51 ` Tony Lindgren
2020-11-03 6:42 ` Peter Ujfalusi
2020-11-03 6:50 ` J, KEERTHY
2020-11-12 11:31 ` Daniel Lezcano [this message]
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=77940e9a-0e1a-f389-645a-071db5e1fcb5@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=aford173@gmail.com \
--cc=andreas@kemnade.info \
--cc=edubezval@gmail.com \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).