[PATCH 1/6] [media] vb2: only check ret if we assigned it

From: Gustavo Padovan Move the ret check to the right level under if (pb). It is not used by the code before that point if pb is NULL. Signed-off-by: Gustavo Padovan --- drivers/media/v4l2-core/videobuf2-core.c | 14 -- 1 file changed, 8 insertions(+), 6 deletions(-) diff --git

Re: [PATCH] drm/vc4: simplify exit path of a failed allocation of dsi_connector

504 ("Logicall Dead Code") > > Signed-off-by: Colin Ian King <colin.k...@canonical.com> > --- > drivers/gpu/drm/vc4/vc4_dsi.c | 16 ---- > 1 file changed, 4 insertions(+), 12 deletions(-) Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.com> Gustavo

Re: [PATCH] drm/vc4: simplify exit path of a failed allocation of dsi_connector

: Colin Ian King > --- > drivers/gpu/drm/vc4/vc4_dsi.c | 16 > 1 file changed, 4 insertions(+), 12 deletions(-) Reviewed-by: Gustavo Padovan Gustavo

Re: [PATCH -next] drm: mxsfb: fix error return code in mxsfb_load()

>fbdev)) { > + ret = PTR_ERR(mxsfb->fbdev); > mxsfb->fbdev = NULL; > dev_err(drm->dev, "Failed to init FB CMA area\n"); > goto err_cma; Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.com> Gustavo

Re: [PATCH -next] drm: mxsfb: fix error return code in mxsfb_load()

b->fbdev = NULL; > dev_err(drm->dev, "Failed to init FB CMA area\n"); > goto err_cma; Reviewed-by: Gustavo Padovan Gustavo

Re: [PATCH -next] drm/atomic: make release_crtc_commit() static

tatic? > > Signed-off-by: Wei Yongjun <weiyongj...@huawei.com> > --- > drivers/gpu/drm/drm_atomic_helper.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.com> Gustavo

Re: [PATCH -next] drm/atomic: make release_crtc_commit() static

> --- > drivers/gpu/drm/drm_atomic_helper.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Reviewed-by: Gustavo Padovan Gustavo

Re: [PATCH -next] drm/hisilicon/hibmc: Fix wrong pointer passed to PTR_ERR()

support for frame buffer") > Signed-off-by: Wei Yongjun <weiyongj...@huawei.com> Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.com> Gustavo

Re: [PATCH -next] drm/hisilicon/hibmc: Fix wrong pointer passed to PTR_ERR()

Hi Wei, 2017-01-12 Wei Yongjun : > From: Wei Yongjun > > PTR_ERR should access the value just tested by IS_ERR, otherwise > the wrong error code will be returned. > > Fixes: d1667b86795a ("drm/hisilicon/hibmc: Add support for frame buffer") > Signed-off-by: Wei

Re: [PATCH] drm: Clean up the 1366x768 fixup codes

Hi Takashi, 2017-01-16 Takashi Iwai : > This is just a cleanup, no functional change. > > The fixup code for 1366x768 in drm_mode_create_from_cmdline_mode() is > basically a copy of the existing code in drm_edid.c. Make the latter > code public so that it can be called from the

Re: [PATCH] drm: Clean up the 1366x768 fixup codes

Hi Takashi, 2017-01-16 Takashi Iwai : > This is just a cleanup, no functional change. > > The fixup code for 1366x768 in drm_mode_create_from_cmdline_mode() is > basically a copy of the existing code in drm_edid.c. Make the latter > code public so that it can be called from the former

[PATCH] selftest: sync: improve assert() failure message

From: Gustavo Padovan <gustavo.pado...@collabora.com> Print "ERROR" on all messages instead of using the not well defined terms like "BAD". Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.com> --- tools/testing/selftests/sync/synctest.h | 2 +- 1

[PATCH] selftest: sync: improve assert() failure message

From: Gustavo Padovan Print "ERROR" on all messages instead of using the not well defined terms like "BAD". Signed-off-by: Gustavo Padovan --- tools/testing/selftests/sync/synctest.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/selftest

Re: [RFC 1/5] drm/virtio: add virtio_gpu_alloc_fence()

2016-12-13 Gerd Hoffmann : > Hi, > > > +struct virtio_gpu_fence *virtio_gpu_fence_alloc(struct virtio_gpu_device > > *vgdev) > > +{ > > + struct virtio_gpu_fence_driver *drv = >fence_drv; > > + struct virtio_gpu_fence *fence; > > + unsigned long irq_flags; > > + > > +

Re: [RFC 1/5] drm/virtio: add virtio_gpu_alloc_fence()

2016-12-13 Gerd Hoffmann : > Hi, > > > +struct virtio_gpu_fence *virtio_gpu_fence_alloc(struct virtio_gpu_device > > *vgdev) > > +{ > > + struct virtio_gpu_fence_driver *drv = >fence_drv; > > + struct virtio_gpu_fence *fence; > > + unsigned long irq_flags; > > + > > + fence =

Re: [PATCH] drm/msm: return fence_fd = -1 if gem_submit fails

2016-12-12 Chris Wilson <ch...@chris-wilson.co.uk>: > On Mon, Dec 12, 2016 at 05:41:08PM -0200, Gustavo Padovan wrote: > > From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> > > > > Previously we were returning garbage here, fix it by setting it to -1 &g

Re: [PATCH] drm/msm: return fence_fd = -1 if gem_submit fails

2016-12-12 Chris Wilson : > On Mon, Dec 12, 2016 at 05:41:08PM -0200, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > Previously we were returning garbage here, fix it by setting it to -1 > > before the first possible point of failure. > > The convent

[RFC 2/5] drm/virtio: add uapi for in and out explicit fences

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Add a new field called fence_fd that will be used by userspace to send in-fences to the kernel and receive out-fences created by the kernel. This uapi enables virtio to take advantage of explicit synchronization of dma-bufs. There a

[RFC 2/5] drm/virtio: add uapi for in and out explicit fences

From: Gustavo Padovan Add a new field called fence_fd that will be used by userspace to send in-fences to the kernel and receive out-fences created by the kernel. This uapi enables virtio to take advantage of explicit synchronization of dma-bufs. There are two new flags

[RFC 4/5] drm/virtio: add out-fences support for explicit synchronization

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> On the out-fence side we get fence returned by the submitted draw call and attach it to a sync_file and send the sync_file fd to userspace. On error -1 is returned to userspace. Signed-off-by: Gustavo Padovan <gus

[RFC 1/5] drm/virtio: add virtio_gpu_alloc_fence()

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Refactor fence creation to remove the potential allocation failure from the cmd_submit and atomic_commit paths. Now the fence should be allocated first and just after we should proceed with the rest of the execution. Signed-off-by: G

[RFC 5/5] drm/virtio: bump driver version after explicit synchronization addition

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> To reflect the (backward compatible) changes in the uabi we are bumping the driver's version. Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk> --- drivers/gpu/drm/virtio/virtgpu_drv.h | 4 ++-- 1 file changed,

[RFC 3/5] drm/virtio: add in-fences support for explicit synchronization

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> When the execbuf call receives an in-fence it will get the dma_fence related to that fence fd and wait on it before submitting the draw call. Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk> --- drivers/gp

[RFC 4/5] drm/virtio: add out-fences support for explicit synchronization

From: Gustavo Padovan On the out-fence side we get fence returned by the submitted draw call and attach it to a sync_file and send the sync_file fd to userspace. On error -1 is returned to userspace. Signed-off-by: Gustavo Padovan --- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 51

[RFC 1/5] drm/virtio: add virtio_gpu_alloc_fence()

From: Gustavo Padovan Refactor fence creation to remove the potential allocation failure from the cmd_submit and atomic_commit paths. Now the fence should be allocated first and just after we should proceed with the rest of the execution. Signed-off-by: Gustavo Padovan --- drivers/gpu/drm

[RFC 5/5] drm/virtio: bump driver version after explicit synchronization addition

From: Gustavo Padovan To reflect the (backward compatible) changes in the uabi we are bumping the driver's version. Signed-off-by: Gustavo Padovan --- drivers/gpu/drm/virtio/virtgpu_drv.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/virtio

[RFC 3/5] drm/virtio: add in-fences support for explicit synchronization

From: Gustavo Padovan When the execbuf call receives an in-fence it will get the dma_fence related to that fence fd and wait on it before submitting the draw call. Signed-off-by: Gustavo Padovan --- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 41 ++ 1 file changed

[PATCH] drm/msm: return fence_fd = -1 if gem_submit fails

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Previously we were returning garbage here, fix it by setting it to -1 before the first possible point of failure. Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk> --- drivers/gpu/drm/msm/msm_gem_submit.c | 5 +

[PATCH] drm/msm: return fence_fd = -1 if gem_submit fails

From: Gustavo Padovan Previously we were returning garbage here, fix it by setting it to -1 before the first possible point of failure. Signed-off-by: Gustavo Padovan --- drivers/gpu/drm/msm/msm_gem_submit.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/gpu

[PATCH] drm/virtio: call drm_plane_cleanup() at destroy phase

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> virtio was missing this call to clean up core plane usage. Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk> --- drivers/gpu/drm/virtio/virtgpu_plane.c | 1 + 1 file changed, 1 insertion(+) diff --git a/dri

[PATCH] drm/virtio: call drm_plane_cleanup() at destroy phase

From: Gustavo Padovan virtio was missing this call to clean up core plane usage. Signed-off-by: Gustavo Padovan --- drivers/gpu/drm/virtio/virtgpu_plane.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/virtio/virtgpu_plane.c b/drivers/gpu/drm/virtio/virtgpu_plane.c index

[PATCH] staging/android: remove Sync Framework tasks from TODO

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> The destaging work is now fully complete. Cc: Arve Hjønnevåg <a...@android.com> Cc: Riley Andrews <riandr...@android.com> Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk> --- drivers/staging/andr

[PATCH] staging/android: remove Sync Framework tasks from TODO

From: Gustavo Padovan The destaging work is now fully complete. Cc: Arve Hjønnevåg Cc: Riley Andrews Signed-off-by: Gustavo Padovan --- drivers/staging/android/TODO | 8 1 file changed, 8 deletions(-) diff --git a/drivers/staging/android/TODO b/drivers/staging/android/TODO index

[PATCH v13] drm/fence: add out-fences support

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The syn

[PATCH v13] drm/fence: add out-fences support

From: Gustavo Padovan Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The sync_file and fd are allocated/created before

[PATCH v12 3/3] drm/fence: add out-fences support

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The syn

[PATCH v12 3/3] drm/fence: add out-fences support

From: Gustavo Padovan Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The sync_file and fd are allocated/created before

[PATCH v12 2/3] drm/fence: add fence timeline to drm_crtc

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the

[PATCH v12 2/3] drm/fence: add fence timeline to drm_crtc

From: Gustavo Padovan Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the fence lock, that we pass in fence_init

[PATCH v12 1/3] drm/fence: add in-fences support

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> There is now a new property called IN_FENCE_FD attached to every plane state that receives sync_file fds from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_array subclass or just a

[PATCH v12 0/3] drm: add explicit fencing

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Hi, Yet another iteration, v12 now after working on the changes proposed by Chris Wilson. Robert Foss managed to port Android's drm_hwcomposer to the new HWC2 API and added support to fences. Current patches can be seen here:

[PATCH v12 1/3] drm/fence: add in-fences support

From: Gustavo Padovan There is now a new property called IN_FENCE_FD attached to every plane state that receives sync_file fds from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_array subclass or just a normal fence) and then used by DRM

[PATCH v12 0/3] drm: add explicit fencing

From: Gustavo Padovan Hi, Yet another iteration, v12 now after working on the changes proposed by Chris Wilson. Robert Foss managed to port Android's drm_hwcomposer to the new HWC2 API and added support to fences. Current patches can be seen here: https://git.collabora.com/cgit/user

Re: [PATCH v11 2/3] drm/fence: add fence timeline to drm_crtc

2016-11-15 Chris Wilson <ch...@chris-wilson.co.uk>: > On Tue, Nov 15, 2016 at 10:57:35AM +0900, Gustavo Padovan wrote: > > diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h > > index 11780a9..0870de1 100644 > > --- a/include/drm/drm_crtc.h > > +++ b/in

Re: [PATCH v11 2/3] drm/fence: add fence timeline to drm_crtc

2016-11-15 Chris Wilson : > On Tue, Nov 15, 2016 at 10:57:35AM +0900, Gustavo Padovan wrote: > > diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h > > index 11780a9..0870de1 100644 > > --- a/include/drm/drm_crtc.h > > +++ b/include/drm/drm_crtc.h > >

[PATCH v11 2/3] drm/fence: add fence timeline to drm_crtc

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the

[PATCH v11 2/3] drm/fence: add fence timeline to drm_crtc

From: Gustavo Padovan Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the fence lock, that we pass in fence_init

[PATCH v11 0/3] drm: add explicit fencing

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Hi, Hopefully the last version of the patches with the two comments from Brian in the previous version addressed. Robert Foss managed to port Android's drm_hwcomposer to the new HWC2 API and added support to fences. Current patch

[PATCH v11 0/3] drm: add explicit fencing

From: Gustavo Padovan Hi, Hopefully the last version of the patches with the two comments from Brian in the previous version addressed. Robert Foss managed to port Android's drm_hwcomposer to the new HWC2 API and added support to fences. Current patches can be seen here: https

[PATCH v11 3/3] drm/fence: add out-fences support

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The syn

[PATCH v11 1/3] drm/fence: add in-fences support

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> There is now a new property called IN_FENCE_FD attached to every plane state that receives sync_file fds from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_array subclass or just a

[PATCH v11 3/3] drm/fence: add out-fences support

From: Gustavo Padovan Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The sync_file and fd are allocated/created before

[PATCH v11 1/3] drm/fence: add in-fences support

From: Gustavo Padovan There is now a new property called IN_FENCE_FD attached to every plane state that receives sync_file fds from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_array subclass or just a normal fence) and then used by DRM

[PATCH v10 1/3] drm/fence: add in-fences support

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> There is now a new property called IN_FENCE_FD attached to every plane state that receives sync_file fds from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_array subclass or just a

[PATCH v10 2/3] drm/fence: add fence timeline to drm_crtc

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the

[PATCH v10 3/3] drm/fence: add out-fences support

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The syn

[PATCH v10 0/3] drm: add explicit fencing

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Hi, Another iteration after comments on v8 and v9. Please refer to the cover letter[1] in a previous version to check for more details. The only changes in this series are in patch 3/3, see commit message for details. Robert Foss m

[PATCH v10 1/3] drm/fence: add in-fences support

From: Gustavo Padovan There is now a new property called IN_FENCE_FD attached to every plane state that receives sync_file fds from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_array subclass or just a normal fence) and then used by DRM

[PATCH v10 2/3] drm/fence: add fence timeline to drm_crtc

From: Gustavo Padovan Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the fence lock, that we pass in fence_init

[PATCH v10 3/3] drm/fence: add out-fences support

From: Gustavo Padovan Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The sync_file and fd are allocated/created before

[PATCH v10 0/3] drm: add explicit fencing

From: Gustavo Padovan Hi, Another iteration after comments on v8 and v9. Please refer to the cover letter[1] in a previous version to check for more details. The only changes in this series are in patch 3/3, see commit message for details. Robert Foss managed to port Android's drm_hwcomposer

[PATCH v8 3/3] drm/fence: add out-fences support

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The syn

[PATCH v8 3/3] drm/fence: add out-fences support

From: Gustavo Padovan Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The sync_file and fd are allocated/created before

[PATCH v8 0/3] drm: add explict fencing

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Hi, Another iteration after Brian comments. Please refer to the cover letter[1] in a previous version to check for more details. The changes since the last version can be seen in commit message on each patch. Robert Foss managed t

[PATCH v8 0/3] drm: add explict fencing

From: Gustavo Padovan Hi, Another iteration after Brian comments. Please refer to the cover letter[1] in a previous version to check for more details. The changes since the last version can be seen in commit message on each patch. Robert Foss managed to port Android's drm_hwcomposer

