On 03.10.2024 09:17, Boris Brezillon wrote:
> On Thu, 3 Oct 2024 01:25:37 +0100
> Adrián Larumbe wrote:
>
> > Commit f11b0417eec2 ("drm/panfrost: Add fdinfo support GPU load metrics")
> > retrieves the OPP for the maximum device clock frequency, but forgets to
> > keep the reference count balanc
On 03/10/2024 08:17, Boris Brezillon wrote:
> On Thu, 3 Oct 2024 01:25:37 +0100
> Adrián Larumbe wrote:
>
>> Commit f11b0417eec2 ("drm/panfrost: Add fdinfo support GPU load metrics")
>> retrieves the OPP for the maximum device clock frequency, but forgets to
>> keep the reference count balanced
On Thu, 3 Oct 2024 01:25:37 +0100
Adrián Larumbe wrote:
> Commit f11b0417eec2 ("drm/panfrost: Add fdinfo support GPU load metrics")
> retrieves the OPP for the maximum device clock frequency, but forgets to
> keep the reference count balanced by putting the returned OPP object. This
> eventually
On Thu, 3 Oct 2024 01:25:37 +0100
Adrián Larumbe wrote:
> Commit f11b0417eec2 ("drm/panfrost: Add fdinfo support GPU load metrics")
> retrieves the OPP for the maximum device clock frequency, but forgets to
> keep the reference count balanced by putting the returned OPP object. This
> eventually
Commit f11b0417eec2 ("drm/panfrost: Add fdinfo support GPU load metrics")
retrieves the OPP for the maximum device clock frequency, but forgets to
keep the reference count balanced by putting the returned OPP object. This
eventually leads to an OPP core warning when removing the device.
Fix it by
