Linux kernel development work - see feature branches https://git.zx2c4.com/linux-dev/atom/include/dt-bindings/msm?h=master 2017-11-23T04:10:39Z 2017-11-23T04:10:39Z Rob Clark robdclark@gmail.com 2017-11-16T14:05:57Z urn:sha1:98ecf1a308977505381b5c360b039a84cf67513c I think this snuck in when I applied the patch for f97decac5f4c (didn't apply cleanly, required some manual applying + git-add). It is unused and shouldn't be here. My bad. Fixes: f97decac5f4c "drm/msm: Support multiple ringbuffers" Signed-off-by: Rob Clark <robdclark@gmail.com> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Dave Airlie <airlied@redhat.com> 2017-10-28T15:01:36Z Jordan Crouse jcrouse@codeaurora.org 2017-10-20T17:06:57Z urn:sha1:f97decac5f4c2d862e5b848694e3ffb29fc8acdd Add the infrastructure to support the idea of multiple ringbuffers. Assign each ringbuffer an id and use that as an index for the various ring specific operations. The biggest delta is to support legacy fences. Each fence gets its own sequence number but the legacy functions expect to use a unique integer. To handle this we return a unique identifier for each submission but map it to a specific ring/sequence under the covers. Newer users use a dma_fence pointer anyway so they don't care about the actual sequence ID or ring. The actual mechanics for multiple ringbuffers are very target specific so this code just allows for the possibility but still only defines one ringbuffer for each target family. Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org> Signed-off-by: Rob Clark <robdclark@gmail.com>