From: Gustavo Padovan
This function returns a copy of the array of fences.
Signed-off-by: Gustavo Padovan
---
drivers/dma-buf/fence-array.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/dma-buf/fence-array.c b/drivers/dma-buf/fence-array.c
index 601448a..ce98249
From: Gustavo Padovan
Create sync_file->fence to abstract the type of fence we are using for
each sync_file. If only one fence is present we use a normal struct fence
but if there is more fences to be added to the sync_file a fence_array
is created.
This behaviour is transparent all sync_f
From: Gustavo Padovan
get_fences() should return a copy of all fences in the fence as some
fence subclass (such as fence_array) can store more than one fence at
time.
Signed-off-by: Gustavo Padovan
---
drivers/dma-buf/fence.c | 14 ++
include/linux/fence.h | 3 +++
2 files
Hi Christian,
2016-06-24 Christian König :
> Am 23.06.2016 um 17:29 schrieb Gustavo Padovan:
> > From: Gustavo Padovan
> >
> > Hi all,
> >
> > This is an attempt to improve fence support on Sync File. The basic idea
> > is to have only sync_file->f
2016-06-23 Chris Wilson :
> On Thu, Jun 23, 2016 at 12:29:46PM -0300, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > fence_array requires a function to clean up its state before we
> > are able to call fence_put() and release it.
>
> An explanatio
2016-06-23 Chris Wilson :
> On Thu, Jun 23, 2016 at 12:29:50PM -0300, Gustavo Padovan wrote:
> > -static void sync_file_add_pt(struct sync_file *sync_file, int *i,
> > +static int sync_file_set_fence(struct sync_file *sync_file,
> > +
Hi Greg,
Any comment on this?
Gustavo
2016-05-31 Gustavo Padovan :
> From: Gustavo Padovan
>
> Hi,
>
> The following patches do a clean up on the sw_sync inteface. It starts by
> removing struct sync_timeline_ops, which was creating unecessary wrappers
> in the
From: Gustavo Padovan
Signalling doesn't need to be enabled at sync_file creation, it is only
required if userspace waiting the fence to signal through poll().
Thus we delay fence_add_callback() until poll is called. It only adds the
callback the first time poll() is called. This avo
From: Gustavo Padovan
Creates a function that given an sync file descriptor returns a
fence_collection containing all fences in the sync_file.
If there is only one fence in the sync_file this fence itself is returned,
however if there is more than one, a fence_collection fence is returned.
v2
From: Gustavo Padovan
Document the new function added to sync_file.c
v2: Adapt to fence_array
Signed-off-by: Gustavo Padovan
---
Documentation/sync_file.txt | 19 +++
1 file changed, 19 insertions(+)
diff --git a/Documentation/sync_file.txt b/Documentation/sync_file.txt
Hi Greg,
Any comment on this?
Thanks,
Gustavo
2016-06-20 Gustavo Padovan :
> From: Gustavo Padovan
>
> Hi Greg,
>
> This is the last step in the Sync Framwork de-stage task. It de-stage
> the SW_SYNC validation framework and the sync_debug info debugfs file.
>
>
From: Gustavo Padovan
Signalling doesn't need to be enabled at sync_file creation, it is only
required if userspace waiting the fence to signal through poll().
Thus we delay fence_add_callback() until poll is called. It only adds the
callback the first time poll() is called. This avo
From: Gustavo Padovan
Create sync_file->fence to abstract the type of fence we are using for
each sync_file. If only one fence is present we use a normal struct fence
but if there is more fences to be added to the sync_file a fence_array
is created.
This change cleans up sync_file a bit.
From: Gustavo Padovan
Add helper to check if fence is array.
v2: Comments from Chris Wilson
- remove ternary if from ops comparison
- add EXPORT_SYMBOL(fence_array_ops)
Cc: Chris Wilson
Cc: Christian König
Signed-off-by: Gustavo Padovan
Reviewed-by: Chris Wilson
From: Gustavo Padovan
Document the new function added to sync_file.c
v2: Adapt to fence_array
Signed-off-by: Gustavo Padovan
---
Documentation/sync_file.txt | 15 +++
1 file changed, 15 insertions(+)
diff --git a/Documentation/sync_file.txt b/Documentation/sync_file.txt
index
From: Gustavo Padovan
Creates a function that given an sync file descriptor returns a
fence containing all fences in the sync_file.
v2: Comments by Daniel Vetter
- Adapt to new version of fence_collection_init()
- Hold a reference for the fence we return
v3:
- Adapt to
From: Gustavo Padovan
Hi all,
This is an attempt to improve fence support on Sync File. The basic idea
is to have only sync_file->fence and store all fences there, either as
normal fences or fence_arrays. That way we can remove some potential
duplication when using fence_array with sync_f
From: Gustavo Padovan
Creates a function that given an sync file descriptor returns a
fence containing all fences in the sync_file.
v2: Comments by Daniel Vetter
- Adapt to new version of fence_collection_init()
- Hold a reference for the fence we return
v3:
- Adapt to
From: Gustavo Padovan
Add helper to check if fence is array.
v2: Comments from Chris Wilson
- remove ternary if from ops comparison
- add EXPORT_SYMBOL(fence_array_ops)
Cc: Chris Wilson
Cc: Christian König
Signed-off-by: Gustavo Padovan
Reviewed-by: Chris Wilson
From: Gustavo Padovan
Hi all,
This patchset improves fence support on Sync File. The basic idea
is to have only sync_file->fence and store all fences there, either as
normal fences or fence_arrays. That way we can remove some potential
duplication when using fence_array with sync_file:
From: Gustavo Padovan
Create sync_file->fence to abstract the type of fence we are using for
each sync_file. If only one fence is present we use a normal struct fence
but if there is more fences to be added to the sync_file a fence_array
is created.
This change cleans up sync_file a bit.
From: Gustavo Padovan
Document the new function added to sync_file.c
v2: Adapt to fence_array
Signed-off-by: Gustavo Padovan
---
Documentation/sync_file.txt | 15 +++
1 file changed, 15 insertions(+)
diff --git a/Documentation/sync_file.txt b/Documentation/sync_file.txt
index
From: Gustavo Padovan
As they are not used anywhere outside drm_irq.c make them static.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/drm_irq.c | 7 ++-
include/drm/drmP.h| 2 --
2 files changed, 2 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/drm_irq.c b
From: Gustavo Padovan
Remove legacy usage of drm_handle_vblank()
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/armada/armada_crtc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/armada/armada_crtc.c
b/drivers/gpu/drm/armada/armada_crtc.c
index
From: Gustavo Padovan
Remove legacy usage of drm_handle_vblank()
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/nouveau/nouveau_display.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_display.c
b/drivers/gpu/drm/nouveau
From: Gustavo Padovan
Remove legacy usage of drm_handle_vblank()
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
b/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
index
From: Gustavo Padovan
Remove legacy usage of drm_handle_vblank()
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c
b/drivers/gpu/drm/atmel-hlcdc
From: Gustavo Padovan
Remove legacy usage of drm_handle_vblank()
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/rcar-du/rcar_du_crtc.c
b/drivers/gpu/drm/rcar-du/rcar_du_crtc.c
index
to notify, through fence_signal(),
> +the driver creates an out-fence to be able to notify, through fence_signal(),
> when it has finished using (or processing) that buffer. Out-fences are fences
> that the driver creates.
Thanks, Javier!
Reviewed-by: Gustavo Padovan
Gustavo
Hi Christian,
2016-06-01 Christian König :
> From: Gustavo Padovan
>
> struct fence_collection inherits from struct fence and carries a
> collection of fences that needs to be waited together.
>
> It is useful to translate a sync_file to a fence to remove the complexity
| 13 +++------
> 10 files changed, 21 insertions(+), 18 deletions(-)
Reviewed-by: Gustavo Padovan
Gustavo
2016-06-01 Christian König :
> From: Gustavo Padovan
>
> struct fence_collection inherits from struct fence and carries a
> collection of fences that needs to be waited together.
>
> It is useful to translate a sync_file to a fence to remove the complexity
> of dealing w
>
> Signed-off-by: Christian König
> ---
> drivers/dma-buf/fence-array.c | 33 +
> include/linux/fence-array.h | 3 ++-
> 2 files changed, 27 insertions(+), 9 deletions(-)
Reviewed-by: Gustavo Padovan
Gustavo
From: Gustavo Padovan
Add Gustavo as maintainer for the Sync File Framework. Sumit is
co-maintainer as he maintains drivers/dma-buf/. It also uses Sumit's
tree as base.
Signed-off-by: Gustavo Padovan
Acked-by: Sumit Semwal
Acked-by: Maarten Lankhorst
---
MAINTAINERS | 11 +++
1
From: Gustavo Padovan
We've got a complaint saying that the description was quite obtuse and
indeed it was. This patch tries to improve it.
Cc: Dave Jones
Signed-off-by: Gustavo Padovan
---
drivers/dma-buf/Kconfig | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
From: Gustavo Padovan
Now fence timeline is aware of the last signaled fence, as it
receives the increment to the current value in sync_timeline_signal().
That allow us to remove .has_signaled() from timeline_ops as we can
directly compare using timeline->value and fence->seqno in
From: Gustavo Padovan
Hi,
The following patches do a clean up on the sw_sync inteface. It starts by
removing struct sync_timeline_ops, which was creating unecessary wrappers
in the code and the start to organize the sync_timeline and sw_sync code
better.
sw_sync interface was moved to
From: Gustavo Padovan
Now that the value of fence and the timeline are not stored by sw_sync
anymore we can remove this extra abstraction to retrieve this data.
This patch changes both fence_ops (.fence_value_str and
.timeline_value_str) to return the str directly.
It also clean up struct
From: Gustavo Padovan
We are moving out of staging/android so rename it to a name that is not
related to android anymore.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync.c | 36 ++--
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git
From: Gustavo Padovan
After we removed sw_sync_timeline this arg has not been really used by
anyone, all its users pass the size of struct sync_timeline there.
So simplify this function but not requiring the size anymore.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync.c
From: Gustavo Padovan
We can glue the sw_sync file operations directly on the sync framework
without the need to pass through sw_sync wrappers.
It only builds sw_sync debugfs file support if CONFIG_SW_SYNC is enabled.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/Makefile
From: Gustavo Padovan
Move drv_name, the last field of sync_timeline_ops, to sync_timeline
and remove sync_timeline_ops.
struct sync_timeline_ops was just an extra abstraction on top of
fence_ops, and in the last few commits we removed all it ops in favor
of cleaner fence_ops.
Signed-off-by
From: Gustavo Padovan
Move the list_head members from sync_pt to struct fence was a mistake,
they will not be used by struct fence as planned before, so here we create
sync_pt again to bring the list heads back.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync.c | 40
From: Gustavo Padovan
As we moved value storage to sync_timeline and fence those two structs
became useless and can be removed now.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c| 24 +++-
drivers/staging/android/sw_sync.h| 24
From: Gustavo Padovan
When we call sync_print_fence() fence is always valid.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync_debug.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/android/sync_debug.c
b/drivers/staging/android
From: Gustavo Padovan
This function was just used by the file release function, so we just fold
its content there and remove sync_timeline_destroy().
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c | 19 +++
1 file changed, 3 insertions(+), 16 deletions
From: Gustavo Padovan
Most of the includes there are not necessary anymore.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync.c | 6 --
drivers/staging/android/sync.h | 3 ---
drivers/staging/android/sync_debug.c | 16
3 files changed, 25
From: Gustavo Padovan
The only use sync_timeline will have in upstream kernel is for debugging
through the SW_SYNC interface. So make it internal to SW_SYNC to avoid
people use it in the future.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/Kconfig | 16 +--
drivers/staging
From: Gustavo Padovan
As it is internal to sw_sync now this value will always be "sw_sync".
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c| 11 +++
drivers/staging/android/sync.h | 2 --
drivers/staging/android/sync_debug.c | 2 +-
3 files
From: Gustavo Padovan
Split sync_debug and sw_sync in two different files.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/Makefile | 1 +
drivers/staging/android/sw_sync.c| 136 +++
drivers/staging/android/sync.h | 2 +
drivers
From: Gustavo Padovan
We don't want to export this from the kernel. This is interface is only
for testing and debug. So testers shall copy the ioctl info in their own
projects.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c | 13 -
drivers/st
From: Gustavo Padovan
SW_SYNC only works with DEBUG_FS so state it in the Kconfig file.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/Kconfig | 1 +
drivers/staging/android/sync_debug.c | 4
drivers/staging/android/sync_debug.h | 4 +---
3 files changed, 2 insertions
From: Gustavo Padovan
'destroyed' was set but not used ny anyone.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c | 5 -
drivers/staging/android/sync.h| 5 +
2 files changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/staging/android/sw
From: Gustavo Padovan
This header file only contains information for debugging and SW_SYNC, so
rename it to sync_debug.h instead of having a more generic name.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c| 2 +-
drivers/staging/android/sync_debug.c
2016-10-26 Brian Starkey :
> Some parts of setting up the CRTC out-fence can be re-used for
> writeback out-fences. Factor this out into a separate function.
>
> Signed-off-by: Brian Starkey
> ---
> drivers/gpu/drm/drm_atomic.c | 64
> +++---
> 1 file chan
2016-10-26 Brian Starkey :
> Add the OUT_FENCE_PTR property to writeback connectors, to enable
> userspace to get a fence which will signal once the writeback is
> complete.
>
> A timeline is added to drm_connector for use by the writeback
> out-fences. It is up to drivers to check for a fence in
2016-10-26 Brian Starkey :
> If userspace has asked for an out-fence for the writeback, we add a
> fence to malidp_mw_job, to be signaled when the writeback job has
> completed.
>
> Signed-off-by: Brian Starkey
> ---
> drivers/gpu/drm/arm/malidp_hw.c |5 -
> drivers/gpu/drm/arm/malidp_m
2016-10-26 Brian Starkey :
> Some parts of setting up the CRTC out-fence can be re-used for
> writeback out-fences. Factor this out into a separate function.
>
> Signed-off-by: Brian Starkey
> ---
> drivers/gpu/drm/drm_atomic.c | 64
> +++---
> 1 file chan
2016-10-27 Brian Starkey :
> On Wed, Oct 26, 2016 at 07:43:57PM -0200, Gustavo Padovan wrote:
> > 2016-10-26 Brian Starkey :
> >
> > > If userspace has asked for an out-fence for the writeback, we add a
> > > fence to malidp_mw_job, to be signaled when the
From: Gustavo Padovan
This new function should be used by drivers when setting a implicit
fence for the plane. It abstracts the fact that the user might have
chosen explicit fencing instead.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/drm_atomic.c | 30
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
From: Gustavo Padovan
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
---
drivers/gpu/drm/msm/msm_atomic.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
From: Gustavo Padovan
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 if we are using implicit or explicit fencing
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
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 the atomic commit
IOCTL.
The fd is then translated to a fence (that may be a fence_collection
subclass or just a normal fence) and then used by DRM
From: Gustavo Padovan
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
---
drivers/gpu/drm/imx/imx-drm-core.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
di
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
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 to
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
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
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
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.
> >
> > W
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
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
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 to
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:
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
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
> >
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 to
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
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
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
2016-10-20 Ville Syrjälä :
> On Thu, Oct 20, 2016 at 12:50:05PM -0200, 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.
>
> I still main
2016-10-20 Brian Starkey :
> Hi Gustavo,
>
> On Thu, Oct 20, 2016 at 12:50:04PM -0200, Gustavo Padovan wrote:
> > 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
the out-fence patch because we already
hold the ref when we create the fence. The sync_file refcount patch will
remain.
>
> Couple more comments below.
>
> On Thu, Oct 20, 2016 at 12:50:05PM -0200, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Support DRM o
2016-10-21 Daniel Vetter :
> On Thu, Oct 20, 2016 at 10:15:20PM +0300, Ville Syrjälä wrote:
> > On Thu, Oct 20, 2016 at 07:34:44PM +0300, Ville Syrjälä wrote:
> > > On Thu, Oct 20, 2016 at 01:55:38PM -0200, Gustavo Padovan wrote:
> > > > 2016-10-20 Ville Syrjälä :
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
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 to
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
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
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_FENCE_
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
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 to
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
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 t
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
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 to
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
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
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_hwcom
401 - 500 of 818 matches
Mail list logo
