From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: bus access for NAND parts
Date: Tue, 04 Nov 2008 11:11:23 +0100 [thread overview]
Message-ID: <49101FCB.8010704@parrot.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0810302323100.15815@lnxricardw.se.axis.com>
Ricard Wanderlof a écrit :
> On Thu, 30 Oct 2008, Cliff Brake wrote:
>
>> Correction -- above should say: "It seems that most devices simply use a
>> _GPIO_ for CE". The chip select is set low in software, and then
>> multiple bus cycles are run to execute the address and data phases of
>> the NAND operation. So what keeps another process from interrupting
>> this and running a bus cycle while the GPIO for NAND CE is still low
>> -- which would toggle the strobes to the NAND cs.
>
> I don't know in general, but in several systems that have multiple buses,
> the NAND flash can be the only device on a particular bus, so conflicts
> with other devices are not an issue in those cases. Otherwise, it would be
> as you say, I agree.
>
The s3c2412 where the nand bus is shared with SDRAM. nCE is like a gpio
set by software. But it isn't a problem because the nand flash doesn't
care about other bus cycle if nWE/nRE is in high state (see nand
datasheets).
So the arbitration is done with nWE/nRE line and without nCE.
Matthieu
prev parent reply other threads:[~2008-11-04 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 11:54 bus access for NAND parts Cliff Brake
2008-10-30 22:08 ` Cliff Brake
2008-10-30 22:24 ` Ricard Wanderlof
2008-11-04 10:11 ` Matthieu CASTET [this message]
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=49101FCB.8010704@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.com \
/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.