All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ankur Maheshwari <ankur_maheshwari@procsys.com>
To: linuxppc-embedded@ozlabs.org
Subject: [Fwd: mpc8xx, i2c read DB busy issue]
Date: Tue, 30 Oct 2007 11:25:15 +0530	[thread overview]
Message-ID: <4726C743.9070809@procsys.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: mpc8xx, i2c read DB busy issue.eml --]
[-- Type: message/rfc822, Size: 1421 bytes --]

From: Ankur Maheshwari <ankur_maheshwari@procsys.com>
To: linuxppc-embedded@ozlabs.org
Subject: mpc8xx, i2c read DB busy issue
Date: Fri, 26 Oct 2007 15:00:31 +0530
Message-ID: <4721B3B7.8070602@procsys.com>

Hi all,

I am trying to use mpc860 as i2c-SLAVE. Kernel, I am using is 
Linux-2.4.4, which I can't change due to some reasons.

I am able to do I2C read/write operations on mpc8xx-i2c slave only after 
re-insmoding my driver module (i2c-algo-8xx.c, and adapter layer drive, 
code I took form i2c-rpx/r360.c ).

The issue I am facing is when I insmod i2c-driver on fresh Linux boot, 
any i2c-mpc860 as slave read/write operation gives me busy status (which 
is for Rx BD not available) in Controller's i2c Event Registers. When I 
get busy status I have to do force_close() and re-init of bd, then only 
busy status goes off.

I tried calling cpm_iic_init(); twice while __init but with no change in 
busy status.

After some initial try, i2c slave write works but i2c read gives no data 
to the master. After re-insmoding driver, read/write works with some 
times (1 out of 15 times) i2c-read failing.

But still I can't understand why busy is coming....

Any help or suggestions are highly appreciated.

thanks,
Ankur Maheshwari

 


                 reply	other threads:[~2007-10-30  5:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4726C743.9070809@procsys.com \
    --to=ankur_maheshwari@procsys.com \
    --cc=linuxppc-embedded@ozlabs.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.