From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pa0-x231.google.com ([2607:f8b0:400e:c03::231]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1a4Ebw-0000Ew-UA for linux-mtd@lists.infradead.org; Wed, 02 Dec 2015 21:06:50 +0000 Received: by pabfh17 with SMTP id fh17so52656299pab.0 for ; Wed, 02 Dec 2015 13:06:28 -0800 (PST) Date: Wed, 2 Dec 2015 13:06:25 -0800 From: Brian Norris To: Jonas Gorski Cc: Simon Arlott , Florian Fainelli , Kamal Dasu , Linux Kernel Mailing List , MTD Maling List , bcm-kernel-feedback-list , David Woodhouse , Boris Brezillon Subject: Re: [PATCH] mtd: brcmnand: Workaround false ECC uncorrectable errors Message-ID: <20151202210625.GR64635@google.com> References: <5659FF4A.7080203@simon.arlott.org.uk> <565F51D2.4010204@simon.arlott.org.uk> <20151202205415.GQ64635@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151202205415.GQ64635@google.com> List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Dec 02, 2015 at 12:54:15PM -0800, Brian Norris wrote: > BTW, I think Kamal had code to handle protecting bitflips in erased > pages code in the Broadcom STB Linux BSP. Perhaps he can port that to > upstream with nand_check_erased_ecc_chunk()? IIUC, that would probably > handle your case too, Simon, although it wouldn't be optimal for an > all-0xff check (i.e., bitflip_threshold == 0). I think this was for BCH only, actually. Hamming wasn't used as much on STB. So the above would only help part of this patch. I'm less sure of the behavior for the Hamming engine. Brian