From: Tony Lindgren <tony@atomide.com>
To: Steve Poulsen <spoulsen@css-design.us>
Cc: Felipe Balbi <me@felipebalbi.com>,
Philip Balister <philip@balister.org>,
linux-omap@vger.kernel.org
Subject: Re: Booting 2.6.25 on the OMAP5912OSK
Date: Tue, 3 Jun 2008 09:49:27 -0700 [thread overview]
Message-ID: <20080603164926.GC6992@atomide.com> (raw)
In-Reply-To: <48455B16.3000506@css-design.us>
* Steve Poulsen <spoulsen@css-design.us> [080603 07:55]:
> I too am seeing this same problem. Do you know when this was introduced
> (kernel version)? I am looking to update the kernel to address some
> flashing issues, and this is the only issue that remains for me. I am
> thinking to revert back to the I2C of the version that should fix this
> issue.
>
> Thanks!
>
> Felipe Balbi wrote:
>> Hi,
>>
>> On Sun, 01 Jun 2008 13:06:03 -0400, Philip Balister <philip@balister.org>
>> wrote:
>>
>>> i2c_omap i2c_omap.1: Transmit overflow
>>> tps65010: power off button
>>>
>>
>> Sounds like a bug in our i2c-omap.c
>>
>> Tony do you know about any issues with i2c-omap.c after
>> highspeed i2c was introduced ?
>>
>> This could be a regression, I remember seeing this on
>> some tests I was doing with twl4030 but they seemed
>> to vanish. Looks like I missed something. I'll try
>> to reproduce my bug with twl4030 and after that dig a
>> bit on i2c driver and i2c omap trms (ugh).
>>
>> Anyways, if you could enable all debugging in i2c and
>> get more info when it happens, that would be great ;-)
Hmm, yeah sounds like something is broken.. Anybody want to try to
narrow it down with git-bisect?
Tony
next prev parent reply other threads:[~2008-06-03 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 17:06 Booting 2.6.25 on the OMAP5912OSK Philip Balister
2008-06-01 21:04 ` Felipe Balbi
2008-06-03 14:54 ` Steve Poulsen
2008-06-03 16:49 ` Tony Lindgren [this message]
2008-06-03 17:32 ` Felipe Balbi
2008-06-01 21:18 ` Felipe Balbi
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=20080603164926.GC6992@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=me@felipebalbi.com \
--cc=philip@balister.org \
--cc=spoulsen@css-design.us \
/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