linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Armin <akuster@pacbell.net>
To: acurtis@onz.com
Cc: Kenneth Johansson <kenneth.johansson@etx.ericsson.se>,
	linuxppc-embedded@lists.linuxppc.org, kuster@pacbell.net,
	acmay@acmay.homeip.ne
Subject: Re: IBM ocp I2C circular dependency
Date: Tue, 07 May 2002 08:19:40 -0700	[thread overview]
Message-ID: <3CD7F08C.3050906@pacbell.net> (raw)
In-Reply-To: NCBBIINEHIPFGJPLBEIFMEJMDGAA.acurtis@onz.com


Allen Curtis wrote:
> I can not speak toward the modularization issue but if the i2c is anything
> like the old 8260 version, change the interruptible_sleep_on() to
> interruptible_sleep_on_timeout(). IMHO this is the easiest fix.
>
>
> i2c-adap-ibm_ocp.c uses
> 	i2c_iic_add_bus and i2c_iic_del_bus from i2c-algo-ibm_ocp.c
>
> i2c-algo-ibm_ocp.c uses
> 	iic_ibmocp_waitforpin from i2c-adap-ibm_ocp.c
>
> This makes it impossible to build as a module. I'am not shure how you want
> to
> solv this.
>
> Also I found a problem with the code when I access a i2c memory from
> userspace and no chip is present at that address. After that it's not
> possible to access anything else on the I2C bus. Works OK as long as I use
> addresses that have a device that answers (I think).
>

Thanks,  I like easy

armin


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2002-05-07 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 13:02 IBM ocp I2C circular dependency Kenneth Johansson
2002-05-07 14:04 ` Allen Curtis
2002-05-07 15:05   ` Kenneth Johansson
2002-05-07 15:10     ` Allen Curtis
2002-05-07 15:19   ` Armin [this message]
2002-05-07 16:16 ` andrew may
2002-05-07 16:42   ` Kenneth Johansson

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=3CD7F08C.3050906@pacbell.net \
    --to=akuster@pacbell.net \
    --cc=acmay@acmay.homeip.ne \
    --cc=acurtis@onz.com \
    --cc=kenneth.johansson@etx.ericsson.se \
    --cc=kuster@pacbell.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 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).