From: "Sai Amruta" <amrutasai.p@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: MPC8313 NAND driver limitation
Date: Thu, 15 Jan 2009 21:19:37 +0530 [thread overview]
Message-ID: <dd2f3b320901150749u2312c2f3q909b05c3440f28bc@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
Hi,
System details:
Linux: 2.6.26-1
Processor: MPC8313
The current freescale NAND controller driver is using "command completion
(CC)" interrupt from FCM block to know the completion read and write
operations. After issuing NAND read/write operation and before FCM CC
interrupt, access to other Local Bus chip selects will failed. I have found
that it was a limitation with freescale FCM block.
To come across this limitation, i have implemented busy wait loop in driver.
I have spent lot of effort to find root cause, so that i would like to
publish my observations here which may help somebody who is using MPC8313.
--
--Amru
[-- Attachment #2: Type: text/html, Size: 692 bytes --]
reply other threads:[~2009-01-15 15:49 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=dd2f3b320901150749u2312c2f3q909b05c3440f28bc@mail.gmail.com \
--to=amrutasai.p@gmail.com \
--cc=linuxppc-dev@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 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).