public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] OMAP USB, beagle-xm fail
Date: Mon, 19 Mar 2012 01:13:19 +0100	[thread overview]
Message-ID: <201203190113.20171.marex@denx.de> (raw)
In-Reply-To: <CA+M6bXmavDnyv9H87xw8Csc0WcCrT+wthmT5rQFagv7MAUCnTA@mail.gmail.com>

Dear Tom Rini,

> On Mon, Feb 13, 2012 at 4:46 AM, Patil, Rachna <rachna@ti.com> wrote:
> > Hi Govindraj,
> > 
> > On Mon, Feb 13, 2012 at 14:29:56, Govindraj wrote:
> >> Hi Peter,
> >> 
> >> On Mon, Feb 13, 2012 at 1:52 PM, Peter Meerwald <pmeerw@pmeerw.net> wrote:
> >> > Hello,
> >> > 
> >> > the recent OMAP USB changes (43b62393da6dfdd7f503d1b37344463a05ea47b5,
> >> > 29321c0518d99494ab2a250e5b4f75b3add83b11) fail on beagleboard-xm rev.
> >> > C, see below
> >> 
> >> The errors have nothing to do with ehci patch merges, (I had tested it
> >> on beagle rev c board before posting it out)
> >> 
> >> Looking into it closely the below two patches are causing this issue:
> >> 
> >> [...]
> >> commit 498cbdfe62a8330f6c89765bdd15e60328a26511
> >> Author: Patil, Rachna <rachna@ti.com>
> >> Date:   Sun Jan 22 23:46:23 2012 +0000
> >> 
> >> ARM: AM33XX: Add AM33XX I2C driver support
> >> 
> >> commit 2faa76196af4b3e93bcb9e38ed9090cbd3b06db3
> >> Author: Patil, Rachna <rachna@ti.com>
> >> Date:   Sun Jan 22 23:44:12 2012 +0000
> >> 
> >> ARM: I2C: I2C Multi byte address support [...]
> >> 
> >> Reverting these two patches I don't see these errors on my beagle rev c
> >> board logs as in here [1]
> > 
> > I have tested these patches on AM335x EVM, AM335x Beaglebone and
> > OMAP35xx. I did not face any issues w.r.t these EVM's.
> > I tried i2c probe, read/write and all of it worked as expected.
> > Also from the logs in [1] I still see an I2C error " wait_for_bb:
> > I2C_STAT=1000", which is bus busy indication.
> 
> To be clear, I assume you're looking for one of the omap37xx platforms
> to see why the busy changes have broken it.  Thanks.

What's the status here?

Best regards,
Marek Vasut

  reply	other threads:[~2012-03-19  0:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  8:22 [U-Boot] OMAP USB, beagle-xm fail Peter Meerwald
2012-02-13  8:59 ` Govindraj
2012-02-13 10:52   ` Peter Meerwald
2012-02-13 11:46   ` Patil, Rachna
2012-02-13 14:24     ` Tom Rini
2012-03-19  0:13       ` Marek Vasut [this message]
2012-03-19  1:27         ` Tom Rini
2012-02-14 14:50     ` T

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=201203190113.20171.marex@denx.de \
    --to=marex@denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox