possible MXS-i2c bug

[Wolfram Sang]

> You can get a large list of i2c messages. In the current implementation, yes, 
> they're iterated in mxs_i2c_xfer_msg. Correct.
> 
> If you want to do DMA transfer do/from the i2c controller, you have to take all 
> these messages and create the chain of DMA transfers according to these 
> messages, correct?

This is what I wonder. I'd think one could work on a per message basis.
Regarding Figure 27-10, the first I2C write command could be sent
seperately (probably even via PIOQUEUE). The only thing to be chained is
the I2C read command and the actual reading of the data.

Just checked, the FSL driver does it basically this way, too.

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120427/db3b5ffd/attachment.sig>