lkml.org 
[lkml]   [2019]   [May]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v2] mtd: rawnand: Add Macronix NAND read retry support
Hi masonccyang@mxic.com.tw,

masonccyang@mxic.com.tw wrote on Tue, 21 May 2019 10:42:06 +0800:

> Hi Miquel,
>
> > > 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?
>
> okay, will fix.
>
> >
> > > +
> > > +struct nand_onfi_vendor_macronix {
> > > + u8 reserved[1];
> >
> > Do you need this "[1]" ?
>
> okay, just u8 reserved;
>
> >
> > > + 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?
>
> okay
>
> >
> > > +
> > > + 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?
>
> okay, will fix.
>
> >
> > > + }
> > > +
> > > + return ret;
> >
> > This will produce a Warning at compile time (ret may be used
> > uninitialized). Have you tested it?
>
> Tool chain I used is "gcc-arm-linux-gnueabi" and no Warning at compile
> time.

What's the output of:
gcc-arm-linux-gnueabi -v
?

>
> Patch it to:
> ----------------------------------------------------------------------------->
> 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);

^ extra space, please be careful with the
typos, and run checkpatch.pl --strict before
sending patches.

> if (ret) {
> pr_err("Failed to set read retry moded:%d\n",
> mode);
> goto err_out;
> }
>
> ret = nand_get_features(chip, feature_addr, feature);
> if (ret) {
> pr_err("Failed to get read retry moded:%d\n",
> mode);
> goto err_out;
> } else if (feature[0] != mode) {
> pr_err("Failed to verify read retry
> moded:%d(%d)\n",
> mode, feature[0]);
> return -EIO;

That's not what I meant. You can keep the former condition but if !ret
then ret = -EIO for instance.

> }
> }
>
> err_out:
> return ret;

Again, do not jump to a single return call, directly do the return from
the point where you want to quit the function.

The problem should be that ret may be used uninitialized, the compiler
should tell you that.

Thanks,
Miquèl

\
 
 \ /
  Last update: 2019-05-21 10:47    [W:0.075 / U:7.172 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site