From: Marcus Mikolaiczyk <m.mikolaiczyk@rac.de>
To: linux-mtd@lists.infradead.org
Subject: NAND connected with address lines based example
Date: Thu, 31 Mar 2005 11:07:47 +0200 [thread overview]
Message-ID: <424BBDE3.4000506@rac.de> (raw)
Dear list users,
I got a system where a Samsung NAND ist connect via Adresslines (A0 ->
CLE, A1 -> ALE) using a chipselect from the processor. I looked through
the guide "MTD NAND Driver Programming Interface" and the sources to
adapt an existing driver. Now I stuck with a problem concerning the
board_hwcontrol function.
It's alwas there that CLE/ALE have a set and a clear command. But in my
setup the CLE/ALE setting is made through the access of the
addresslines. See the table:
A1(ALE) A0(CLE) Beispieladresse Funktion
-------------------------------------------------------------------------------
1 0 0 0xA8000000 read/write access on mem
2 0 1 0xA8000001 Command
3 1 0 0xA8000002 Addresssetting
4 1 1 0xA8000003 not valid
The base is A8000000 for example.
Now writing a Byte to 0xA8000001 (a NAND command) automatically sets ALE
=0 and CLE=1
Writing the addressparts is done through writing the 1st databyte Col1
to address 0xA8000002 and so on.
Concerning now the function board_hwcontrol there is the
...
switch(cmd) {
case NAND_CTL_SETCLE: /* Write to addr 0xA8000001 */;break;
case NAND_CTL_CLRCLE: /* do nothing */;break;
case NAND_CTL_SETALE: /* Write to addr 0xA8000002 */;break;
case NAND_CTL_CLRALE: /* do nothing */;break;
}
...
Am I right when these commands have to be empty in this case?
Where do I tell the system to use the address 0xA8000001 for commands
and 0xA8000002 for addresses?
Kind Regards
Marcus
next reply other threads:[~2005-03-31 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 9:07 Marcus Mikolaiczyk [this message]
2005-03-31 9:48 ` NAND connected with address lines based example William J Beksi
2005-03-31 9:58 ` Marcus Mikolaiczyk
2005-03-31 9:54 ` Pathompong Puengrostham
2005-03-31 10:53 ` Thomas Gleixner
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=424BBDE3.4000506@rac.de \
--to=m.mikolaiczyk@rac.de \
--cc=linux-mtd@lists.infradead.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