From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>
Subject: Re: [PATCH] mtd: nand: samsung: Disable subpage writes on E-die NAND
Date: Tue, 9 Jan 2018 09:46:21 +0100 [thread overview]
Message-ID: <20180109094621.23a5e368@bbrezillon> (raw)
In-Reply-To: <20180108234837.GA15913@lenoch>
On Tue, 9 Jan 2018 00:48:37 +0100
Ladislav Michl <ladis@linux-mips.org> wrote:
> Samsung E-die SLC NAND manufactured using 21nm process supports only
I would add the chip name here (K9F1G08U0E).
> 1 partial program cycle, so disable subpage writes for it.
Which means it does not support partial page programming, so how about
rewording it like that:
Samsung E-die SLC NAND manufactured using 21nm process (K9F1G08U0E)
does not support partial page programming, so disable subpage writes
for it.
> Manufacturing process is stored in lowest two bits of 5th ID byte.
>
> Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> ---
> Note: Patch generated and tested against next-20180108 on at91sam9g20
> board with K9F1G08U0E.
Just out of curiosity, what are the symptoms when you don't have this
flag set?
>
> drivers/mtd/nand/nand_samsung.c | 15 +++++++++++----
> 1 file changed, 11 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mtd/nand/nand_samsung.c b/drivers/mtd/nand/nand_samsung.c
> index f6b0a63a068c..9400b4a84243 100644
> --- a/drivers/mtd/nand/nand_samsung.c
> +++ b/drivers/mtd/nand/nand_samsung.c
> @@ -92,10 +92,17 @@ static void samsung_nand_decode_id(struct nand_chip *chip)
> } else {
> nand_decode_ext_id(chip);
>
> - /* Datasheet values for SLC Samsung K9F4G08U0D-S[I|C]B0(T00) */
> - if (nand_is_slc(chip) && chip->id.data[1] == 0xDC) {
> - chip->ecc_step_ds = 512;
> - chip->ecc_strength_ds = 1;
> + if (nand_is_slc(chip)) {
> + /* K9F4G08U0D-S[I|C]B0(T00) */
> + if (chip->id.data[1] == 0xDC) {
> + chip->ecc_step_ds = 512;
> + chip->ecc_strength_ds = 1;
> + }
> +
> + /* 21nm chips do not support partial page write */
> + if (chip->id.len > 4 &&
> + (chip->id.data[4] & GENMASK(1,0)) == 0x1)
NAND vendors tend to change their ID decoding scheme a lot, so maybe we
should be more restrictive here: replace "chip->id.len > 4" by
"chip->id.len == 5" and restrict it to chip->id.data[1] == 0xF1.
> + chip->options |= NAND_NO_SUBPAGE_WRITE;
> }
> }
> }
next prev parent reply other threads:[~2018-01-09 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 23:48 [PATCH] mtd: nand: samsung: Disable subpage writes on E-die NAND Ladislav Michl
2018-01-09 8:46 ` Boris Brezillon [this message]
2018-01-09 9:08 ` Ladislav Michl
2018-01-09 9:27 ` Boris Brezillon
2018-01-09 9:58 ` Ladislav Michl
2018-01-09 10:06 ` Boris Brezillon
2018-01-09 11:19 ` Ladislav Michl
2018-01-09 13:07 ` 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=20180109094621.23a5e368@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=ladis@linux-mips.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--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