drm/omap: fix issue w/ fb attached to multiple CRTCs
authorRob Clark <rob@ti.com>
Fri, 12 Oct 2012 23:58:02 +0000 (18:58 -0500)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 22 Oct 2012 22:46:37 +0000 (15:46 -0700)
commitb74af83dd289270e1486cf5d9f0e3e894c76bd30
tree56b3da5ef8d50a21cc9c60ea49e4c9632b5748ad
parentfaaa054036e395d4e847d1dac49a55b7ef85f500
drm/omap: fix issue w/ fb attached to multiple CRTCs

When the fb is detached from one CRTC/plane, paddr was set back to
zero.  But really we don't want to do this because the fb could still
be attached to other CRTC/plane(s).  This originally worked like this
to catch cases of freeing a pinned fb (but with the refcnt'ing this
should no longer be needed).  Also, there is checking in the GEM code
for freeing a pinned GEM object, so this extra level of checking is
redundant.

Signed-off-by: Rob Clark <rob@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/staging/omapdrm/omap_fb.c