ping ...
On 2021/05/18 20:58, Robert Foss wrote:
On Tue, 18 May 2021 at 09:42, Johan Hovold wrote:
On Mon, May 17, 2021 at 11:27:38AM +0200, Robert Foss wrote:
Hey Yu,
On Mon, 17 May 2021 at 10:08, Yu Kuai wrote:
pm_runtime_get_sync will increment pm usage counter even it failed.
Forgett
On Tue, 18 May 2021 at 09:42, Johan Hovold wrote:
>
> On Mon, May 17, 2021 at 11:27:38AM +0200, Robert Foss wrote:
> > Hey Yu,
> >
> > On Mon, 17 May 2021 at 10:08, Yu Kuai wrote:
> > >
> > > pm_runtime_get_sync will increment pm usage counter even it failed.
> > > Forgetting to putting operation
On Mon, May 17, 2021 at 11:27:38AM +0200, Robert Foss wrote:
> Hey Yu,
>
> On Mon, 17 May 2021 at 10:08, Yu Kuai wrote:
> >
> > pm_runtime_get_sync will increment pm usage counter even it failed.
> > Forgetting to putting operation will result in reference leak here.
> > Fix it by replacing it wi
On 2021/05/17 17:27, Robert Foss wrote:
Hey Yu,
On Mon, 17 May 2021 at 10:08, Yu Kuai wrote:
pm_runtime_get_sync will increment pm usage counter even it failed.
Forgetting to putting operation will result in reference leak here.
Fix it by replacing it with pm_runtime_resume_and_get to keep us
Hey Yu,
On Mon, 17 May 2021 at 10:08, Yu Kuai wrote:
>
> pm_runtime_get_sync will increment pm usage counter even it failed.
> Forgetting to putting operation will result in reference leak here.
> Fix it by replacing it with pm_runtime_resume_and_get to keep usage
> counter balanced.
>
> Reported
pm_runtime_get_sync will increment pm usage counter even it failed.
Forgetting to putting operation will result in reference leak here.
Fix it by replacing it with pm_runtime_resume_and_get to keep usage
counter balanced.
Reported-by: Hulk Robot
Signed-off-by: Yu Kuai
---
drivers/gpu/drm/bridge
