diff options
author | Daniel Vetter <daniel.vetter@ffwll.ch> | 2012-12-02 20:53:40 (GMT) |
---|---|---|
committer | Daniel Vetter <daniel.vetter@ffwll.ch> | 2013-01-20 21:16:59 (GMT) |
commit | 786b99ed13223d8ac58a937dd348aead45eb8191 (patch) | |
tree | d2fed735d5be17d37d02a2a30260c766c079cf43 /drivers/char/msm_smd_pkt.c | |
parent | 4b096ac10da0b63f09bd123b86fed8deb80646ce (diff) | |
download | linux-786b99ed13223d8ac58a937dd348aead45eb8191.tar.xz |
drm: create drm_framebuffer_lookup
And replace all fb lookups with it. Also add a WARN to
drm_mode_object_find since that is now no longer the blessed interface
to look up an fb. And add kerneldoc to both functions.
This only updates all callsites, but immediately drops the acquired
refence again. Hence all callers still rely on the fact that a mode fb
can't disappear while they're holding the struct mutex. Subsequent
patches will instate proper use of refcounts, and then rework the rmfb
and unref code to no longer serialize fb destruction with the
mode_config lock. We don't want that since otherwise a compositor
might end up stalling for a few frames in rmfb.
v2: Don't use kref_get_unless_zero - Greg KH doesn't like that kind of
interface.
Reviewed-by: Rob Clark <rob@ti.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/char/msm_smd_pkt.c')
0 files changed, 0 insertions, 0 deletions