search for: e69c463

Displaying 2 results from an estimated 2 matches for "e69c463".

Did you mean: 369463
2013 Aug 27
0
[PATCH 3/9] drm/nouveau: Allocate local event handlers
...++++++++ drivers/gpu/drm/nouveau/core/include/core/event.h | 6 ++++++ drivers/gpu/drm/nouveau/nouveau_fence.c | 15 +++++++------- 3 files changed, 38 insertions(+), 7 deletions(-) diff --git a/drivers/gpu/drm/nouveau/core/core/event.c b/drivers/gpu/drm/nouveau/core/core/event.c index e69c463..1a8d685 100644 --- a/drivers/gpu/drm/nouveau/core/core/event.c +++ b/drivers/gpu/drm/nouveau/core/core/event.c @@ -23,6 +23,30 @@ #include <core/os.h> #include <core/event.h> +int +nouveau_event_handler_create(struct nouveau_event *event, int index, + int (*func)(struct nouv...
2013 Aug 27
11
[PATCH 0/9] drm/nouveau: Cleanup event/handler design
This series was originally motivated by a deadlock, introduced in commit 1d7c71a3e2f77336df536855b0efd2dc5bdeb41b 'drm/nouveau/disp: port vblank handling to event interface', due to inverted lock order between nouveau_drm_vblank_enable() and nouveau_drm_vblank_handler() (the complete lockdep report is included in the patch 4/5 changelog). Because this series fixes the vblank event