diff options
| author | Daniel Vetter <daniel.vetter@ffwll.ch> | 2011-10-26 00:14:15 +0200 |
|---|---|---|
| committer | Dave Airlie <airlied@redhat.com> | 2012-07-19 22:50:16 -0400 |
| commit | e2b3c5b64b35af35b0715936f88212c457394c2f (patch) | |
| tree | 9a6afff5fe812b63bed412cf442fe2c3a453671e /include/drm | |
| parent | 923d1fe86b4a98292bee8f08f386eb3eb4c7927e (diff) | |
| download | linux-stable-e2b3c5b64b35af35b0715936f88212c457394c2f.tar.gz linux-stable-e2b3c5b64b35af35b0715936f88212c457394c2f.tar.bz2 linux-stable-e2b3c5b64b35af35b0715936f88212c457394c2f.zip | |
drm/savage: clean up reclaim_buffers
The reclaim_buffers function of the savage driver actually wants to run
with the hw_lock held - at least there are printks in the call-chain
to that effect. But the drm core only calls reclaim_buffers as used
by savage _after_ forcefully dropping the hwlock (in case it's still
hold by the closing fd).
So do the same idlelock dance as for the other dma drivers and hope
that papers over any issues.
v2: Don't let the idlelock linger around.
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Tested-by: Tormod Volden <debian.tormod@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'include/drm')
0 files changed, 0 insertions, 0 deletions