From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from top.free-electrons.com ([176.31.233.9] helo=mail.free-electrons.com) by merlin.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1VoeGA-0002Zc-18 for linux-mtd@lists.infradead.org; Thu, 05 Dec 2013 19:06:51 +0000 Date: Thu, 5 Dec 2013 20:06:18 +0100 From: Thomas Petazzoni To: "Gupta, Pekon" Subject: Re: OMAP3 NAND ECC selection Message-ID: <20131205200618.19b33ee2@skate> In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73EA5222E@DBDE04.ent.ti.com> References: <52A04E75.3010609@corscience.de> <20131205171326.GA26766@atomide.com> <20131205182628.GF2345@localhost> <20980858CB6D3A4BAE95CA194937D5E73EA5222E@DBDE04.ent.ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Brian Norris , Peter Meerwald , Tony Lindgren , Enric Balletbo Serra , "linux-mtd@lists.infradead.org" , Ezequiel Garcia , Javier Martinez Canillas , "linux-omap@vger.kernel.org" , Andreas =?UTF-8?B?Qmllw59tYW5u?= List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Dear Gupta, Pekon, On Thu, 5 Dec 2013 19:02:22 +0000, Gupta, Pekon wrote: > >From: Ezequiel Garcia [mailto:ezequiel.garcia@free-electrons.com] > [...] > >AFAIK, there's no hardware limitation that would prevent us from setting > >a per-partition ECC, keep in mind this effort is not reduced to make > >devicetree accept ECC on the partitions. > > > I had some reservations in doing so.. (as mentioned in previous email also [2]) > I would rather like to understand long term benefits of such implementation. The long term benefits is simply to properly handle the hardware constraints. We have hardware platforms were parts of the NAND *MUST* use 1-bit ECC to be compatible with the ROM code, and other parts of the NAND *MUST* use stronger 4-bits or 8-bits ECC to comply with the NAND requirements. Isn't handling hardware constraints properly not a sufficient motivation for doing something? > Also, any constrain due to ROM code, or upgrading from remote can be > handled using various alternative approaches like [a] and [b]. And you're not realizing that these solutions are ugly and impractical? Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com