[PATCH v8 1/3] drm/fence: add in-fences support

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> There is now a new property called IN_FENCE_FD attached to every plane state that receives sync_file fds from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_array subclass or just a

[PATCH v8 2/3] drm/fence: add fence timeline to drm_crtc

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the

[PATCH v8 1/3] drm/fence: add in-fences support

From: Gustavo Padovan There is now a new property called IN_FENCE_FD attached to every plane state that receives sync_file fds from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_array subclass or just a normal fence) and then used by DRM

[PATCH v8 2/3] drm/fence: add fence timeline to drm_crtc

From: Gustavo Padovan Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the fence lock, that we pass in fence_init

Re: [PATCH v8 0/3] drm: add explict fencing

Subject was supposed to be v9! sorry about that. 2016-11-11 Gustavo Padovan <gust...@padovan.org>: > From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> > > Hi, > > Another iteration after Brian comments. Please refer to the cover letter[1] in > a previous ver

Re: [PATCH v8 0/3] drm: add explict fencing

Subject was supposed to be v9! sorry about that. 2016-11-11 Gustavo Padovan : > From: Gustavo Padovan > > Hi, > > Another iteration after Brian comments. Please refer to the cover letter[1] in > a previous version to check for more details. > > The changes since the

Re: [PATCH v8 3/3] drm/fence: add out-fences support

