From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Valdis.Kletnieks@vt.edu
Cc: Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Hans de Goede <hdegoede@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 13/15] mtd: nand: samsung: retrieve ECC requirements from extended ID
Date: Mon, 30 May 2016 09:44:46 +0200 [thread overview]
Message-ID: <20160530094446.5edec3ac@bbrezillon> (raw)
In-Reply-To: <198040.1464567635@turing-police.cc.vt.edu>
Hi Valdis,
On Sun, 29 May 2016 20:20:35 -0400
Valdis.Kletnieks@vt.edu wrote:
> On Fri, 27 May 2016 14:54:59 +0200, Boris Brezillon said:
> > From: Hans de Goede <hdegoede@redhat.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....)
Actually, that was my first reaction [1], but the more I think about it
the more I realize it's a non-issue.
AFAICT, there's no full-id entries for Samsung NANDs in the nand_ids
table, so this either means there's no real users of Samsung MLCs or
NAND controller drivers connecting to those chips don't care about the
->ecc_{step_ds,strength_ds} fields.
I agree that the solution is not perfect, but I'd prefer seeing the
NAND detection code iteratively improved than rejecting everything
until we're 100% sure that all cases are correctly handled (which might
never happen since NAND vendors introduce new NAND ID scheme if they
need to).
BTW, do you have Samsung datasheets describing a different NAND ID
format, or is it purely hypothetical?
Regards,
Boris
[1]http://lists.infradead.org/pipermail/linux-mtd/2015-July/060582.html
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-30 7:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 12:54 [PATCH 00/15] mtd: nand: allow vendor specific detection/initialization Boris Brezillon
2016-05-27 12:54 ` [PATCH 01/15] mtd: nand: get rid of the mtd parameter in all auto-detection functions Boris Brezillon
2016-05-27 12:54 ` [PATCH 02/15] mtd: nand: store nand ID in struct nand_chip Boris Brezillon
2016-05-27 12:54 ` [PATCH 03/15] mtd: nand: get rid of busw parameter Boris Brezillon
2016-05-27 12:54 ` [PATCH 04/15] mtd: nand: rename nand_get_flash_type() into nand_detect() Boris Brezillon
2016-05-27 12:54 ` [PATCH 05/15] mtd: nand: add vendor specific initialization step Boris Brezillon
2016-05-27 12:54 ` [PATCH 06/15] mtd: nand: kill the MTD_NAND_IDS Kconfig option Boris Brezillon
2016-05-27 12:54 ` [PATCH 07/15] mtd: nand: move samsung specific initialization in nand_samsung.c Boris Brezillon
2016-05-27 12:54 ` [PATCH 08/15] mtd: nand: move hynix specific initialization in nand_hynix.c Boris Brezillon
2016-05-27 12:54 ` [PATCH 09/15] mtd: nand: move toshiba specific initialization in nand_toshiba.c Boris Brezillon
2016-05-27 12:54 ` [PATCH 10/15] mtd: nand: move micron specific initialization in nand_micron.c Boris Brezillon
2016-05-27 12:54 ` [PATCH 11/15] mtd: nand: move AMD/Spansion specific initialization in nand_amd.c Boris Brezillon
2016-05-27 12:54 ` [PATCH 12/15] mtd: nand: move Macronix specific initialization in nand_macronix.c Boris Brezillon
2016-05-27 12:54 ` [PATCH 13/15] mtd: nand: samsung: retrieve ECC requirements from extended ID Boris Brezillon
2016-05-30 0:20 ` Valdis.Kletnieks
2016-05-30 7:44 ` Boris Brezillon [this message]
2016-05-30 20:56 ` Valdis.Kletnieks
2016-05-30 22:28 ` Boris Brezillon
2016-05-30 22:32 ` Boris Brezillon
2016-05-27 12:55 ` [PATCH 14/15] mtd: nand: hynix: rework NAND ID decoding to extract more information Boris Brezillon
2016-05-27 12:55 ` [PATCH 15/15] mtd: nand: hynix: add read-retry support for 1x nm MLC NANDs Boris Brezillon
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=20160530094446.5edec3ac@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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;
as well as URLs for NNTP newsgroup(s).