From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: possible MXS-i2c bug
Date: Fri, 27 Apr 2012 17:41:19 +0200 [thread overview]
Message-ID: <20120427154119.GF16504@pengutronix.de> (raw)
In-Reply-To: <201204271708.53467.marex@denx.de>
> 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>
next prev parent reply other threads:[~2012-04-27 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 11:26 possible MXS-i2c bug Marek Vasut
2012-04-26 11:41 ` Fabio Estevam
2012-04-26 11:42 ` Wolfram Sang
2012-04-26 23:10 ` Marek Vasut
2012-04-27 14:59 ` Wolfram Sang
2012-04-27 15:08 ` Marek Vasut
2012-04-27 15:41 ` Wolfram Sang [this message]
2012-04-27 15:53 ` Marek Vasut
2012-04-27 16:37 ` Wolfram Sang
2012-04-28 3:03 ` [TEST PATCH] mxs-i2c DMA support Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120427154119.GF16504@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).