On Tue, Apr 07, 2015 at 08:18:57PM +0200, Martin Sperl wrote:
> > On 07.04.2015, at 19:40, Mark Brown <[email protected]> wrote:

> > For your workload perhaps.  For some workloads they are very common
> > (register reads are the most obvious example, they are typically a write
> > transfer to provide the register address followed by a read transfer for
> > the data).

> Which spi_write_then_read collapses into a single transfer.

No it doesn't.  It creates a single message with two transfers (which is
what I'd expect any user doing this to do, there are others that don't
use the SPI helper APIs).

Attachment: signature.asc
Description: Digital signature

Reply via email to