All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/omap: force runtime PM suspend on system suspend
Date: Tue, 4 Aug 2020 11:22:59 +0300	[thread overview]
Message-ID: <5c74d5a1-3a5f-6eb9-17f4-147f4b2f890c@ti.com> (raw)
In-Reply-To: <20200717162854.GQ10990@atomide.com>

Hi,

On 17/07/2020 19:28, Tony Lindgren wrote:
> * Tomi Valkeinen <tomi.valkeinen@ti.com> [200618 09:53]:
>> Use SET_LATE_SYSTEM_SLEEP_PM_OPS in DSS submodules to force runtime PM
>> suspend and resume.
>>
>> We use suspend late version so that omapdrm's system suspend callback is
>> called first, as that will disable all the display outputs after which
>> it's safe to force DSS into suspend.
> 
> This would be great to have merged as a fix for v5.8 as it fixes a
> suspend and resume regression:
> 
> Fixes: cef766300353 ("drm/omap: Prepare DSS for probing without legacy platform data")
> Tested-by: Tony Lindgren <tonY@atomide.com>
> 

I have pushed this to drm-misc-fixes. I added

Cc: stable@vger.kernel.org # v5.7+

 Tomi

-- 
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2020-08-04  8:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18  9:51 [PATCH v2] drm/omap: force runtime PM suspend on system suspend Tomi Valkeinen
2020-06-18 13:16 ` Tony Lindgren
2020-06-18 14:01   ` Tomi Valkeinen
2020-06-18 14:41     ` Tony Lindgren
2020-06-18 16:24       ` Tony Lindgren
2020-06-18 16:24         ` Tony Lindgren
2020-07-17 16:28 ` Tony Lindgren
2020-08-04  8:22   ` Tomi Valkeinen [this message]

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=5c74d5a1-3a5f-6eb9-17f4-147f4b2f890c@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=grygorii.strashko@ti.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.