Hi Brian, 2016-11-11 Brian Starkey <brian.star...@arm.com>: > Hi Gustavo, > > On Fri, Nov 11, 2016 at 02:16:09PM +0900, Gustavo Padovan wrote: > > From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> > > > > Support DRM out-fences by creating

Re: [PATCH v8 3/3] drm/fence: add out-fences support

Hi Brian, 2016-11-11 Brian Starkey : > Hi Gustavo, > > On Fri, Nov 11, 2016 at 02:16:09PM +0900, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > Support DRM out-fences by creating a sync_file with a fence for each CRTC > > that sets the OUT_FE

[PATCH v8 2/3] drm/fence: add fence timeline to drm_crtc

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the

[PATCH v8 1/3] drm/fence: add in-fences support

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> There is now a new property called IN_FENCE_FD attached to every plane state that receives sync_file fds from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_array subclass or just a

[PATCH v8 0/3] drm: add explict fencing

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Hi, New version of the DRM fences patches with all comments on v7 adressed. Please refer to the cover letter[1] in a previous version to check for more details. The changes since the last version can be seen in commit message on each

[PATCH v8 3/3] drm/fence: add out-fences support

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The syn

[PATCH v8 2/3] drm/fence: add fence timeline to drm_crtc

From: Gustavo Padovan Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the fence lock, that we pass in fence_init

