summaryrefslogtreecommitdiff
path: root/net/caif/cfvidl.c
diff options
context:
space:
mode:
authorDave Airlie <airlied@redhat.com>2017-02-03 09:09:36 +1000
committerDave Airlie <airlied@redhat.com>2017-02-03 09:09:36 +1000
commita20def95401112358bcc90242f252a96084a2d47 (patch)
treeec6ed90dbf0a2537a57ed5c29b3fd01da8295061 /net/caif/cfvidl.c
parent52b679f60e2a68af88411f12318675a2424a0e14 (diff)
parente8fe4f4b2b7b93048729538321c681c0cff33b39 (diff)
Merge tag 'topic/vma-fix-for-4.10-2017-02-02' of git://anongit.freedesktop.org/git/drm-intel into drm-fixes
here's Maarten's backport of the vma fixes for v4.10. * tag 'topic/vma-fix-for-4.10-2017-02-02' of git://anongit.freedesktop.org/git/drm-intel: drm/i915: Track pinned vma in intel_plane_state drm/atomic: Unconditionally call prepare_fb.
Diffstat (limited to 'net/caif/cfvidl.c')
0 files changed, 0 insertions, 0 deletions
->cyclic' is written by `pl330_alloc_chan_resources' under `pl330->lock' but read by `pl330_tx_submit' under `pch->lock'. Second, I have removed locking from `pl330_request_channel' and `pl330_release_channel' functions. Function `pl330_request_channel' is only called from `pl330_alloc_chan_resources', so the lock is already held. Function `pl330_release_channel' is called from `pl330_free_chan_resources', which already holds the lock, and from `pl330_del'. Function `pl330_del' is called in an error path of `pl330_probe' and at the end of `pl330_remove', but I assume that there cannot be concurrent accesses to the protected data at those points. Signed-off-by: Iago Abal <mail@iagoabal.eu> Reviewed-by: Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Diffstat (limited to 'include/dt-bindings/clock/exynos5433.h')