All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J, KEERTHY" <j-keerthy@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>, Tony Lindgren <tony@atomide.com>
Cc: <edubezval@gmail.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>,
	<daniel.lezcano@linaro.org>
Subject: Re: [PATCH] thermal: ti-soc-thermal: Disable the CPU PM notifier for OMAP4430
Date: Tue, 3 Nov 2020 12:20:32 +0530	[thread overview]
Message-ID: <2d6ecaaa-e760-759d-a23b-9556dd390758@ti.com> (raw)
In-Reply-To: <b05f4bae-c285-828b-d5f1-fbf8613b4ca4@ti.com>



On 11/3/2020 12:12 PM, 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.

Peter,

Thanks for the fix.

Acked-by: Keerthy <j-keerthy@ti.com>

Best Regards,
Keerthy

> 
>> Tested-by: Tony Lindgren <tony@atomide.com>
>>
>> Regards,
>>
>> Tony
>>
> 
> - Péter
> 
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
> 

WARNING: multiple messages have this Message-ID (diff)
From: "J, KEERTHY" <j-keerthy@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>, Tony Lindgren <tony@atomide.com>
Cc: linux-pm@vger.kernel.org, daniel.lezcano@linaro.org,
	linux-kernel@vger.kernel.org, edubezval@gmail.com,
	andreas@kemnade.info, linux-omap@vger.kernel.org,
	aford173@gmail.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] thermal: ti-soc-thermal: Disable the CPU PM notifier for OMAP4430
Date: Tue, 3 Nov 2020 12:20:32 +0530	[thread overview]
Message-ID: <2d6ecaaa-e760-759d-a23b-9556dd390758@ti.com> (raw)
In-Reply-To: <b05f4bae-c285-828b-d5f1-fbf8613b4ca4@ti.com>



On 11/3/2020 12:12 PM, 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.

Peter,

Thanks for the fix.

Acked-by: Keerthy <j-keerthy@ti.com>

Best Regards,
Keerthy

> 
>> Tested-by: Tony Lindgren <tony@atomide.com>
>>
>> Regards,
>>
>> Tony
>>
> 
> - Péter
> 
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-11-03  6:50 UTC|newest]

Thread overview: 10+ 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:03 ` Peter Ujfalusi
2020-10-29 10:51 ` Tony Lindgren
2020-10-29 10:51   ` Tony Lindgren
2020-11-03  6:42   ` Peter Ujfalusi
2020-11-03  6:42     ` Peter Ujfalusi
2020-11-03  6:50     ` J, KEERTHY [this message]
2020-11-03  6:50       ` J, KEERTHY
2020-11-12 11:31     ` Daniel Lezcano
2020-11-12 11:31       ` 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=2d6ecaaa-e760-759d-a23b-9556dd390758@ti.com \
    --to=j-keerthy@ti.com \
    --cc=aford173@gmail.com \
    --cc=andreas@kemnade.info \
    --cc=daniel.lezcano@linaro.org \
    --cc=edubezval@gmail.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 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.