lkml.org 
[lkml]   [2022]   [Nov]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH v9 02/11] drm/panfrost: Don't sync rpm suspension after mmu flushing
    Date
    Lockdep warns about potential circular locking dependency of devfreq
    with the fs_reclaim caused by immediate device suspension when mapping is
    released by shrinker. Fix it by doing the suspension asynchronously.

    Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
    ---
    drivers/gpu/drm/panfrost/panfrost_mmu.c | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    diff --git a/drivers/gpu/drm/panfrost/panfrost_mmu.c b/drivers/gpu/drm/panfrost/panfrost_mmu.c
    index e246d914e7f6..99a0975f6f03 100644
    --- a/drivers/gpu/drm/panfrost/panfrost_mmu.c
    +++ b/drivers/gpu/drm/panfrost/panfrost_mmu.c
    @@ -273,7 +273,7 @@ static void panfrost_mmu_flush_range(struct panfrost_device *pfdev,
    if (pm_runtime_active(pfdev->dev))
    mmu_hw_do_operation(pfdev, mmu, iova, size, AS_COMMAND_FLUSH_PT);

    - pm_runtime_put_sync_autosuspend(pfdev->dev);
    + pm_runtime_put_autosuspend(pfdev->dev);
    }

    static int mmu_map_sg(struct panfrost_device *pfdev, struct panfrost_mmu *mmu,
    --
    2.38.1
    \
     
     \ /
      Last update: 2022-11-23 04:01    [W:4.646 / U:0.064 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site