[PATCH v8 1/3] drm/fence: add in-fences support

From: Gustavo Padovan There is now a new property called IN_FENCE_FD attached to every plane state that receives sync_file fds from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_array subclass or just a normal fence) and then used by DRM

[PATCH v8 0/3] drm: add explict fencing

From: Gustavo Padovan Hi, New version of the DRM fences patches with all comments on v7 adressed. Please refer to the cover letter[1] in a previous version to check for more details. The changes since the last version can be seen in commit message on each patch. Robert Foss managed to port

[PATCH v8 3/3] drm/fence: add out-fences support

From: Gustavo Padovan Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The sync_file and fd are allocated/created before

Re: [PATCH v7 3/3] drm/fence: add out-fences support

2016-11-08 Daniel Vetter <dan...@ffwll.ch>: > On Tue, Nov 08, 2016 at 03:54:50PM +0900, Gustavo Padovan wrote: > > From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> > > > > Support DRM out-fences by creating a sync_file with a fence for each CRTC > &g

Re: [PATCH v7 3/3] drm/fence: add out-fences support

2016-11-08 Daniel Vetter : > On Tue, Nov 08, 2016 at 03:54:50PM +0900, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > Support DRM out-fences by creating a sync_file with a fence for each CRTC > > that sets the OUT_FENCE_PTR property. > > > >

