From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from AM1EHSOBE002.bigfish.com (am1ehsobe002.messaging.microsoft.com [213.199.154.205]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.global.frontbridge.com", Issuer "Cybertrust SureServer Standard Validation CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 981F91007D1 for ; Tue, 14 Dec 2010 04:51:45 +1100 (EST) Received: from mail11-am1 (localhost.localdomain [127.0.0.1]) by mail11-am1-R.bigfish.com (Postfix) with ESMTP id E971EF30501 for ; Mon, 13 Dec 2010 17:51:38 +0000 (UTC) Received: from AM1EHSMHS002.bigfish.com (unknown [10.3.201.247]) by mail11-am1.bigfish.com (Postfix) with ESMTP id C02E52B0050 for ; Mon, 13 Dec 2010 17:51:38 +0000 (UTC) Received: from de01smr01.freescale.net (de01smr01.freescale.net [10.208.0.31]) by de01egw01.freescale.net (8.14.3/8.14.3) with ESMTP id oBDHruW8008204 for ; Mon, 13 Dec 2010 10:53:56 -0700 (MST) Received: from az33exm25.fsl.freescale.net (az33exm25.am.freescale.net [10.64.32.16]) by de01smr01.freescale.net (8.13.1/8.13.0) with ESMTP id oBDI8lcm010633 for ; Mon, 13 Dec 2010 12:08:47 -0600 (CST) Date: Mon, 13 Dec 2010 11:51:31 -0600 From: Scott Wood To: Joakim Tjernlund Subject: Re: MPC831x (and others?) NAND erase performance improvements Message-ID: <20101213115131.57050e1d@udp111988uds.am.freescale.net> In-Reply-To: References: <20101213113356.1596c6a6@udp111988uds.am.freescale.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Cc: Mark Mason , David Laight , linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 13 Dec 2010 18:41:32 +0100 Joakim Tjernlund wrote: > Scott Wood wrote on 2010/12/13 18:33:56: > > > > On Mon, 13 Dec 2010 11:32:00 +0100 > > Joakim Tjernlund wrote: > > > > > What if one has several NAND chips to build a big FS? Is the NAND > > > controller equipped to handle that? > > > > FCM can drive one NAND chip per eLBC chipselect, though possibly you > > could go beyond that with a board-logic chipselect mechanism. > > hmm, then I guess one would have to use one GPIO/IRQ per NAND chip? Couldn't you just tie together all the open-drain busy lines before you invert it? You'll only be driving one NAND chip at a time anyway; the others should not be asserting busy. -Scott