All of lore.kernel.org
 help / color / mirror / Atom feed
From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: possible MXS-i2c bug
Date: Thu, 26 Apr 2012 08:41:27 -0300	[thread overview]
Message-ID: <CAOMZO5BQbyKXYEzpRrjLoyXMY9ykbJ05rtnN2aFAf=+WjQ+K0A@mail.gmail.com> (raw)
In-Reply-To: <201204261326.29388.marex@denx.de>

On Thu, Apr 26, 2012 at 8:26 AM, Marek Vasut <marex@denx.de> wrote:
> Hi,
>
> I recently tried mxs-i2c (on 3.4-rc4) with at24 eeprom, didn't work as expected.
>
> Apparently, there might be some timing issue, when I put printk() into the at24
> driver eeprom write function, it "fixed" itself. Though, replacing the i2c
> driver with i2c gpio also fixed the issue, so I suspect the i2c driver has some
> flaw in it.

Does Wolfram's patch help?
http://www.spinics.net/lists/linux-i2c/msg08002.html

I don't have a I2C eeprom soldered on my mx28evk to test it.

  reply	other threads:[~2012-04-26 11:41 UTC|newest]

Thread overview: 18+ 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 [this message]
     [not found] ` <201204261326.29388.marex-ynQEQJNshbs@public.gmane.org>
2012-04-26 11:42   ` Wolfram Sang
2012-04-26 11:42     ` Wolfram Sang
     [not found]     ` <20120426114201.GC3548-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-04-26 23:10       ` Marek Vasut
2012-04-26 23:10         ` Marek Vasut
     [not found]         ` <201204270110.21377.marex-ynQEQJNshbs@public.gmane.org>
2012-04-27 14:59           ` Wolfram Sang
2012-04-27 14:59             ` Wolfram Sang
     [not found]             ` <20120427145936.GD16504-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-04-27 15:08               ` Marek Vasut
2012-04-27 15:08                 ` Marek Vasut
     [not found]                 ` <201204271708.53467.marex-ynQEQJNshbs@public.gmane.org>
2012-04-27 15:41                   ` Wolfram Sang
2012-04-27 15:41                     ` Wolfram Sang
     [not found]                     ` <20120427154119.GF16504-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-04-27 15:53                       ` Marek Vasut
2012-04-27 15:53                         ` Marek Vasut
     [not found]                         ` <201204271753.39516.marex-ynQEQJNshbs@public.gmane.org>
2012-04-27 16:37                           ` Wolfram Sang
2012-04-27 16:37                             ` Wolfram Sang
     [not found]                             ` <20120427163756.GH16504-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-04-28  3:03                               ` [TEST PATCH] mxs-i2c DMA support Marek Vasut
2012-04-28  3:03                                 ` 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='CAOMZO5BQbyKXYEzpRrjLoyXMY9ykbJ05rtnN2aFAf=+WjQ+K0A@mail.gmail.com' \
    --to=festevam@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.