From: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
To: Torsten Fleischer <to-fleischer-zqRNUXuvxA0b1SvskN2V4Q@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Alexandre Belloni
<alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Fabio Estevam <r49496-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
Lucas Stach <l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Subject: Re: [PATCH] i2c: mxs: Rework the PIO mode operation
Date: Sun, 21 Jul 2013 23:21:22 +0200 [thread overview]
Message-ID: <201307212321.22207.marex@denx.de> (raw)
In-Reply-To: <3767128.gOKkIqK4p5-BVXpyJtzy6LO1Ldfs0Uenw@public.gmane.org>
Hi Torsten,
> Hi Marek,
>
> > Thinking about this, did you correctly configure the EEPROM write sector
> > size? I think it's 32 bytes for this device.
>
> The EEPROM is correctly configured, i.e. page size is set to 32.
>
> I made a test by writing one byte (0x01) to the address 0x0100 of the
> EEPROM. The EEPROM's I2C bus address is 0x54.
> The test has only one transfer with a message length of 3 bytes.
>
> I figured out that the value written to the MXS_I2C_DATA register should be
> 0x010001a8. But instead of that a value of 0x00000000 is written to the
> register.
>
> I think that the reason for that can be found in the following code
> section:
>
> if (i + 1 == msg->len) {
> /* This is the last transfer. */
> start |= flags;
> start &= ~MXS_I2C_CTRL0_RETAIN_CLOCK;
> xlen = (i + 2) % 4;
> data >>= (4 - xlen) * 8;
> } else if ((i & 3) == 2) {
> /* Regular transfer. */
> xlen = 4;
> } else {
> /* Just stuff data. */
> continue;
> }
>
> After the last byte is stuffed into the variable data (i = 2) xlen is
> calculated (with xlen = (i + 2) % 4) to zero. Thus the following shift
> operation (data >>= (4 - xlen) * 8) shifts all the bits out of data that
> already contains 0x010001a8.
You're right, thanks for finding this! Does the following fix look OK ? I added
some more comments and "decompressed" the code some more.
diff --git a/drivers/i2c/busses/i2c-mxs.c b/drivers/i2c/busses/i2c-mxs.c
index fb6f110..ee17b6a 100644
--- a/drivers/i2c/busses/i2c-mxs.c
+++ b/drivers/i2c/busses/i2c-mxs.c
@@ -366,7 +366,7 @@ static int mxs_i2c_pio_setup_xfer(struct i2c_adapter *adap,
struct mxs_i2c_dev *i2c = i2c_get_adapdata(adap);
uint32_t addr_data = msg->addr << 1;
uint32_t data = 0;
- int i, ret, xlen = 0;
+ int i, ret, xlen = 0, xmit = 0;
uint32_t start;
/* Mute IRQs coming from this block. */
@@ -463,20 +463,42 @@ static int mxs_i2c_pio_setup_xfer(struct i2c_adapter
*adap,
data >>= 8;
data |= (msg->buf[i] << 24);
+ xmit = 0;
+
+ /* This is the last transfer of the message. */
if (i + 1 == msg->len) {
- /* This is the last transfer. */
+ /* Add optional STOP flag. */
start |= flags;
+ /* Remove RETAIN_CLOCK bit. */
start &= ~MXS_I2C_CTRL0_RETAIN_CLOCK;
- xlen = (i + 2) % 4;
- data >>= (4 - xlen) * 8;
- } else if ((i & 3) == 2) {
- /* Regular transfer. */
- xlen = 4;
- } else {
- /* Just stuff data. */
- continue;
+ xmit = 1;
}
+ /* Four bytes are ready in the "data" variable. */
+ if ((i & 3) == 2)
+ xmit = 1;
+
+ /* Nothing interesting happened, continue stuffing. */
+ if (!xmit)
+ continue;
+
+ /*
+ * Compute the size of the transfer and shift the
+ * data accordingly.
+ *
+ * i = (4k + 0) .... xlen = 2
+ * i = (4k + 1) .... xlen = 3
+ * i = (4k + 2) .... xlen = 4
+ * i = (4k + 3) .... xlen = 1
+ */
+
+ if ((i % 4) == 3)
+ xlen = 1;
+ else
+ xlen = (i % 4) + 2;
+
+ data >>= (4 - xlen) * 8;
+
dev_dbg(i2c->dev,
"PIO: len=%i pos=%i total=%i [W%s%s%s]\n",
xlen, i, msg->len,
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-07-21 21:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 19:46 [PATCH] i2c: mxs: Rework the PIO mode operation Marek Vasut
[not found] ` <1373312807-13227-1-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
2013-07-08 19:49 ` Marek Vasut
2013-07-09 13:21 ` Alexandre Belloni
2013-07-15 2:05 ` Marek Vasut
[not found] ` <201307150405.53110.marex-ynQEQJNshbs@public.gmane.org>
2013-07-15 12:14 ` Lucas Stach
[not found] ` <1373890479.4172.3.camel-WzVe3FnzCwFR6QfukMTsflXZhhPuCNm+@public.gmane.org>
2013-07-15 12:27 ` Marek Vasut
2013-07-15 14:58 ` Shawn Guo
[not found] ` <20130715145836.GB23589-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2013-07-15 23:25 ` Marek Vasut
2013-07-17 12:16 ` to-fleischer-zqRNUXuvxA0b1SvskN2V4Q
[not found] ` <1UzQet-1Vf4pE0-VM4m3MaA7PGi2rA4ip7KQzlaCuRwF3y+@public.gmane.org>
2013-07-17 16:23 ` Marek Vasut
2013-07-17 17:04 ` Marek Vasut
[not found] ` <201307171904.00784.marex-ynQEQJNshbs@public.gmane.org>
2013-07-18 19:12 ` Torsten Fleischer
[not found] ` <3767128.gOKkIqK4p5-BVXpyJtzy6LO1Ldfs0Uenw@public.gmane.org>
2013-07-21 21:21 ` Marek Vasut [this message]
[not found] ` <201307212321.22207.marex-ynQEQJNshbs@public.gmane.org>
2013-07-28 9:47 ` Torsten Fleischer
2013-07-15 12:43 ` Lucas Stach
[not found] ` <1373892198.4172.17.camel-WzVe3FnzCwFR6QfukMTsflXZhhPuCNm+@public.gmane.org>
2013-07-15 23:24 ` 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=201307212321.22207.marex@denx.de \
--to=marex-ynqeqjnshbs@public.gmane.org \
--cc=alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=r49496-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=to-fleischer-zqRNUXuvxA0b1SvskN2V4Q@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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).