[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <198040.1464567635@turing-police.cc.vt.edu>
Date: Sun, 29 May 2016 20:20:35 -0400
From: Valdis.Kletnieks@...edu
To: Boris Brezillon <boris.brezillon@...e-electrons.com>
Cc: Richard Weinberger <richard@....at>, linux-mtd@...ts.infradead.org,
David Woodhouse <dwmw2@...radead.org>,
Brian Norris <computersforpeace@...il.com>,
Hans de Goede <hdegoede@...hat.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 13/15] mtd: nand: samsung: retrieve ECC requirements from extended ID
On Fri, 27 May 2016 14:54:59 +0200, Boris Brezillon said:
> From: Hans de Goede <hdegoede@...hat.com>
>
> On some nand controllers with hw-ecc the controller code wants to know
> the ecc strength and size and having these as 0, 0 is not accepted.
>
> Specifying these in devicetree is possible but undesirable as the nand
> may be different in different production runs of the same board, so it
> is better to get this info from the nand id where possible.
>
> This commit adds code to read the ecc strength and size from the nand
> for Samsung extended-id nands. This code is based on the info for the 5th
> id byte in the datasheets for the following Samsung nands: K9GAG08U0E,
> K9GAG08U0F, K9GAG08X0D, K9GBG08U0A, K9GBG08U0B. These all use these bits
> in the exact same way.
Is this correct for all Samsung nand devices supported by this driver?
(If this driver only covers those 5 specific parts, it's OK. If there's
others, more research is needed....)
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists