[RFCv3 03/14] drm: Add primary plane helpers

2014-03-20 Thread Daniel Vetter
On Thu, Mar 20, 2014 at 12:01 AM, Matt Roper wrote: > On Wed, Mar 19, 2014 at 01:24:23PM +0100, Daniel Vetter wrote: >> On Tue, Mar 18, 2014 at 05:22:48PM -0700, Matt Roper wrote: >> > When we expose non-overlay planes to userspace, they will become >> > accessible via standard userspace plane

[RFCv3 03/14] drm: Add primary plane helpers

2014-03-19 Thread Daniel Vetter
On Wed, Mar 19, 2014 at 11:15:36AM -0700, Matt Roper wrote: > On Wed, Mar 19, 2014 at 12:28:43PM +0100, Daniel Vetter wrote: > > On Tue, Mar 18, 2014 at 05:22:48PM -0700, Matt Roper wrote: > ... > > > + > > > + /* > > > + * set_config() adjusts crtc->primary->fb; however the DRM setplane > > > +

[RFCv3 03/14] drm: Add primary plane helpers

2014-03-19 Thread Matt Roper
On Wed, Mar 19, 2014 at 01:24:23PM +0100, Daniel Vetter wrote: > On Tue, Mar 18, 2014 at 05:22:48PM -0700, Matt Roper wrote: > > When we expose non-overlay planes to userspace, they will become > > accessible via standard userspace plane API's. We should be able to > > handle the standard plane

[RFCv3 03/14] drm: Add primary plane helpers

2014-03-19 Thread Daniel Vetter
On Tue, Mar 18, 2014 at 05:22:48PM -0700, Matt Roper wrote: > When we expose non-overlay planes to userspace, they will become > accessible via standard userspace plane API's. We should be able to > handle the standard plane operations against primary planes in a generic > way via the page flip

[RFCv3 03/14] drm: Add primary plane helpers

2014-03-19 Thread Daniel Vetter
On Tue, Mar 18, 2014 at 05:22:48PM -0700, Matt Roper wrote: > When we expose non-overlay planes to userspace, they will become > accessible via standard userspace plane API's. We should be able to > handle the standard plane operations against primary planes in a generic > way via the page flip

[RFCv3 03/14] drm: Add primary plane helpers

2014-03-19 Thread Daniel Vetter
On Tue, Mar 18, 2014 at 05:22:48PM -0700, Matt Roper wrote: > When we expose non-overlay planes to userspace, they will become > accessible via standard userspace plane API's. We should be able to > handle the standard plane operations against primary planes in a generic > way via the page flip

[RFCv3 03/14] drm: Add primary plane helpers

2014-03-19 Thread Matt Roper
On Wed, Mar 19, 2014 at 12:28:43PM +0100, Daniel Vetter wrote: > On Tue, Mar 18, 2014 at 05:22:48PM -0700, Matt Roper wrote: ... > > + > > + /* > > +* set_config() adjusts crtc->primary->fb; however the DRM setplane > > +* code that called us expects to handle the framebuffer update and

[RFCv3 03/14] drm: Add primary plane helpers

2014-03-19 Thread Rob Clark
On Wed, Mar 19, 2014 at 7:28 AM, Daniel Vetter wrote: >> + /* >> + * set_config() adjusts crtc->primary->fb; however the DRM setplane >> + * code that called us expects to handle the framebuffer update and >> + * reference counting; save and restore the current fb before >> +

[RFCv3 03/14] drm: Add primary plane helpers

2014-03-18 Thread Matt Roper
When we expose non-overlay planes to userspace, they will become accessible via standard userspace plane API's. We should be able to handle the standard plane operations against primary planes in a generic way via the page flip handler and modeset handler. Drivers that can program primary planes