[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220108174249.811872-1-robdclark@gmail.com>
Date: Sat, 8 Jan 2022 09:42:45 -0800
From: Rob Clark <robdclark@...il.com>
To: dri-devel@...ts.freedesktop.org
Cc: freedreno@...ts.freedesktop.org, linux-arm-msm@...r.kernel.org,
Rob Clark <robdclark@...omium.org>,
Abhinav Kumar <quic_abhinavk@...cinc.com>,
Akhil P Oommen <quic_akhilpo@...cinc.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Jonathan Marek <jonathan@...ek.ca>,
Jordan Crouse <jordan@...micpenguin.net>,
linux-kernel@...r.kernel.org (open list),
Vladimir Lypak <vladimir.lypak@...il.com>
Subject: [PATCH v2 0/2] drm/msm/gpu: System suspend fixes
From: Rob Clark <robdclark@...omium.org>
Because system suspend uses pm_runtime_force_suspend() we can't rely
runpm refcnt's to protect us if the GPU is active, etc. Fortunately
*usually* the GPU is idle when system suspend is triggered. But that
isn't quite good enough.
The first patch attempts to block for a modest amount of time until GPU
is idle (and failing that, returns -EBUSY). We could have taken a
slightly easier approach and just returned -EBUSY if GPU is not idle,
but that would cause system suspend to fail. And no one likes pulling
a hot laptop out of their backpack.
The second patch avoids getting devfreq callbacks after suspend, since
pm_runtime_force_suspend() breaks the pm_runtime_get_if_in_use() tricks
used to deal with devfreq callbacks while suspended.
Rob Clark (2):
drm/msm/gpu: Wait for idle before suspending
drm/msm/gpu: Cancel idle/boost work on suspend
drivers/gpu/drm/msm/adreno/adreno_device.c | 18 ++++++++++++++++++
drivers/gpu/drm/msm/msm_gpu.c | 3 +++
drivers/gpu/drm/msm/msm_gpu.h | 3 +++
drivers/gpu/drm/msm/msm_gpu_devfreq.c | 21 +++++++++++++++++++--
4 files changed, 43 insertions(+), 2 deletions(-)
--
2.33.1
Powered by blists - more mailing lists