From: andrew may <acmay@acmay.homeip.net>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: [PATCH]IBM OCP I2C
Date: Mon, 29 Apr 2002 14:40:53 -0700 [thread overview]
Message-ID: <20020429144053.B6106@ecam.san.rr.com> (raw)
This is incremental to the other patches I posted. It gets the
iic_xfer that is based of the ppcboot code working. The return
values are still not correct but the data is transfered ok for
what I have tested. I do not try to do a Repeated Start for
anything yet either.
If anyone has any comments or more test conditions I would like
to hear them.
I pulled some defines from the PPCBoot code and I am not sure the
correct header file for them.
I would like to dump the iic_outb/inb as well. In the iic_xfer I
use readb/writeb directly without problems.
I put this comment in there about the driver. Does any see anything
wrong with this?
/*
* Limits of the IBM OCP I2C driver.
* There is no way to do lenght 0 transfers since iic->cntl TCT==00 means 1 byte
* We can not handle I2C_M_NOSTART since there is no way to put just one bit
* on the bus after a NA.
* We can not handle I2C_M_REV_DIR_ADDR since the Rd/Wr bit is not
* set directly in the address register and the controller uses the
* Rd/Wr bit in the CNTL reg to know what to do.
*
* If you need to get around any of these I suggest you setup i2c-adap-ibm...
* to use the algo-bit and provide functions to use the DirectControl Reg of
* the IBM OCP hardware.
*/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-04-29 21:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 21:40 andrew may [this message]
[not found] ` <3CCDE113.5000700@pacbell.net>
2002-04-30 0:05 ` [PATCH]IBM OCP I2C andrew may
-- strict thread matches above, loose matches on Subject: below --
2002-05-07 18:33 andrew may
2002-05-07 19:54 ` andrew may
2002-04-24 3:01 [PATCH] IBM ocp I2C andrew may
2002-04-24 3:01 ` andrew may
2002-04-24 4:36 ` Armin
2002-04-24 15:18 ` andrew may
2002-04-24 18:26 ` andrew may
2002-04-24 18:45 ` Armin
2002-05-01 17:05 ` Armin
2002-04-26 20:48 ` Armin
2002-04-27 3:35 ` andrew may
2002-04-28 4:09 ` Armin
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=20020429144053.B6106@ecam.san.rr.com \
--to=acmay@acmay.homeip.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.