From: "Michel Dänzer" <michel@daenzer.net>
To: Grigori Goronzy <greg@chown.ath.cx>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/radeon: unpin cursor BOs before suspend
Date: Fri, 3 Jul 2015 12:30:04 +0900 [thread overview]
Message-ID: <559601BC.2030703@daenzer.net> (raw)
In-Reply-To: <1435881253-4912-4-git-send-email-greg@chown.ath.cx>
[ Dropping stable@vger.kernel.org from Cc; the patch will be picked up
for stable after it lands in Linus' tree ]
On 03.07.2015 08:54, Grigori Goronzy wrote:
> Everything is evicted from VRAM before suspend, so we need to make
> sure all BOs are unpinned and re-pinned after resume. Fixes broken
> mouse cursor after resume introduced by commit b9729b17.
>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=100541
> Cc: stable@vger.kernel.org
> Signed-off-by: Grigori Goronzy <greg@chown.ath.cx>
> ---
> drivers/gpu/drm/radeon/radeon_device.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_device.c b/drivers/gpu/drm/radeon/radeon_device.c
> index 14deeae..dddd5df 100644
> --- a/drivers/gpu/drm/radeon/radeon_device.c
> +++ b/drivers/gpu/drm/radeon/radeon_device.c
> @@ -1578,6 +1578,20 @@ int radeon_suspend_kms(struct drm_device *dev, bool suspend, bool fbcon)
> drm_helper_connector_dpms(connector, DRM_MODE_DPMS_OFF);
> }
>
> + /* unpin cursors */
> + list_for_each_entry(crtc, &dev->mode_config.crtc_list, head) {
> + struct radeon_crtc *radeon_crtc = to_radeon_crtc(crtc);
> +
> + if (radeon_crtc->cursor_bo) {
> + struct radeon_bo *robj = gem_to_radeon_bo(radeon_crtc->cursor_bo);
> + r = radeon_bo_reserve(robj, false);
> + if (r == 0) {
> + radeon_bo_unpin(robj);
> + radeon_bo_unreserve(robj);
> + }
> + }
> + }
> +
> /* unpin the front buffers */
> list_for_each_entry(crtc, &dev->mode_config.crtc_list, head) {
> struct radeon_framebuffer *rfb = to_radeon_framebuffer(crtc->primary->fb);
>
This could be done in the same loop as the front buffers.
On resume, the cursor BO is currently pinned again by
radeon_cursor_reset -> radeon_set_cursor. However, radeon_cursor_reset
is also called when changing the video mode, in which case it causes the
cursor BO pin count to increase by 1 for each CRTC using it. Presumably,
the mouse cursor would end up broken again on suspend/resume after that
for you.
We need a solution which pins the BO again on resume but doesn't
increase the pin count during a mode change. I'm not sure right now what
the best way is to achieve that, I'll think about it more later.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
next prev parent reply other threads:[~2015-07-03 3:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 23:54 [PATCH 1/4] drm/radeon: use RCU query for GEM_BUSY syscall Grigori Goronzy
2015-07-02 23:54 ` [PATCH 2/4] drm/radeon: fix HDP flushing Grigori Goronzy
2015-07-02 23:54 ` [PATCH 3/4] drm/radeon: default to 2048 MB GART size on SI+ Grigori Goronzy
2015-07-02 23:54 ` [PATCH 4/4] drm/radeon: unpin cursor BOs before suspend Grigori Goronzy
2015-07-03 3:30 ` Michel Dänzer [this message]
2015-07-03 8:16 ` Grigori Goronzy
2015-07-03 10:01 ` Michel Dänzer
2015-07-03 9:45 ` [PATCH 1/4] drm/radeon: use RCU query for GEM_BUSY syscall Christian König
2015-07-06 21:14 ` Alex Deucher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=559601BC.2030703@daenzer.net \
--to=michel@daenzer.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@chown.ath.cx \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox