public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: Quad Die NAND Chip with 16Gb
Date: Fri, 31 Aug 2007 17:04:43 +0200	[thread overview]
Message-ID: <20070831150443.GA10808@anita.doom> (raw)

Hi Folks!

Actually I am trying to pimp our NAND driver which already supports
Micron MT29Fxx Chips very well. The last incarnation of these has quad
die and two CE lines, namely CE1 and CE2.

The driver accesses the first two dies by speaking to a CPLD an whenever
Bit0 is accessed it asserts CE1 of NAND, when Bit1 is accessed it
asserts CE2.

#define CPLD_NAND_CE1  0x01 /* Chip Enable1 to NAND Flash */
#define CPLD_NAND_CE2  0x02 /* Chip Enable2 to NAND Flash */
#define CPLD_NAND_ALE  0x04 /* Address Latch Enable to NAND Flash */
#define CPLD_NAND_CLE  0x08 /* Command Latch Enable to NAND Flash */
#define CPLD_NAND_RYBY 0x20 /* RY/BY# input from NAND Flash */

My question is now (as I am not familiar with the driver), how I
implement this doubling of capacitiy into the driver. Where can I best
do this? 
I mean where is the best point of code to kind of double the structures?
has anybody done something like this before?

The driver is at http://www.ludenkalle.de/nand/scb9xxx.c and is adapted
from the other nand drivers there. 

May be somebody has some advices for me :-/

Kind regards, Konsti

-- 
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E  A080 1E69 3FDA EF62 FCEF

             reply	other threads:[~2007-08-31 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 15:04 Konstantin Kletschke [this message]
2007-08-31 15:31 ` Quad Die NAND Chip with 16Gb Konstantin Kletschke
2007-09-04 10:32   ` Konstantin Kletschke

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=20070831150443.GA10808@anita.doom \
    --to=lists@ku-gbr.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