Re: [PATCH 4/5] fpga-mgr: separate getting/locking FPGA manager

2017-04-06 Thread Alan Tull
On Wed, Apr 5, 2017 at 11:07 PM, Moritz Fischer wrote: > Hi Alan, > > minor nits, inline > > On Mon, Mar 13, 2017 at 04:53:32PM -0500, Alan Tull wrote: >> Add fpga_mgr_lock/unlock functions that get a mutex for >> exclusive use. >> >> of_fpga_mgr_get, fpga_mgr_get, and fpga_mgr_put no longer lock

Re: [PATCH 4/5] fpga-mgr: separate getting/locking FPGA manager

2017-04-05 Thread Moritz Fischer
Hi Alan, minor nits, inline On Mon, Mar 13, 2017 at 04:53:32PM -0500, Alan Tull wrote: > Add fpga_mgr_lock/unlock functions that get a mutex for > exclusive use. > > of_fpga_mgr_get, fpga_mgr_get, and fpga_mgr_put no longer lock > the FPGA manager mutex. > > This makes it more straightforward t

[PATCH 4/5] fpga-mgr: separate getting/locking FPGA manager

2017-03-13 Thread Alan Tull
Add fpga_mgr_lock/unlock functions that get a mutex for exclusive use. of_fpga_mgr_get, fpga_mgr_get, and fpga_mgr_put no longer lock the FPGA manager mutex. This makes it more straightforward to save a reference to a FPGA manager and only attempting to lock it when programming the FPGA. Signed-