From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] omap24xx_i2c: i2c 16-bit write to pcf8575
Date: Mon, 10 Mar 2014 16:10:05 -0400 [thread overview]
Message-ID: <20140310201005.GA16805@bill-the-cat> (raw)
In-Reply-To: <CAPKmKfsL98zm3S7gBe6d5oSCnXEF3w3HqL_h9UXkOapoFwJr3w@mail.gmail.com>
On Wed, Mar 05, 2014 at 04:01:47PM -0500, Richard Retanubun wrote:
> Hello,
>
> My platform is a dra7xx_evm. My code baseline is denx master
>
> I am trying to write to the pcf8575 i2c gpio expander at address 0x21 (bit P4)
>
> I can read 16-bit okay in this version, but 16-bit writing is not working.
>
> // Display current values
> i2c md 21 0.0 2
> 0000: f7 eb ..
>
> // Set bit P4 to 1
> i2c mw 21 0.0 0xffeb 2
>
> // But it remains at 0xf7
> i2c md 21 0.0 2
> 0000: f7 eb ..
>
> When we put scopes on the i2c lines, it seems that the i2c mw
> transaction produces a longer i2c bus sequence that does not map to
> the [Start:Addr:W:A:P7-P0:A:P17-P10:A:Stop] that the pcf8575 device
> expects.
>
> Either I am invoking "i2c mw" incorrectly, or the oma24xx_i2c driver
> is not handling i2c 16-bit writes correctly yet.
>
> Any hints will be appreciated. Thanks for everyone's time
Have you tried doing it progmatically rather than via the command line?
You may indeed be running into something we don't support in "i2c mw",
if I skim the comments right.
--
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/20140310/80f87925/attachment.pgp>
prev parent reply other threads:[~2014-03-10 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 21:01 [U-Boot] omap24xx_i2c: i2c 16-bit write to pcf8575 Richard Retanubun
2014-03-10 20:10 ` Tom Rini [this message]
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=20140310201005.GA16805@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