From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mason Yang <masonccyang@mxic.com.tw>
Cc: vigneshr@ti.com, bbrezillon@kernel.org, juliensu@mxic.com.tw,
richard@nod.at, linux-kernel@vger.kernel.org,
frieder.schrempf@kontron.de, marek.vasut@gmail.com,
linux-mtd@lists.infradead.org, computersforpeace@gmail.com,
dwmw2@infradead.org, zhengxunli@mxic.com.tw
Subject: Re: [PATCH v2] mtd: rawnand: Add Macronix NAND read retry support
Date: Mon, 20 May 2019 14:34:38 +0200 [thread overview]
Message-ID: <20190520143438.46248bfc@xps13> (raw)
In-Reply-To: <1558076001-29579-1-git-send-email-masonccyang@mxic.com.tw>
Hi Mason,
Mason Yang <masonccyang@mxic.com.tw> wrote on Fri, 17 May 2019 14:53:21
+0800:
> Add support for Macronix NAND read retry.
>
> Macronix NANDs support specific read operation for data recovery,
> which can be enabled/disabled with a SET/GET_FEATURE.
> Driver checks byte 167 of Vendor Blocks in ONFI parameter page table
> to see if this high-reliability function is supported.
>
> Signed-off-by: Mason Yang <masonccyang@mxic.com.tw>
> ---
> drivers/mtd/nand/raw/nand_macronix.c | 57 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 57 insertions(+)
>
> diff --git a/drivers/mtd/nand/raw/nand_macronix.c b/drivers/mtd/nand/raw/nand_macronix.c
> index e287e71..1a4dc92 100644
> --- a/drivers/mtd/nand/raw/nand_macronix.c
> +++ b/drivers/mtd/nand/raw/nand_macronix.c
> @@ -17,6 +17,62 @@
>
> #include "internals.h"
>
> +#define MACRONIX_READ_RETRY_BIT BIT(0)
> +#define MACRONIX_READ_RETRY_MODE 6
Can you name this define MACRONIX_NUM_READ_RETRY_MODES?
> +
> +struct nand_onfi_vendor_macronix {
> + u8 reserved[1];
Do you need this "[1]" ?
> + u8 reliability_func;
> +} __packed;
> +
> +/*
> + * Macronix NANDs support using SET/GET_FEATURES to enter/exit read retry mode
> + */
> +static int macronix_nand_setup_read_retry(struct nand_chip *chip, int mode)
> +{
> + u8 feature[ONFI_SUBFEATURE_PARAM_LEN];
> + int ret, feature_addr = ONFI_FEATURE_ADDR_READ_RETRY;
> +
> + if (chip->parameters.supports_set_get_features &&
> + test_bit(feature_addr, chip->parameters.set_feature_list) &&
> + test_bit(feature_addr, chip->parameters.get_feature_list)) {
> + feature[0] = mode;
> + ret = nand_set_features(chip, feature_addr, feature);
> + if (ret)
> + pr_err("Failed to set read retry moded:%d\n", mode);
Do you have to call nand_get_features() on error?
> +
> + ret = nand_get_features(chip, feature_addr, feature);
> + if (ret || feature[0] != mode)
> + pr_err("Failed to verify read retry moded:%d(%d)\n",
> + mode, feature[0]);
if ret == 0 but feature[0] != mode, shouldn't you return an error?
> + }
> +
> + return ret;
This will produce a Warning at compile time (ret may be used
uninitialized). Have you tested it?
> +}
> +
> +static void macronix_nand_onfi_init(struct nand_chip *chip)
> +{
> + struct nand_parameters *p = &chip->parameters;
> + struct nand_onfi_vendor_macronix *mxic;
> +
> + if (!p->onfi)
> + return;
> +
> + mxic = (struct nand_onfi_vendor_macronix *)p->onfi->vendor;
> + if ((mxic->reliability_func & MACRONIX_READ_RETRY_BIT) == 0)
> + return;
> +
> + chip->read_retries = MACRONIX_READ_RETRY_MODE;
> + chip->setup_read_retry = macronix_nand_setup_read_retry;
> +
> + if (p->supports_set_get_features) {
> + bitmap_set(p->set_feature_list,
> + ONFI_FEATURE_ADDR_READ_RETRY, 1);
> + bitmap_set(p->get_feature_list,
> + ONFI_FEATURE_ADDR_READ_RETRY, 1);
> + }
> +}
> +
> /*
> * Macronix AC series does not support using SET/GET_FEATURES to change
> * the timings unlike what is declared in the parameter page. Unflag
> @@ -65,6 +121,7 @@ static int macronix_nand_init(struct nand_chip *chip)
> chip->options |= NAND_BBM_FIRSTPAGE | NAND_BBM_SECONDPAGE;
>
> macronix_nand_fix_broken_get_timings(chip);
> + macronix_nand_onfi_init(chip);
>
> return 0;
> }
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mason Yang <masonccyang@mxic.com.tw>
Cc: bbrezillon@kernel.org, marek.vasut@gmail.com,
linux-kernel@vger.kernel.org, richard@nod.at,
dwmw2@infradead.org, computersforpeace@gmail.com,
linux-mtd@lists.infradead.org, vigneshr@ti.com,
frieder.schrempf@kontron.de, juliensu@mxic.com.tw,
zhengxunli@mxic.com.tw
Subject: Re: [PATCH v2] mtd: rawnand: Add Macronix NAND read retry support
Date: Mon, 20 May 2019 14:34:38 +0200 [thread overview]
Message-ID: <20190520143438.46248bfc@xps13> (raw)
In-Reply-To: <1558076001-29579-1-git-send-email-masonccyang@mxic.com.tw>
Hi Mason,
Mason Yang <masonccyang@mxic.com.tw> wrote on Fri, 17 May 2019 14:53:21
+0800:
> Add support for Macronix NAND read retry.
>
> Macronix NANDs support specific read operation for data recovery,
> which can be enabled/disabled with a SET/GET_FEATURE.
> Driver checks byte 167 of Vendor Blocks in ONFI parameter page table
> to see if this high-reliability function is supported.
>
> Signed-off-by: Mason Yang <masonccyang@mxic.com.tw>
> ---
> drivers/mtd/nand/raw/nand_macronix.c | 57 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 57 insertions(+)
>
> diff --git a/drivers/mtd/nand/raw/nand_macronix.c b/drivers/mtd/nand/raw/nand_macronix.c
> index e287e71..1a4dc92 100644
> --- a/drivers/mtd/nand/raw/nand_macronix.c
> +++ b/drivers/mtd/nand/raw/nand_macronix.c
> @@ -17,6 +17,62 @@
>
> #include "internals.h"
>
> +#define MACRONIX_READ_RETRY_BIT BIT(0)
> +#define MACRONIX_READ_RETRY_MODE 6
Can you name this define MACRONIX_NUM_READ_RETRY_MODES?
> +
> +struct nand_onfi_vendor_macronix {
> + u8 reserved[1];
Do you need this "[1]" ?
> + u8 reliability_func;
> +} __packed;
> +
> +/*
> + * Macronix NANDs support using SET/GET_FEATURES to enter/exit read retry mode
> + */
> +static int macronix_nand_setup_read_retry(struct nand_chip *chip, int mode)
> +{
> + u8 feature[ONFI_SUBFEATURE_PARAM_LEN];
> + int ret, feature_addr = ONFI_FEATURE_ADDR_READ_RETRY;
> +
> + if (chip->parameters.supports_set_get_features &&
> + test_bit(feature_addr, chip->parameters.set_feature_list) &&
> + test_bit(feature_addr, chip->parameters.get_feature_list)) {
> + feature[0] = mode;
> + ret = nand_set_features(chip, feature_addr, feature);
> + if (ret)
> + pr_err("Failed to set read retry moded:%d\n", mode);
Do you have to call nand_get_features() on error?
> +
> + ret = nand_get_features(chip, feature_addr, feature);
> + if (ret || feature[0] != mode)
> + pr_err("Failed to verify read retry moded:%d(%d)\n",
> + mode, feature[0]);
if ret == 0 but feature[0] != mode, shouldn't you return an error?
> + }
> +
> + return ret;
This will produce a Warning at compile time (ret may be used
uninitialized). Have you tested it?
> +}
> +
> +static void macronix_nand_onfi_init(struct nand_chip *chip)
> +{
> + struct nand_parameters *p = &chip->parameters;
> + struct nand_onfi_vendor_macronix *mxic;
> +
> + if (!p->onfi)
> + return;
> +
> + mxic = (struct nand_onfi_vendor_macronix *)p->onfi->vendor;
> + if ((mxic->reliability_func & MACRONIX_READ_RETRY_BIT) == 0)
> + return;
> +
> + chip->read_retries = MACRONIX_READ_RETRY_MODE;
> + chip->setup_read_retry = macronix_nand_setup_read_retry;
> +
> + if (p->supports_set_get_features) {
> + bitmap_set(p->set_feature_list,
> + ONFI_FEATURE_ADDR_READ_RETRY, 1);
> + bitmap_set(p->get_feature_list,
> + ONFI_FEATURE_ADDR_READ_RETRY, 1);
> + }
> +}
> +
> /*
> * Macronix AC series does not support using SET/GET_FEATURES to change
> * the timings unlike what is declared in the parameter page. Unflag
> @@ -65,6 +121,7 @@ static int macronix_nand_init(struct nand_chip *chip)
> chip->options |= NAND_BBM_FIRSTPAGE | NAND_BBM_SECONDPAGE;
>
> macronix_nand_fix_broken_get_timings(chip);
> + macronix_nand_onfi_init(chip);
>
> return 0;
> }
Thanks,
Miquèl
next prev parent reply other threads:[~2019-05-20 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 6:53 [PATCH v2] mtd: rawnand: Add Macronix NAND read retry support Mason Yang
2019-05-17 6:53 ` Mason Yang
2019-05-20 12:34 ` Miquel Raynal [this message]
2019-05-20 12:34 ` Miquel Raynal
2019-05-21 2:42 ` masonccyang
2019-05-21 2:42 ` masonccyang
2019-05-21 8:47 ` Miquel Raynal
2019-05-21 8:47 ` Miquel Raynal
2019-05-24 7:40 ` masonccyang
2019-05-24 7:40 ` masonccyang
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=20190520143438.46248bfc@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=frieder.schrempf@kontron.de \
--cc=juliensu@mxic.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=masonccyang@mxic.com.tw \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=zhengxunli@mxic.com.tw \
/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.