devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Huang Shijie <b32955@freescale.com>
To: Huang Shijie <b32955@freescale.com>
Cc: devicetree@vger.kernel.org, dedekind1@gmail.com,
	t.figa@samsung.com, linux-mtd@lists.infradead.org,
	computersforpeace@gmail.com, dwmw2@infradead.org
Subject: Re: [PATCH v3] mtd: gpmi: add a new DT property to use the datasheet's minimum required ECC
Date: Tue, 12 Nov 2013 13:26:06 +0800	[thread overview]
Message-ID: <5281BBEE.7000502@freescale.com> (raw)
In-Reply-To: <1383818858-5410-1-git-send-email-b32955@freescale.com>

于 2013年11月07日 18:07, Huang Shijie 写道:
> In default way, we use the ecc_strength/ecc_step size calculated by ourselves
> and use all the OOB area.
>
> This patch adds a new property : "fsl,use-minimum-ecc"
>
> If we enable it, we will firstly try to use the datasheet's minimum required
> ECC provided by the MTD layer (the ecc_strength_ds/ecc_step_ds fields
> in the nand_chip{}). So we may have free space in the OOB area by using the
> minimum ECC, and we may support JFFS2 with some SLC NANDs, such as Micron's
> SLC NAND.
>
> If we fail to use the minimum ECC, we will use the legacy method to calculate
> the ecc_strength and ecc_step size.
>
> Signed-off-by: Huang Shijie<b32955@freescale.com>
> ---
> v1 -->  v2: rebase this patch on the latest l2-mtd.
> v2 -->  v3: change the descriptions.
> ---
>   .../devicetree/bindings/mtd/gpmi-nand.txt          |    8 ++++++++
>   drivers/mtd/nand/gpmi-nand/gpmi-nand.c             |    3 +++
>   2 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mtd/gpmi-nand.txt b/Documentation/devicetree/bindings/mtd/gpmi-nand.txt
> index 551b2a1..458d596 100644
> --- a/Documentation/devicetree/bindings/mtd/gpmi-nand.txt
> +++ b/Documentation/devicetree/bindings/mtd/gpmi-nand.txt
> @@ -17,6 +17,14 @@ Required properties:
>   Optional properties:
>     - nand-on-flash-bbt: boolean to enable on flash bbt option if not
>                          present false
> +  - fsl,use-minimum-ecc: Protect this NAND flash with the minimum ECC
> +                       strength required. The required ECC strength is
> +                       automatically discoverable for some flash
> +                       (e.g., according to the ONFI standard).
> +                       However, note that if this strength is not
> +                       discoverable or this property is not enabled,
> +                       the software may chooses an implementation-defined
> +                       ECC scheme.
>
>   The device tree may optionally contain sub-nodes describing partitions of the
>   address space. See partition.txt for more detail.
> diff --git a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> index 8f4e5b1..b849b92 100644
> --- a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> +++ b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> @@ -353,6 +353,9 @@ static int legacy_set_geometry(struct gpmi_nand_data *this)
>
>   int common_nfc_set_geometry(struct gpmi_nand_data *this)
>   {
> +	if (of_property_read_bool(this->dev->of_node, "fsl,use-minimum-ecc")
> +		&&  set_geometry_by_ecc_info(this))
> +		return 0;
>   	return legacy_set_geometry(this);
>   }
>
Hi Brian:
Is this patch ok now? I hope it can be accepted at this merge-window.


thanks
Huang Shijie


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2013-11-12  5:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 10:07 [PATCH v3] mtd: gpmi: add a new DT property to use the datasheet's minimum required ECC Huang Shijie
2013-11-12  5:26 ` Huang Shijie [this message]
2013-11-12 17:47   ` Brian Norris
     [not found]     ` <CAN8TOE_-O_gxM+c4k6NXvvo=7Ozp1J187=XtK9gxfLa4LGQAWQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-13 20:46       ` Brian Norris

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=5281BBEE.7000502@freescale.com \
    --to=b32955@freescale.com \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=t.figa@samsung.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;
as well as URLs for NNTP newsgroup(s).