All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	linux-mtd@lists.infradead.org,
	Boris Brezillon <boris.brezillon@free-electrons.com>,
	Richard Weinberger <richard@nod.at>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 0/3] mtd: nand: standardize ECC maximization
Date: Fri, 16 Sep 2016 15:08:49 +0200	[thread overview]
Message-ID: <20160916150849.4a3ca0bb@bbrezillon> (raw)
In-Reply-To: <1465398264-8202-1-git-send-email-boris.brezillon@free-electrons.com>

On Wed,  8 Jun 2016 17:04:21 +0200
Boris Brezillon <boris.brezillon@free-electrons.com> wrote:

> Hello,
> 
> Sorry for the noise, but I forgot to add DT maintainers in Cc.
> 
> This series aims at standardizing a feature already supported by
> some NAND controller drivers: setting the maximum ECC strength
> based on the OOB area size instead of using the ECC strength/step_size
> information retrieved from the DT or NAND detection code.
> 
> This is particularly useful when the NAND device is used in by a
> FS/wear-leveling layer that is not using the OOB area at all (this is
> the case of UBI).
> 
> Note that drivers already implementing this kind of logic are not
> converted to the new approach (because of backward compatibility
> concern), but new drivers or drivers that do not already implement
> this 'ECC maximization' logic are encouraged to do it.

Applied.

> 
> Regards,
> 
> Boris
> 
> Boris Brezillon (3):
>   mtd: nand: Add an option to maximize the ECC strength
>   mtd: nand: Support maximizing ECC when using software BCH
>   mtd: nand: sunxi: Support ECC maximization
> 
>  Documentation/devicetree/bindings/mtd/nand.txt |  9 ++++++++
>  drivers/mtd/nand/nand_base.c                   | 23 ++++++++++++++++++++
>  drivers/mtd/nand/sunxi_nand.c                  | 29 ++++++++++++++++++++++++++
>  include/linux/mtd/nand.h                       |  1 +
>  4 files changed, 62 insertions(+)
> 

WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	Brian Norris
	<computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Boris Brezillon
	<boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
	Richard Weinberger <richard-/L3Ra7n9ekc@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	Ian Campbell
	<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
	Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RESEND PATCH 0/3] mtd: nand: standardize ECC maximization
Date: Fri, 16 Sep 2016 15:08:49 +0200	[thread overview]
Message-ID: <20160916150849.4a3ca0bb@bbrezillon> (raw)
In-Reply-To: <1465398264-8202-1-git-send-email-boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>

On Wed,  8 Jun 2016 17:04:21 +0200
Boris Brezillon <boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> wrote:

> Hello,
> 
> Sorry for the noise, but I forgot to add DT maintainers in Cc.
> 
> This series aims at standardizing a feature already supported by
> some NAND controller drivers: setting the maximum ECC strength
> based on the OOB area size instead of using the ECC strength/step_size
> information retrieved from the DT or NAND detection code.
> 
> This is particularly useful when the NAND device is used in by a
> FS/wear-leveling layer that is not using the OOB area at all (this is
> the case of UBI).
> 
> Note that drivers already implementing this kind of logic are not
> converted to the new approach (because of backward compatibility
> concern), but new drivers or drivers that do not already implement
> this 'ECC maximization' logic are encouraged to do it.

Applied.

> 
> Regards,
> 
> Boris
> 
> Boris Brezillon (3):
>   mtd: nand: Add an option to maximize the ECC strength
>   mtd: nand: Support maximizing ECC when using software BCH
>   mtd: nand: sunxi: Support ECC maximization
> 
>  Documentation/devicetree/bindings/mtd/nand.txt |  9 ++++++++
>  drivers/mtd/nand/nand_base.c                   | 23 ++++++++++++++++++++
>  drivers/mtd/nand/sunxi_nand.c                  | 29 ++++++++++++++++++++++++++
>  include/linux/mtd/nand.h                       |  1 +
>  4 files changed, 62 insertions(+)
> 

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-09-16 13:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 15:04 [RESEND PATCH 0/3] mtd: nand: standardize ECC maximization Boris Brezillon
2016-06-08 15:04 ` Boris Brezillon
2016-06-08 15:04 ` [RESEND PATCH 1/3] mtd: nand: Add an option to maximize the ECC strength Boris Brezillon
2016-06-10 14:04   ` Rob Herring
2016-06-10 14:04     ` Rob Herring
2016-06-08 15:04 ` [RESEND PATCH 2/3] mtd: nand: Support maximizing ECC when using software BCH Boris Brezillon
2016-06-08 15:04   ` Boris Brezillon
2016-06-08 15:04 ` [RESEND PATCH 3/3] mtd: nand: sunxi: Support ECC maximization Boris Brezillon
2016-06-08 15:04   ` Boris Brezillon
2016-09-16 13:08 ` Boris Brezillon [this message]
2016-09-16 13:08   ` [RESEND PATCH 0/3] mtd: nand: standardize " 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=20160916150849.4a3ca0bb@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=richard@nod.at \
    --cc=robh+dt@kernel.org \
    /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.