* Tomi Valkeinen [200609 16:27]:
> On 09/06/2020 19:10, Tony Lindgren wrote:
> > Yeah so it seems. Can we just diconnect the display outputs
> > in .prepare somewhere? Or is that the wrong place to do it?
>
> Hmm, yes, perhaps... If omapdrm uses .prepare to disable all the outputs.
> Then DSS sub
* Tomi Valkeinen [200609 15:38]:
> On 09/06/2020 18:12, Tony Lindgren wrote:
> > * Tomi Valkeinen [200609 10:33]:
> > > Use suspend_late and resume_early callbacks in DSS submodules to force
> > > runtime PM suspend and resume.
> > >
> > > We use suspend_late callback so that omapdrm's system su
* Tomi Valkeinen [200609 10:33]:
> Use suspend_late and resume_early callbacks in DSS submodules to force
> runtime PM suspend and resume.
>
> We use suspend_late callback so that omapdrm's system suspend callback
> is called first, as that will disable all the display outputs after
> which it's
On 09/06/2020 19:10, Tony Lindgren wrote:
* Tomi Valkeinen [200609 15:38]:
On 09/06/2020 18:12, Tony Lindgren wrote:
* Tomi Valkeinen [200609 10:33]:
Use suspend_late and resume_early callbacks in DSS submodules to force
runtime PM suspend and resume.
We use suspend_late callback so that om
On 09/06/2020 18:12, Tony Lindgren wrote:
* Tomi Valkeinen [200609 10:33]:
Use suspend_late and resume_early callbacks in DSS submodules to force
runtime PM suspend and resume.
We use suspend_late callback so that omapdrm's system suspend callback
is called first, as that will disable all the
Use suspend_late and resume_early callbacks in DSS submodules to force
runtime PM suspend and resume.
We use suspend_late callback 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.
Signed-off-by
