Le jeu. 2 juil. 2020 à 14:31, Philippe CORNU a écrit :
>
>
>
> On 2/29/20 11:16 PM, Marek Vasut wrote:
> > Add missing pm_runtime_get_sync() into ltdc_crtc_atomic_enable() to
> > match pm_runtime_put_sync() in ltdc_crtc_atomic_disable(), otherwise
> > the LTDC might suspend via runtime PM,
On 7/2/20 12:07 PM, Philippe CORNU wrote:
Hi,
[...]
Thank for your patch. Pm_runtime_put_sync is also done into function
ltdc_crtc_mode_fixup.
To avoid several call of Pm_runtime_put_sync, it could be better to check
pm_runtime activity:
+ int ret;
On 2/29/20 11:16 PM, Marek Vasut wrote:
> Add missing pm_runtime_get_sync() into ltdc_crtc_atomic_enable() to
> match pm_runtime_put_sync() in ltdc_crtc_atomic_disable(), otherwise
> the LTDC might suspend via runtime PM, disable clock, and then fail
> to resume later on.
>
> The test which
;>
>>> -Original Message-----
>>> From: Marek Vasut
>>> Sent: samedi 29 février 2020 23:17
>>> To: dri-devel@lists.freedesktop.org
>>> Cc: Marek Vasut ; Yannick FERTRE ;
>>> Philippe CORNU ; Benjamin Gaignard
>>> ; Vincent ABRIOU ;
>>>
Fertre
>
>> Best regards
>>
>> Yannick Fertré
>>
>>
>> -Original Message-
>> From: Marek Vasut
>> Sent: samedi 29 février 2020 23:17
>> To: dri-devel@lists.freedesktop.org
>> Cc: Marek Vasut ; Yannick FERTRE ;
>> Philippe COR
gt; Sent: samedi 29 février 2020 23:17
> To: dri-devel@lists.freedesktop.org
> Cc: Marek Vasut ; Yannick FERTRE ;
> Philippe CORNU ; Benjamin Gaignard
> ; Vincent ABRIOU ;
> Maxime Coquelin ; Alexandre TORGUE
> ; linux-st...@st-md-mailman.stormreply.com;
> linux-ar
radead.org
Subject: [PATCH] drm/stm: repair runtime power management
Add missing pm_runtime_get_sync() into ltdc_crtc_atomic_enable() to match
pm_runtime_put_sync() in ltdc_crtc_atomic_disable(), otherwise the LTDC might
suspend via runtime PM, disable clock, and then fail to resume later on
Add missing pm_runtime_get_sync() into ltdc_crtc_atomic_enable() to
match pm_runtime_put_sync() in ltdc_crtc_atomic_disable(), otherwise
the LTDC might suspend via runtime PM, disable clock, and then fail
to resume later on.
The test which triggers it is roughly -- run qt5 application which
uses