summaryrefslogtreecommitdiff
path: root/drivers/mfd/ezx-pcap.c
diff options
context:
space:
mode:
authorJerome Glisse <jglisse@redhat.com>2011-11-18 11:47:03 -0500
committerJerome Glisse <jglisse@redhat.com>2011-12-05 18:25:21 -0500
commitc9a49e79367428d33d80152534e28c615f880a87 (patch)
tree1cf782ac24c57266c59f5c18963274038d53af5a /drivers/mfd/ezx-pcap.c
parent56914a460c19d86435be8981cf2a5d1adc76b2e8 (diff)
drm/ttm: callback move_notify any time bo placement change v4
Previously we were calling back move_notify in error path when the bo is returned to it's original position or when destroy the bo. When destroying the bo set the new mem placement as NULL when calling back in the driver. Updating nouveau to deal with NULL placement properly. v2: reserve the object before calling move_notify in bo destroy path at that point ttm should be the only piece of code interacting with the object so atomic_set is safe here. v3: callback move notify only once the bo is in its new position call move notify want swaping out the buffer v4:- don't call move_notify when swapin out bo, assume driver should do what is appropriate in swap notify - move move_notify call back to ttm_bo_cleanup_memtype_use for destroy path Reviewed-by: Jerome Glisse <jglisse@redhat.com> Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com>
Diffstat (limited to 'drivers/mfd/ezx-pcap.c')
0 files changed, 0 insertions, 0 deletions