summaryrefslogtreecommitdiffstats
path: root/Documentation/wimax
diff options
context:
space:
mode:
authorDaniel Vetter <daniel.vetter@ffwll.ch>2013-07-04 23:35:28 +0200
committerDaniel Vetter <daniel.vetter@ffwll.ch>2013-07-11 14:36:43 +0200
commit59cdb63d529c81fc8ac0620ad50f29d5fb4411c9 (patch)
tree18e20e7e3a863d18ca30c0fce9853657fb86390e /Documentation/wimax
parent2adbee62e00d869a30cb93ea2269e5ea26a9bbc4 (diff)
downloadblackbird-op-linux-59cdb63d529c81fc8ac0620ad50f29d5fb4411c9.tar.gz
blackbird-op-linux-59cdb63d529c81fc8ac0620ad50f29d5fb4411c9.zip
drm/i915: kill dev_priv->rps.lock
Now that the rps interrupt locking isn't clearly separated (at elast conceptually) from all the other interrupt locking having a different lock stopped making sense: It protects much more than just the rps workqueue it started out with. But with the addition of VECS the separation started to blurr and resulted in some more complex locking for the ring interrupt refcount. With this we can (again) unifiy the ringbuffer irq refcounts without causing a massive confusion, but that's for the next patch. v2: Explain better why the rps.lock once made sense and why no longer, requested by Ben. Reviewed-by: Ben Widawsky <ben@bwidawsk.net> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'Documentation/wimax')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud