From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] OMAP3 i2c issues on IGEP, u-boot 2013.10
Date: Wed, 27 Nov 2013 16:35:17 +0100 [thread overview]
Message-ID: <20131127163517.58766db5@skate> (raw)
In-Reply-To: <20131127144555.GZ420@bill-the-cat>
Dear Tom Rini,
On Wed, 27 Nov 2013 09:45:55 -0500, Tom Rini wrote:
> > I see that 960187ffa125b3938fec4b827bd9e8c04a204af8 ("ARM: OMAP: I2C:
> > New read, write and probe functions") has changed significantly the
> > OMAP I2C driver. And it turns out that reverting this commit actually
> > fixes the problem. No more error messages, no more hang at boot. The
> > commit message says that it was tested on OMAP4, OMAP5 and AM335x, but
> > apparently OMAP3 isn't working all that well with this commit.
>
> I don't see this problem on my omap3_beagle, but I don't have that in
> heavy rotation either. Looking things over, can you try the following
> patch, which just drops the extra sanity check for unconfigured pads.
> The kernel doesn't have any logic like this and I suspect that while
> it's reliable enough of a check on some platforms, it's only true for
> the OMAP4+ variant of the block.
Seems a little bit better with this patch. But now, amongst
approximately 12 boots, I had two boots that failed with:
OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz
IGEPv2 + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 512 MiB
MMC: OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus 0 are properly configured
i2c_write: error waiting for addr ACK (status=0x0)
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus 0 are properly configured
i2c_write: error waiting for addr ACK (status=0x0)
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus 0 are properly configured
i2c_write: error waiting for addr ACK (status=0x0)
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus 0 are properly configured
i2c_write: error waiting for addr ACK (status=0x0)
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus 0 are properly configured
i2c_write: error waiting for addr ACK (status=0x0)
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus 0 are properly configured
i2c_read: error waiting for addr ACK (status=0x0)
TWL4030:USB:Read[0xfd] Error 1
[... more of the same stuff indefinitely ...]
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-27 15:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 12:19 [U-Boot] OMAP3 i2c issues on IGEP, u-boot 2013.10 Thomas Petazzoni
2013-11-27 13:56 ` Enric Balletbo Serra
2013-11-27 14:11 ` Thomas Petazzoni
2013-11-27 14:22 ` Enric Balletbo Serra
2013-11-27 14:50 ` Andreas Bießmann
2013-11-27 14:52 ` Nikita Kiryanov
2013-11-27 15:28 ` Thomas Petazzoni
2013-11-27 15:52 ` Nikita Kiryanov
2013-11-27 16:01 ` Lubomir Popov
2013-11-27 16:13 ` Tom Rini
2013-11-27 21:16 ` Lubomir Popov
2013-11-27 16:10 ` Thomas Petazzoni
2013-11-27 16:31 ` Nikita Kiryanov
2013-11-27 17:12 ` Enric Balletbo Serra
2013-11-28 13:06 ` Nikita Kiryanov
2013-11-27 14:58 ` Nikita Kiryanov
2013-11-27 14:45 ` Tom Rini
2013-11-27 15:35 ` Thomas Petazzoni [this message]
2013-11-27 15:45 ` Michael Trimarchi
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=20131127163517.58766db5@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=u-boot@lists.denx.de \
/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.