[PATCH 1/3] drm/gma500: Unpin framebuffer when destroying it

2013-06-05 Thread Patrik Jakobsson
On Sun, May 26, 2013 at 11:00 PM, Daniel Vetter wrote: > On Sun, May 26, 2013 at 10:31 PM, Patrik Jakobsson > wrote: >> On Sun, May 26, 2013 at 9:07 PM, Daniel Vetter wrote: >>> On Sun, May 26, 2013 at 08:03:53PM +0200, Patrik Jakobsson wrote: A framebuffer is pinned when it's set as pipe b

Re: [PATCH 1/3] drm/gma500: Unpin framebuffer when destroying it

2013-06-05 Thread Patrik Jakobsson
On Sun, May 26, 2013 at 11:00 PM, Daniel Vetter wrote: > On Sun, May 26, 2013 at 10:31 PM, Patrik Jakobsson > wrote: >> On Sun, May 26, 2013 at 9:07 PM, Daniel Vetter wrote: >>> On Sun, May 26, 2013 at 08:03:53PM +0200, Patrik Jakobsson wrote: A framebuffer is pinned when it's set as pipe b

[PATCH 1/3] drm/gma500: Unpin framebuffer when destroying it

2013-05-26 Thread Daniel Vetter
On Sun, May 26, 2013 at 10:31 PM, Patrik Jakobsson wrote: > On Sun, May 26, 2013 at 9:07 PM, Daniel Vetter wrote: >> On Sun, May 26, 2013 at 08:03:53PM +0200, Patrik Jakobsson wrote: >>> A framebuffer is pinned when it's set as pipe base, so we also need to >>> unpin it when it's destroyed. Some

[PATCH 1/3] drm/gma500: Unpin framebuffer when destroying it

2013-05-26 Thread Patrik Jakobsson
On Sun, May 26, 2013 at 9:07 PM, Daniel Vetter wrote: > On Sun, May 26, 2013 at 08:03:53PM +0200, Patrik Jakobsson wrote: >> A framebuffer is pinned when it's set as pipe base, so we also need to >> unpin it when it's destroyed. Some framebuffers are never used as >> scanout (no mode set on them)

[PATCH 1/3] drm/gma500: Unpin framebuffer when destroying it

2013-05-26 Thread Daniel Vetter
On Sun, May 26, 2013 at 08:03:53PM +0200, Patrik Jakobsson wrote: > A framebuffer is pinned when it's set as pipe base, so we also need to > unpin it when it's destroyed. Some framebuffers are never used as > scanout (no mode set on them) so if the pin count is less than one, no > unpinning is need

[PATCH 1/3] drm/gma500: Unpin framebuffer when destroying it

2013-05-26 Thread Patrik Jakobsson
A framebuffer is pinned when it's set as pipe base, so we also need to unpin it when it's destroyed. Some framebuffers are never used as scanout (no mode set on them) so if the pin count is less than one, no unpinning is needed. Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=889511 Bugzilla

Re: [PATCH 1/3] drm/gma500: Unpin framebuffer when destroying it

2013-05-26 Thread Daniel Vetter
On Sun, May 26, 2013 at 10:31 PM, Patrik Jakobsson wrote: > On Sun, May 26, 2013 at 9:07 PM, Daniel Vetter wrote: >> On Sun, May 26, 2013 at 08:03:53PM +0200, Patrik Jakobsson wrote: >>> A framebuffer is pinned when it's set as pipe base, so we also need to >>> unpin it when it's destroyed. Some

Re: [PATCH 1/3] drm/gma500: Unpin framebuffer when destroying it

2013-05-26 Thread Patrik Jakobsson
On Sun, May 26, 2013 at 9:07 PM, Daniel Vetter wrote: > On Sun, May 26, 2013 at 08:03:53PM +0200, Patrik Jakobsson wrote: >> A framebuffer is pinned when it's set as pipe base, so we also need to >> unpin it when it's destroyed. Some framebuffers are never used as >> scanout (no mode set on them)

Re: [PATCH 1/3] drm/gma500: Unpin framebuffer when destroying it

2013-05-26 Thread Daniel Vetter
On Sun, May 26, 2013 at 08:03:53PM +0200, Patrik Jakobsson wrote: > A framebuffer is pinned when it's set as pipe base, so we also need to > unpin it when it's destroyed. Some framebuffers are never used as > scanout (no mode set on them) so if the pin count is less than one, no > unpinning is need

[PATCH 1/3] drm/gma500: Unpin framebuffer when destroying it

2013-05-26 Thread Patrik Jakobsson
A framebuffer is pinned when it's set as pipe base, so we also need to unpin it when it's destroyed. Some framebuffers are never used as scanout (no mode set on them) so if the pin count is less than one, no unpinning is needed. Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=889511 Bugzilla