On 11/17/15 12:28, Daniel Vetter wrote:
On Fri, Nov 13, 2015 at 05:53:13PM +0200, Jyri Sarha wrote:
Since first RFC version:
- Added "drm/atomic: Track drm_plane's active state"-patch

We would need something like this to get rid off OMAPDSS somewhat
messy runtime_resume code. How does this look, could this generic
solution be refined to be acceptable for mainline, or should we start
looking a local solution to omapdrm?

One more comment besides what I've written in the older thread: You're not
on latest drm-next, which has gained an active_only paramter to the plane
commit helper.

It might be best to discuss this topic on #dri-devel on freenode irc a
bit.


Thanks a lot for you comments!

I just rebased my stuff on top the the latest drm-next. I think I need digest your earlier comments about drm_atomic_add_affected_planes etc. a bit before I can take advantage of any interactive communication. I'll try to follow those instruction first and see where it leads me.

Thanks,
Jyri

Cheers, Daniel


Jyri Sarha (2):
   drm/atomic: Track drm_plane's active state
   drm/atomic: Disable planes on blanked CRTC and enable on unblank

  drivers/gpu/drm/drm_atomic_helper.c | 82 +++++++++++++++++++++++++++++--------
  drivers/gpu/drm/drm_plane_helper.c  | 10 +----
  include/drm/drm_atomic_helper.h     | 39 +-----------------
  include/drm/drm_crtc.h              |  2 +
  4 files changed, 70 insertions(+), 63 deletions(-)

--
1.9.1



--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to