mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Felipe Balbi <balbi@ti.com>
Cc: <airlied@linux.ie>, <airlied@redhat.com>, <robdclark@gmail.com>,
	<bparrot@ti.com>, <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Darren Etheridge <detheridge@ti.com>
Subject: Re: [PATCH] drm/tilcdc: restore correct display mode and contents on pm resume
Date: Thu, 24 Apr 2014 12:58:17 -0500	[thread overview]
Message-ID: <20140424175817.GB4659@saruman.home> (raw)
In-Reply-To: <1393873736-26867-1-git-send-email-balbi@ti.com>

[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]

On Mon, Mar 03, 2014 at 01:08:56PM -0600, Felipe Balbi wrote:
> From: Darren Etheridge <detheridge@ti.com>
> 
> On resume the screen contents were not being restored properly.  Looking at
> other DRM drivers it seems a call to drm_helper_resume_force_mode() is needed
> in the resume handler to force restoration of the mode and framebuffer data.
> 
> Signed-off-by: Darren Etheridge <detheridge@ti.com>

ping

> ---
>  drivers/gpu/drm/tilcdc/tilcdc_drv.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/gpu/drm/tilcdc/tilcdc_drv.c b/drivers/gpu/drm/tilcdc/tilcdc_drv.c
> index 171a820..1a5ddfa 100644
> --- a/drivers/gpu/drm/tilcdc/tilcdc_drv.c
> +++ b/drivers/gpu/drm/tilcdc/tilcdc_drv.c
> @@ -563,6 +563,13 @@ static int tilcdc_pm_resume(struct device *dev)
>  		if (registers[i].save && (priv->rev >= registers[i].rev))
>  			tilcdc_write(ddev, registers[i].reg, priv->saved_register[n++]);
>  
> +	/*
> +	 * if this call isn't here, the display is blank on return from
> +	 * suspend.  With this call here the contents of the framebuffer
> +	 * during suspend are restored correctly.
> +	 */
> +	drm_helper_resume_force_mode(ddev);
> +
>  	drm_kms_helper_poll_enable(ddev);
>  
>  	return 0;
> -- 
> 1.9.0
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-04-24 17:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03 19:08 Felipe Balbi
2014-04-24 17:58 ` Felipe Balbi [this message]
2014-04-24 20:48 ` Rob Clark

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=20140424175817.GB4659@saruman.home \
    --to=balbi@ti.com \
    --cc=airlied@linux.ie \
    --cc=airlied@redhat.com \
    --cc=bparrot@ti.com \
    --cc=detheridge@ti.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robdclark@gmail.com \
    /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

all inboxes | Powered by JetHome®