From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] OMAP: I2C: New read, write and probe functions
Date: Thu, 30 May 2013 13:07:09 -0400 [thread overview]
Message-ID: <20130530170709.GP11917@bill-the-cat> (raw)
In-Reply-To: <20130530143742.GM11917@bill-the-cat>
On Thu, May 30, 2013 at 10:37:42AM -0400, Tom Rini wrote:
> On Thu, May 30, 2013 at 01:24:42AM +0300, Lubomir Popov wrote:
>
> > Tested on OMAP4/5 only, but should work on older OMAPs and
> > derivatives as well.
> >
> > - Rewritten i2c_read to operate correctly with all types of chips
> > (old function could not read consistent data from some I2C slaves).
> > - Optimised i2c_write.
> > - New i2c_probe, optionally selectable via CONFIG_I2C_PROBE_WRITE,
> > performs write access vs read. The old probe could hang the system
> > under certain conditions (e.g. unconfigured pads).
> > - The read/write/probe functions try to identify unconfigured bus.
> > - Status functions now read irqstatus_raw as per TRM guidelines
> > (except for OMAP243X and OMAP34XX).
> > - Driver now supports up to I2C5 (OMAP5).
> >
> > Signed-off-by: Lubomir Popov <lpopov@mm-sol.com>
>
> With CONFIG_I2C_PROBE_WRITE set:
> Tested-by: Tom Rini <trini@ti.com> on Beagleboard / Beagleboard xM
But, crap, breaks am335x_evm (and probably beaglebones, etc). I'll
dig into this more to see if I can spot something obvious tomorrow.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130530/01008034/attachment.pgp>
next prev parent reply other threads:[~2013-05-30 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 22:24 [U-Boot] [PATCH v3] OMAP: I2C: New read, write and probe functions Lubomir Popov
2013-05-30 14:37 ` Tom Rini
2013-05-30 14:51 ` Lubomir Popov
2013-05-30 15:01 ` Tom Rini
2013-05-30 17:07 ` Tom Rini [this message]
2013-05-30 18:41 ` Lubomir Popov
2013-05-30 19:34 ` Lubomir Popov
2013-05-31 10:39 ` Lubomir Popov
2013-05-31 10:58 ` Lubomir Popov
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=20130530170709.GP11917@bill-the-cat \
--to=trini@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox