mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Jan Lübbe" <jlu@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] i2c-omap: Update driver
Date: Wed, 02 Oct 2013 21:45:34 +0200	[thread overview]
Message-ID: <1380743134.7042.4.camel@polaris.local> (raw)
In-Reply-To: <20130930081642.GA30088@pengutronix.de>

On Mon, 2013-09-30 at 10:16 +0200, Sascha Hauer wrote: 
> On Thu, Sep 26, 2013 at 01:40:24PM +0200, Jan Weitzel wrote:
> > The driver didn't work well with at24 driver. NACKS are lost.
> > Errors are lost in isr due to the local variable err. Also we didn't wait for
> > bus free in omap_i2c_xfer_msg.
> > 
> > Fix issues and get other improvements from linux kernel
> > 
> > Tested on OMAP4 and AM335x
> > 
> > Signed-off-by: Jan Weitzel <j.weitzel@phytec.de>
> 
> Applied, thanks

When booting my BeagleBone with this, I see:
i2c-omap i2c-am33xx0: bus 0 rev84148224.11 at 100 kHz

The revision entry looks strange, but the at24 EEPROM continues to be
accessible. I've not yet looked at it in detail. Jan, do you have an
idea?

Regards,
Jan


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-10-02 19:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26 11:40 Jan Weitzel
2013-09-30  8:16 ` Sascha Hauer
2013-10-02 19:45   ` Jan Lübbe [this message]
2013-10-07 13:18     ` [PATCH] i2c-omap: fix reported revison Jan Weitzel
2013-10-14  9:15       ` Sascha Hauer

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=1380743134.7042.4.camel@polaris.local \
    --to=jlu@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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