[PATCH v7 3/3] drm/fence: add out-fences support

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The syn

[PATCH v7 3/3] drm/fence: add out-fences support

From: Gustavo Padovan Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The sync_file and fd are allocated/created before

[PATCH v7 0/3] drm: add explict fencing

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Hi, This is yet another version of the DRM fences patches. Please refer to the cover letter[1] in a previous version to check for more details. In v7 we now have split most of the out_fences code into prepare_crtc_sig

[PATCH v7 2/3] drm/fence: add fence timeline to drm_crtc

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the

[PATCH v7 0/3] drm: add explict fencing

From: Gustavo Padovan Hi, This is yet another version of the DRM fences patches. Please refer to the cover letter[1] in a previous version to check for more details. In v7 we now have split most of the out_fences code into prepare_crtc_signaling() and unprepare_crtc_signaling() with improved

[PATCH v7 2/3] drm/fence: add fence timeline to drm_crtc

From: Gustavo Padovan Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the fence lock, that we pass in fence_init

[PATCH v7 1/3] drm/fence: add in-fences support

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> There is now a new property called IN_FENCE_FD attached to every plane state that receives sync_file fds from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_array subclass or just a

[PATCH v7 1/3] drm/fence: add in-fences support

From: Gustavo Padovan There is now a new property called IN_FENCE_FD attached to every plane state that receives sync_file fds from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_array subclass or just a normal fence) and then used by DRM

Re: [PATCH] drm/sun4i: Propagate error to the caller

-- > drivers/gpu/drm/sun4i/sun4i_drv.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Gustavo

Re: [PATCH] drm/sun4i: Propagate error to the caller

ertion(+), 1 deletion(-) Reviewed-by: Gustavo Padovan Gustavo

Re: [PATCH v2 1/7] selftest: sync: basic tests for sw_sync framework

Hi Emilio, 2016-10-19 Emilio López : > These tests are based on the libsync test suite from Android. > This commit lays the ground for future tests, as well as includes > tests for a variety of basic allocation commands. > > Signed-off-by: Emilio López

Re: [PATCH v2 1/7] selftest: sync: basic tests for sw_sync framework

Hi Emilio, 2016-10-19 Emilio López : > These tests are based on the libsync test suite from Android. > This commit lays the ground for future tests, as well as includes > tests for a variety of basic allocation commands. > > Signed-off-by: Emilio López > --- > tools/testing/selftests/Makefile

Re: [PATCH v6 4/6] drm/fence: add in-fences support

2016-10-28 Daniel Vetter <dan...@ffwll.ch>: > On Thu, Oct 27, 2016 at 05:37:09PM -0200, Gustavo Padovan wrote: > > From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> > > > > There is now a new property called FENCE_FD attached to every plane > > st

Re: [PATCH v6 4/6] drm/fence: add in-fences support

2016-10-28 Daniel Vetter : > On Thu, Oct 27, 2016 at 05:37:09PM -0200, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > There is now a new property called FENCE_FD attached to every plane > > state that receives the sync_file fd from userspace via

[PATCH v6 6/6] drm/fence: add out-fences support

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The syn

[PATCH v6 3/6] drm/msm: use drm_atomic_set_fence_for_plane() to set the fence

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> drm_atomic_set_fence_for_plane() is smart and won't overwrite plane_state->fence if the user already set an explicit fence there. Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk> --- drivers/gpu/drm/msm/m

[PATCH v6 0/6] drm: add explict fencing

From: Gustavo Padovan <gustavo.pado...@collabora.co.uk> This is yet another version of the DRM fences patches. Please refer to the cover letter[1] in previous version to check the fences details. For v6 we create drm_atomic_set_fence_for_plane() that tries to abstract from drivers

<    1   2   3   4   5   6   7   8   9   10   >