From: Kenneth Johansson <kenneth.johansson@inn.ericsson.se>
To: andrew may <acmay@acmay.homeip.net>
Cc: Linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>,
Armin Kuster <akuster@mvista.com>
Subject: Re: 405 I2C
Date: 22 May 2002 12:36:36 +0200 [thread overview]
Message-ID: <1022063796.7265.74.camel@swb11> (raw)
In-Reply-To: <20020521110050.B20012@ecam.san.rr.com>
On Tue, 2002-05-21 at 20:00, andrew may wrote:
> well i2c...read_byte_data is really a write of 1 byte followed by a read
> of 1 byte. The scan is just a read of 1 byte.
Yepp thats the difference.
>
> So you should be going through the combined xfer function.
Yes your right I missed that. It dose look like it's the first write
that never get an ack. This is the debug output from a one byte read
from address 0 from a non existing device.
kernel: iic_xfer: iic_xfer: Clearing status register
kernel: iic_xfer: Waiting for any pending transfers to complete
kernel: iic_xfer: Clearing master data buffer
kernel: iic_xfer: Loading slave address
kernel: iic_xfer: Call combined transaction
kernel: Beginning combined transaction
kernel: This one is a write
kernel: iic_sendbytes: Waiting for interrupt
kernel: iic_ibmocp_handler: in interrupt handler
kernel: iic_ibmocp_handler: status = 26
kernel: i2c-algo-ppc405.o: fail: only wrote -1 bytes.
It dose look like I actually have to learn how this is supposed to work
we seem to have more than one problem with the current code :(
--
Kenneth Johansson
Ericsson AB Tel: +46 8 404 71 83
Borgafjordsgatan 9 Fax: +46 8 404 72 72
164 80 Stockholm kenneth.johansson@etx.ericsson.se
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-22 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 15:30 405 I2C Kenneth Johansson
2002-05-21 15:59 ` andrew may
2002-05-21 16:16 ` Kenneth Johansson
2002-05-21 18:00 ` andrew may
2002-05-22 10:36 ` Kenneth Johansson [this message]
2002-05-22 19:53 ` andrew may
2002-05-21 16:07 ` Armin Kuster
2002-05-21 17:27 ` andrew may
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=1022063796.7265.74.camel@swb11 \
--to=kenneth.johansson@inn.ericsson.se \
--cc=acmay@acmay.homeip.net \
--cc=akuster@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).