rfkill « net - net-next.git - net-next plumbings

Mode	Name	Size
-rw-r--r--	Kconfig	774	log plain
-rw-r--r--	Makefile	184	log plain
-rw-r--r--	core.c	31731	log plain
-rw-r--r--	input.c	8962	log plain
-rw-r--r--	rfkill-gpio.c	4750	log plain
-rw-r--r--	rfkill.h	740	log plain

`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/memory')