public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: Huang Shijie <b32955@freescale.com>,
	"dwmw2@infradead.org" <dwmw2@infradead.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"dedekind1@gmail.com" <dedekind1@gmail.com>
Subject: Re: [PATCH v3 3/6] mtd: set the ecc step size for master/slave mtd_info
Date: Sat, 17 Aug 2013 11:58:04 -0700	[thread overview]
Message-ID: <20130817185804.GA11210@norris.computersforpeace.net> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73E9F4173@DBDE04.ent.ti.com>

On Tue, Aug 13, 2013 at 04:29:46AM +0000, Gupta, Pekon wrote:
> > On Mon, Aug 12, 2013 at 05:44:57PM +0800, Huang Shijie wrote:
> > > 于 2013年08月12日 17:24, Gupta, Pekon 写道:
> > > >In addition, chip->ecc.bytes should also be helpful for userspace
> > > >utility to determine how much bytes to reserve in spare-area for ECC.
> > > >So exposing that as sysfs entry is also good.
> > > >
> > > I do not need the chip->ecc.bytes. :)
> > > For me, export the chip->ecc.size is enough.
> > 
> > A better argument against this is that ecc.bytes does not necessarily
> > have utility across many types of NAND drivers by itself, since ECC
> > layouts differ. And at that point, we're trying to duplicate the
> > behavior of ioctl(ECCGETLAYOUT) (which notably has run out of room and
> > isn't 100% informative anymore).
> > 
> > > So you can submit a patch if you need this field.
> > 
> > Yes, if you have good reason for exporting it, send a patch and a good
> > argument. And it would need to explain why we can't just use
> > ECCGETLAYOUT.
> > 
> Thanks for the info..
> I wasn't fully aware of ioctl(ECCGETLAYOUT), I'll explore it further.

Just to be clear, there may be good reason to duplicate features between
ECCGETLAYOUT and sysfs (for instance, because we've grown beyond the
size of ECCGETLAYOUT, or simply so that modern, useful parameters are
all in one place).

> Also, is there any documentation or URL explaining all ioctl for MTD?

That's a good question. As far as I know, the best reference is
include/uapi/mtd/mtd-abi.h. There's some old documentation for UBI
ioctls on:

  http://linux-mtd.infradead.org/
  http://linux-mtd.infradead.org/doc/ubidesign/ubidesign.pdf

I don't really see anything like that for MTD. But you are free to write
up such documentation! You can send patches against mtd-www.git:

  http://linux-mtd.infradead.org/faq/general.html#L_mtdwww

Or perhaps we could use something within the kernel Documentation/mtd/
directory? I would consult Artem/David for that one.

Brian

  parent reply	other threads:[~2013-08-17 18:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12  5:24 [PATCH v3 0/6] Export the ECC step size to user applications Huang Shijie
2013-08-12  5:24 ` [PATCH v3 1/6] mtd: add a new field to mtd_info{} Huang Shijie
2013-08-12  5:24 ` [PATCH v3 2/6] mtd: add a new sys node to show the ecc step size Huang Shijie
2013-08-12  5:24 ` [PATCH v3 3/6] mtd: set the ecc step size for master/slave mtd_info Huang Shijie
2013-08-12  7:00   ` Gupta, Pekon
2013-08-12  8:28     ` Huang Shijie
2013-08-12  9:24       ` Gupta, Pekon
2013-08-12  9:44         ` Huang Shijie
2013-08-13  0:25           ` Brian Norris
2013-08-13  4:29             ` Gupta, Pekon
2013-08-13  6:14               ` Huang Shijie
2013-08-17 18:58               ` Brian Norris [this message]
2013-08-12  5:24 ` [PATCH v3 4/6] mtd: set ONFI nand's default hooks in nand_set_defaults() Huang Shijie
2013-08-12  5:24 ` [PATCH v3 5/6] mtd: gpmi: remove the nand_scan() Huang Shijie
2013-08-12  5:24 ` [PATCH v3 6/6] mtd: update the ABI document about the ecc step Huang Shijie

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=20130817185804.GA11210@norris.computersforpeace.net \
    --to=computersforpeace@gmail.com \
    --cc=b32955@freescale.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pekon@ti.com \
    /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