search for: sync_timeline

Modify sync_fence_create to accept an array of 'struct fence' objects. This will allow drm drivers to create sync_fence objects and pass sync fd's between user space with minimal modifications, without ever creating sync_timeline or sync_pt objects, and without implementing the sync_timeline_ops interface. Modify the sync driver debug code to not assume that every 'struct fence' (that is associated with a 'struct sync_fence') is embedded within a 'struct sync_pt'. Signed-off-by: Lauri Peltonen <...

...o Nouveau. It's not a lot of code, because I only use a relatively small subset of the android sync driver functionality. Thanks to Maarten's rewrite, all I need to do is to allow creating a sync_fence from a drm fence in order to pass it to user space. I don't need to use sync_pt or sync_timeline, or fill in sync_timeline_ops. I can see why the upstream has been reluctant to de-stage the android sync driver in its current form, since (even though it now builds on struct fence) it still duplicates some of the drm fence concepts. I'd like to think that my patches only use the parts of t...

...of code, because I only use a relatively > > small subset of the android sync driver functionality. Thanks to Maarten's > > rewrite, all I need to do is to allow creating a sync_fence from a drm fence in > > order to pass it to user space. I don't need to use sync_pt or sync_timeline, > > or fill in sync_timeline_ops. > > > > I can see why the upstream has been reluctant to de-stage the android sync > > driver in its current form, since (even though it now builds on struct fence) > > it still duplicates some of the drm fence concepts. I'd lik...

...#39;s not a lot of code, because I only use a relatively > small subset of the android sync driver functionality. Thanks to Maarten's > rewrite, all I need to do is to allow creating a sync_fence from a drm fence in > order to pass it to user space. I don't need to use sync_pt or sync_timeline, > or fill in sync_timeline_ops. > > I can see why the upstream has been reluctant to de-stage the android sync > driver in its current form, since (even though it now builds on struct fence) > it still duplicates some of the drm fence concepts. I'd like to think that my > p...

...because I only use a relatively >>> small subset of the android sync driver functionality. Thanks to Maarten's >>> rewrite, all I need to do is to allow creating a sync_fence from a drm fence in >>> order to pass it to user space. I don't need to use sync_pt or sync_timeline, >>> or fill in sync_timeline_ops. >>> >>> I can see why the upstream has been reluctant to de-stage the android sync >>> driver in its current form, since (even though it now builds on struct fence) >>> it still duplicates some of the drm fence concepts...