From: Brian Norris <computersforpeace@gmail.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] mtd: introduce the mtd_pairing_scheme concept
Date: Sun, 12 Jun 2016 23:22:29 -0700 [thread overview]
Message-ID: <20160613062229.GA115118@google.com> (raw)
In-Reply-To: <20160613055532.GB107340@google.com>
On Sun, Jun 12, 2016 at 10:55:32PM -0700, Brian Norris wrote:
> On Sat, Jun 11, 2016 at 08:54:08AM +0200, Boris Brezillon wrote:
> > On Fri, 10 Jun 2016 19:17:15 -0700
> > Brian Norris <computersforpeace@gmail.com> wrote:
[...]
> > > Also, the "pair" term (and examples you use) seem to imply 2-cell MLC,
> > > whereas I believe you're trying to handle TLC too. I don't know if we
> > > should drop the "pair" term, or just explain it better.
> >
> > I clearly have some problems with the words I've chosen, but those terms
> > were extracted from NAND datasheets (group and pair), and I think
> > keeping the same wording help people converting datasheet specs into
> > pairing scheme implementation.
> >
> > Any suggestions to replace those 2 words?
>
> I'm not sure we should replace the words (esp. if those are used by
> multiple vendors). [...]
I see that George highlighted a Micron datasheet in other parts of this
thread, and I noticed it uses the term "shared page." That explains why
I couldn't find the word "pair" in my quick search of Micron datasheets!
So I guess "shared page" would be a nomination, though I'm certainly not
forcing it, if you think pair is better.
Brian
next prev parent reply other threads:[~2016-06-13 6:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 10:01 [PATCH 0/4] mtd: add support for pairing scheme description Boris Brezillon
2016-04-25 10:01 ` [PATCH 1/4] mtd: introduce the mtd_pairing_scheme concept Boris Brezillon
2016-06-11 2:17 ` Brian Norris
2016-06-11 6:54 ` Boris Brezillon
2016-06-13 5:55 ` Brian Norris
2016-06-13 6:22 ` Brian Norris [this message]
2016-06-13 6:37 ` Boris Brezillon
2016-04-25 10:01 ` [PATCH 2/4] mtd: nand: implement two pairing scheme Boris Brezillon
2016-04-25 10:01 ` [PATCH 3/4] mtd: nand: add a pairing field to nand_flash_dev Boris Brezillon
2016-04-25 10:01 ` [PATCH 4/4] mtd: nand: H27UCG8T2ATR: point to the correct pairing scheme implementation Boris Brezillon
2016-04-28 8:04 ` [PATCH 0/4] mtd: add support for pairing scheme description Richard Weinberger
2016-06-11 2:16 ` Brian Norris
2016-06-11 6:45 ` Boris Brezillon
2016-06-13 5:54 ` Brian Norris
2016-06-13 6:33 ` 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=20160613062229.GA115118@google.com \
--to=computersforpeace@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=dwmw2@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.