On Thu, Apr 28, 2016 at 7:55 PM, Gustavo Padovan <gustavo.padovan@xxxxxxxxxxxxxxx> wrote: > 2016-04-28 Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx>: > >> On Thu, Apr 28, 2016 at 07:43:16PM +0200, Daniel Vetter wrote: >> > On Thu, Apr 28, 2016 at 6:56 PM, Ville Syrjälä >> > <ville.syrjala@xxxxxxxxxxxxxxx> wrote: >> > >> - better for tracing, can identify the buffer/fence promptly >> > > >> > > Can fences be reused somehow while still attached to a plane, or ever? >> > > That might cause some oddness if you, say, leave a fence attached to one >> > > plane and then do a modeset on another crtc perhaps which needs to turn >> > > the first crtc off+on to reconfigure something. >> > >> > Fences auto-disappear of course and don't stick around when you >> > duplicate the drm_plane_state again. I still don't really get the real >> > concerns though ... >> >> Properties that magically change values shouldn't exist IMO. I guess if >> you could have write-only properties or something it migth be sensible? > > We can just not return FENCE_FD on get_props, that would make it > write-only. We do actually return a value for get_props, but it's -1 which for fds means "no fd". That's to make sure userspace can save&restore any prop without causing harm. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
