nfp: add support for reading nffw info - net-next.git - net-next plumbings

summary refs log tree commit diff

path: root/include/uapi/drm/savage_drm.h

diff options

author	Jakub Kicinski <jakub.kicinski@netronome.com>	2017-02-09 09:17:32 -0800
committer	David S. Miller <davem@davemloft.net>	2017-02-10 15:52:25 -0500
commit	a0d8e02c35ff6068925d8c5ff4202b561aa90de6 (patch)
tree	4abb78b2781c021d8eb88567f01b9f9f826b4097 /include/uapi/drm/savage_drm.h
parent	59a8474888e9b06252ebe8979630b371c926a00c (diff)

nfp: add support for reading nffw info

NFFW info is a resource which contains information about the loaded application firmware. Add code which will allow us to decode it and retrieve MIP location. Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com> Signed-off-by: David S. Miller <davem@davemloft.net>

Diffstat (limited to 'include/uapi/drm/savage_drm.h')

0 files changed, 0 insertions, 0 deletions

ck 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 'tools/testing/selftests/vm/hugepage-mmap.c')