On Fri, Dec 08, 2017 at 02:17:39PM -0800, Gurchetan Singh wrote:
> The problem I'm trying to solve is that the internal cursor fb is leaky and
> even present after closing the drm driver fd. This can be seen by running
> modetest after this test case:
>
> https://chromium.googlesource.com/chromiu
The problem I'm trying to solve is that the internal cursor fb is leaky and
even present after closing the drm driver fd. This can be seen by running
modetest after this test case:
https://chromium.googlesource.com/chromiumos/platform/drm-tests/+/master/drm_cursor_test.c
However, as you mentione
On Wed, Dec 06, 2017 at 07:01:59PM -0800, Gurchetan Singh wrote:
> When a CRTC is disabled and we used an internally created framebuffer,
> this patch disables the cursor plane and drops the reference that was
> introduced when we called drm_internal_framebuffer_create.
>
> Signed-off-by: Gurcheta
When a CRTC is disabled and we used an internally created framebuffer,
this patch disables the cursor plane and drops the reference that was
introduced when we called drm_internal_framebuffer_create.
Signed-off-by: Gurchetan Singh
---
drivers/gpu/drm/drm_crtc.c | 7 +++
1 file changed, 7 ins
