From: Simon Guinot <simon.guinot@sequanux.org>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: Lior Amsalem <alior@marvell.com>,
devicetree@vger.kernel.org, Tawfik Bayouk <tawfik@marvell.com>,
Seif Mazareeb <seif@marvell.com>, Willy Tarreau <w@1wt.eu>,
Simon Guinot <sguinot@lacie.com>,
linux-mtd@lists.infradead.org,
Gregory Clement <gregory.clement@free-electrons.com>,
Brian Norris <computersforpeace@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Subject: Re: [PATCH v2 0/4] Allow to specify an ECC scheme through DT
Date: Tue, 1 Apr 2014 12:04:17 +0200 [thread overview]
Message-ID: <20140401100417.GI27979@kw.sim.vm.gnt> (raw)
In-Reply-To: <1395401690-25221-1-git-send-email-ezequiel.garcia@free-electrons.com>
[-- Attachment #1: Type: text/plain, Size: 2457 bytes --]
On Fri, Mar 21, 2014 at 08:34:46AM -0300, Ezequiel Garcia wrote:
> Now that we have agreed on the ECC devicetree binding, here's a patchset
> that makes pxa3xx-nand driver use it.
>
> This work is required on platforms where the flash device reports a required
> ECC strength, but that are capable of handling a stronger one. Simon Guinot
> reported a situation where the vendor provided a bootloader configured with
> a stronger than required ECC scheme. Without this patches, such a situation
> would require a hack to make the driver use a specific ECC scheme.
>
> (Simon: it would be great if you can confirm this allows you to remove any hacks).
Hi Ezequiel,
I confirm this allows me to configure the ECC strength and step size
from DT.
Tested-by: Simon Guinot <simon.guinot@sequanux.org>
Thanks.
Simon
>
> The first two patches clean the pxa_ecc_init(), preparing for the real
> work to be done.
>
> The third patch makes use of the ECC strength and ECC step size parameters.
> To ensure full backward compatibility, the patch *tries* to use DT-specified
> ECC parameters, falling back to using the ONFI-specified settings if the
> former are missing.
>
> Also, we use the ONFI 'datasheet' ECC strength requirement, to ensure the
> DT-specified ECC strength is strong enough to meet the requirement.
>
> Finally, the last patch updates the documentation binding, with the supported
> ECC parameters.
>
> Tested on Marvell's Armada 370 RD and also Compulab's CM-X300 (PXA3xx SoC),
> which is a non-DT platform. Based on today's l2-mtd.git.
>
> Changes from v1:
>
> * Fixed typo in ECC strength normalization calculus.
>
> Ezequiel Garcia (4):
> mtd: nand: pxa3xx: Normalize ECC strength for ECC scheme selection
> mtd: nand: pxa3xx: Clean pxa_ecc_init() error handling
> mtd: nand: pxa3xx: Use ECC strength and step size devicetree binding
> mtd: nand: pxa3xx: Add supported ECC strength and step size to the DT
> binding
>
> .../devicetree/bindings/mtd/pxa3xx-nand.txt | 8 +++
> drivers/mtd/nand/pxa3xx_nand.c | 78 +++++++++++++---------
> include/linux/platform_data/mtd-nand-pxa3xx.h | 3 +
> 3 files changed, 59 insertions(+), 30 deletions(-)
>
> --
> 1.9.0
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Simon Guinot <simon.guinot@sequanux.org>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: Lior Amsalem <alior@marvell.com>,
devicetree@vger.kernel.org, Tawfik Bayouk <tawfik@marvell.com>,
Seif Mazareeb <seif@marvell.com>, Willy Tarreau <w@1wt.eu>,
Simon Guinot <sguinot@lacie.com>,
linux-mtd@lists.infradead.org,
Gregory Clement <gregory.clement@free-electrons.com>,
Brian Norris <computersforpeace@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Subject: Re: [PATCH v2 0/4] Allow to specify an ECC scheme through DT
Date: Tue, 1 Apr 2014 12:04:17 +0200 [thread overview]
Message-ID: <20140401100417.GI27979@kw.sim.vm.gnt> (raw)
In-Reply-To: <1395401690-25221-1-git-send-email-ezequiel.garcia@free-electrons.com>
[-- Attachment #1.1: Type: text/plain, Size: 2457 bytes --]
On Fri, Mar 21, 2014 at 08:34:46AM -0300, Ezequiel Garcia wrote:
> Now that we have agreed on the ECC devicetree binding, here's a patchset
> that makes pxa3xx-nand driver use it.
>
> This work is required on platforms where the flash device reports a required
> ECC strength, but that are capable of handling a stronger one. Simon Guinot
> reported a situation where the vendor provided a bootloader configured with
> a stronger than required ECC scheme. Without this patches, such a situation
> would require a hack to make the driver use a specific ECC scheme.
>
> (Simon: it would be great if you can confirm this allows you to remove any hacks).
Hi Ezequiel,
I confirm this allows me to configure the ECC strength and step size
from DT.
Tested-by: Simon Guinot <simon.guinot@sequanux.org>
Thanks.
Simon
>
> The first two patches clean the pxa_ecc_init(), preparing for the real
> work to be done.
>
> The third patch makes use of the ECC strength and ECC step size parameters.
> To ensure full backward compatibility, the patch *tries* to use DT-specified
> ECC parameters, falling back to using the ONFI-specified settings if the
> former are missing.
>
> Also, we use the ONFI 'datasheet' ECC strength requirement, to ensure the
> DT-specified ECC strength is strong enough to meet the requirement.
>
> Finally, the last patch updates the documentation binding, with the supported
> ECC parameters.
>
> Tested on Marvell's Armada 370 RD and also Compulab's CM-X300 (PXA3xx SoC),
> which is a non-DT platform. Based on today's l2-mtd.git.
>
> Changes from v1:
>
> * Fixed typo in ECC strength normalization calculus.
>
> Ezequiel Garcia (4):
> mtd: nand: pxa3xx: Normalize ECC strength for ECC scheme selection
> mtd: nand: pxa3xx: Clean pxa_ecc_init() error handling
> mtd: nand: pxa3xx: Use ECC strength and step size devicetree binding
> mtd: nand: pxa3xx: Add supported ECC strength and step size to the DT
> binding
>
> .../devicetree/bindings/mtd/pxa3xx-nand.txt | 8 +++
> drivers/mtd/nand/pxa3xx_nand.c | 78 +++++++++++++---------
> include/linux/platform_data/mtd-nand-pxa3xx.h | 3 +
> 3 files changed, 59 insertions(+), 30 deletions(-)
>
> --
> 1.9.0
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 144 bytes --]
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2014-04-01 10:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 11:34 [PATCH v2 0/4] Allow to specify an ECC scheme through DT Ezequiel Garcia
2014-03-21 11:34 ` Ezequiel Garcia
2014-03-21 11:34 ` [PATCH v2 1/4] mtd: nand: pxa3xx: Normalize ECC strength for ECC scheme selection Ezequiel Garcia
2014-03-21 11:34 ` Ezequiel Garcia
2014-03-21 11:34 ` [PATCH v2 2/4] mtd: nand: pxa3xx: Clean pxa_ecc_init() error handling Ezequiel Garcia
2014-03-21 11:34 ` Ezequiel Garcia
2014-03-21 11:34 ` [PATCH v2 3/4] mtd: nand: pxa3xx: Use ECC strength and step size devicetree binding Ezequiel Garcia
2014-03-21 11:34 ` Ezequiel Garcia
2014-05-12 18:01 ` Brian Norris
2014-05-12 18:01 ` Brian Norris
2014-05-12 19:18 ` Ezequiel Garcia
2014-05-12 19:18 ` Ezequiel Garcia
2014-05-13 23:37 ` Brian Norris
2014-05-13 23:37 ` Brian Norris
2014-03-21 11:34 ` [PATCH v2 4/4] mtd: nand: pxa3xx: Add supported ECC strength and step size to the DT binding Ezequiel Garcia
2014-03-21 11:34 ` Ezequiel Garcia
2014-04-01 10:04 ` Simon Guinot [this message]
2014-04-01 10:04 ` [PATCH v2 0/4] Allow to specify an ECC scheme through DT Simon Guinot
2014-04-03 15:19 ` Ezequiel Garcia
2014-04-03 15:19 ` Ezequiel Garcia
2014-04-14 14:56 ` Ezequiel Garcia
2014-04-14 14:56 ` Ezequiel Garcia
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=20140401100417.GI27979@kw.sim.vm.gnt \
--to=simon.guinot@sequanux.org \
--cc=alior@marvell.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=linux-mtd@lists.infradead.org \
--cc=seif@marvell.com \
--cc=sguinot@lacie.com \
--cc=tawfik@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=w@1wt.eu \
/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.