Thread (19 messages) 19 messages, 3 authors, 2015-08-17

Re: [PATCH V3 3/6] slimbus: Add messaging APIs to slimbus framework

From: Mark Brown <broonie@kernel.org>
Date: 2015-08-15 02:14:46
Also in: linux-arm-msm, lkml

On Fri, Aug 14, 2015 at 07:25:25PM +0100, Mark Brown wrote:
On Mon, Aug 03, 2015 at 12:59:47AM -0600, Sagar Dharia wrote:
quoted
+	sema_init(&ctrl->tx_sem, (ctrl->tx.n - 1));
This sempahore counts the number of free slots in the statically
allocated list of transfers we have allocated.  It would be good to see
some discussion in the changelog as to why we've got this statically
allocated pool rather than just dynamically allocating them as needed -
I can see a performance argument there but it'd be good to have the
thinking documented.
One other related thing here: we're keeping the buffers permanently
coherently mapped rather than only mapping them to the device as needed.
Is this the best approach?  On the one hand it increases the cost to the
CPU when setting things up and reading data back, on the other hand it
avoids mapping operations.

Since it's becoming part of the driver API with this it bears some
thought, it will be a little annoying (and fiddly) to change later.

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help