summaryrefslogtreecommitdiff
path: root/sound/pci/echoaudio/gina24.c
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2017-02-06 14:52:10 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2017-02-06 14:52:10 +0100
commitcbf304e420da96992eae50bb6d51035681340ab8 (patch)
tree76f729910e5fdca468464004f94b70b6b3cca81e /sound/pci/echoaudio/gina24.c
parentd5adbfcd5f7bcc6fa58a41c5c5ada0e5c826ce2c (diff)
parenta9306a63631493afc75893a4ac405d4e1cbae6aa (diff)
parent6e978b22efa1db9f6e71b24440b5f1d93e968ee3 (diff)
Merge branches 'pm-core-fixes' and 'pm-cpufreq-fixes'
* pm-core-fixes: PM / runtime: Avoid false-positive warnings from might_sleep_if() * pm-cpufreq-fixes: cpufreq: intel_pstate: Disable energy efficiency optimization cpufreq: brcmstb-avs-cpufreq: properly retrieve P-state upon suspend cpufreq: brcmstb-avs-cpufreq: extend sysfs entry brcm_avs_pmap
>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 'sound/pci/oxygen/oxygen.c')