[PATCH 2/5] exynos: add EXYNOS_G2D_EVENT to drmHandleEvent

2015-04-23 Thread Tobias Jakobi
Hello Emil, On 2015-04-21 20:14, Emil Velikov wrote: > Hi Tobias, > > On 30/03/15 13:04, Tobias Jakobi wrote: >> Hello, >> >> On 2015-03-30 02:02, Rob Clark wrote: >>> so, iirc, vmwgfx also has some custom events.. not really sure if >>> they have their own hand-rolled drmHandleEvent() or if th

[PATCH 2/5] exynos: add EXYNOS_G2D_EVENT to drmHandleEvent

2015-04-21 Thread Emil Velikov
Hi Tobias, On 30/03/15 13:04, Tobias Jakobi wrote: > Hello, > > On 2015-03-30 02:02, Rob Clark wrote: >> so, iirc, vmwgfx also has some custom events.. not really sure if >> they have their own hand-rolled drmHandleEvent() or if they have >> another way of catching those. >> >> Maybe we need som

[PATCH 2/5] exynos: add EXYNOS_G2D_EVENT to drmHandleEvent

2015-03-30 Thread Tobias Jakobi
Hello, On 2015-03-30 02:02, Rob Clark wrote: > so, iirc, vmwgfx also has some custom events.. not really sure if > they have their own hand-rolled drmHandleEvent() or if they have > another way of catching those. > > Maybe we need some more flexible way to register handlers for driver > custom e

[PATCH 2/5] exynos: add EXYNOS_G2D_EVENT to drmHandleEvent

2015-03-30 Thread Tobias Jakobi
Hello, On 2015-03-30 02:02, Rob Clark wrote: > Maybe we need some more flexible way to register handlers for driver > custom events? But everyone adding their own thing to > drmHandleEvent() doesn't really seem so nice.. that said, I'm not > sure how much to care. If it is just exynos and vmwg

[PATCH 2/5] exynos: add EXYNOS_G2D_EVENT to drmHandleEvent

2015-03-29 Thread Rob Clark
so, iirc, vmwgfx also has some custom events.. not really sure if they have their own hand-rolled drmHandleEvent() or if they have another way of catching those. Maybe we need some more flexible way to register handlers for driver custom events? But everyone adding their own thing to drmHandleEv

[PATCH 2/5] exynos: add EXYNOS_G2D_EVENT to drmHandleEvent

2015-03-23 Thread Emil Velikov
Hi Tobias, On 22/03/15 16:29, Tobias Jakobi wrote: > Hello Emil, > Emil Velikov wrote: >> I fear we are not (yet) allowed to do either of these changes. >> >> The exynos/exynos_drm.h header is (supposed to) be in sync/come from the >> kernel. And changes here are to be reflected only when the corre

[PATCH 2/5] exynos: add EXYNOS_G2D_EVENT to drmHandleEvent

2015-03-22 Thread Tobias Jakobi
Hello Emil, Emil Velikov wrote: > I fear we are not (yet) allowed to do either of these changes. > > The exynos/exynos_drm.h header is (supposed to) be in sync/come from the > kernel. And changes here are to be reflected only when the corresponding > patch lands in drm-next (as per RELEASING). t

[PATCH 2/5] exynos: add EXYNOS_G2D_EVENT to drmHandleEvent

2015-03-22 Thread Emil Velikov
On 20/03/15 22:25, Tobias Jakobi wrote: > This event is specific to Exynos G2D DRM driver. Only > process it when Exynos support is enabled. > > Signed-off-by: Tobias Jakobi > --- > exynos/exynos_drm.h | 12 > xf86drm.h | 7 ++- > xf86drmMode.c | 18

[PATCH 2/5] exynos: add EXYNOS_G2D_EVENT to drmHandleEvent

2015-03-20 Thread Tobias Jakobi
This event is specific to Exynos G2D DRM driver. Only process it when Exynos support is enabled. Signed-off-by: Tobias Jakobi --- exynos/exynos_drm.h | 12 xf86drm.h | 7 ++- xf86drmMode.c | 18 ++ 3 files changed, 36 insertions(+), 1 deletion(-)