#ifndef WM8785_H_INCLUDED #define WM8785_H_INCLUDED #define WM8785_R0 0 #define WM8785_R1 1 #define WM8785_R2 2 #define WM8785_R7 7 /* R0 */ #define WM8785_MCR_MASK 0x007 #define WM8785_MCR_SLAVE 0x000 #define WM8785_MCR_MASTER_128 0x001 #define WM8785_MCR_MASTER_192 0x002 #define WM8785_MCR_MASTER_256 0x003 #define WM8785_MCR_MASTER_384 0x004 #define WM8785_MCR_MASTER_512 0x005 #define WM8785_MCR_MASTER_768 0x006 #define WM8785_OSR_MASK 0x018 #define WM8785_OSR_SINGLE 0x000 #define WM8785_OSR_DOUBLE 0x008 #define WM8785_OSR_QUAD 0x010 #define WM8785_FORMAT_MASK 0x060 #define WM8785_FORMAT_RJUST 0x000 #define WM8785_FORMAT_LJUST 0x020 #define WM8785_FORMAT_I2S 0x040 #define WM8785_FORMAT_DSP 0x060 /* R1 */ #define WM8785_WL_MASK 0x003 #define WM8785_WL_16 0x000 #define WM8785_WL_20 0x001 #define WM8785_WL_24 0x002 #define WM8785_WL_32 0x003 #define WM8785_LRP 0x004 #define WM8785_BCLKINV 0x008 #define WM8785_LRSWAP 0x010 #define WM8785_DEVNO_MASK 0x0e0 /* R2 */ #define WM8785_HPFR 0x001 #define WM8785_HPFL 0x002 #define WM8785_SDODIS 0x004 #define WM8785_PWRDNR 0x008 #define WM8785_PWRDNL 0x010 #define WM8785_TDM_MASK 0x1c0 #endif nds-private-remove' selected='selected'>nds-private-remove net-next plumbingsTobias Klauser
summaryrefslogtreecommitdiff
path: root/include/trace/events/host1x.h
diff options
context:
space:
mode:
authorIago Abal <mail@iagoabal.eu>2017-01-11 14:00:21 +0100
committerVinod Koul <vinod.koul@intel.com>2017-01-25 15:35:11 +0530
commit91539eb1fda2d530d3b268eef542c5414e54bf1a (patch)
tree960f5ca6342ad20837aff18aad6e8ecd7da32fd6 /include/trace/events/host1x.h
parent6610d0edf6dc7ee97e46ab3a538a565c79d26199 (diff)
dmaengine: pl330: fix double lock
The static bug finder EBA (http://www.iagoabal.eu/eba/) reported the following double-lock bug: Double lock: 1. spin_lock_irqsave(pch->lock, flags) at pl330_free_chan_resources:2236; 2. call to function `pl330_release_channel' immediately after; 3. call to function `dma_pl330_rqcb' in line 1753; 4. spin_lock_irqsave(pch->lock, flags) at dma_pl330_rqcb:1505. I have fixed it as suggested by Marek Szyprowski. First, I have replaced `pch->lock' with `pl330->lock' in functions `pl330_alloc_chan_resources' and `pl330_free_chan_resources'. This avoids the double-lock by acquiring a different lock than `dma_pl330_rqcb'. NOTE that, as a result, `pl330_free_chan_resources' executes `list_splice_tail_init' on `pch->work_list' under lock `pl330->lock', whereas in the rest of the code `pch->work_list' is protected by `pch->lock'. I don't know if this may cause race conditions. Similarly `pch->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/trace/events/host1x.h')