From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Felix Matouschek <felix@matouschek.org>
Cc: linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH v2] mtd: spinand: Add support for XTX XT26G0xA
Date: Mon, 11 Apr 2022 22:03:10 +0200 [thread overview]
Message-ID: <20220411220310.14e2da32@xps13> (raw)
In-Reply-To: <e697bea9-29b6-2f83-7d42-02afd88fa6b1@matouschek.org>
Hi Felix,
felix@matouschek.org wrote on Mon, 11 Apr 2022 21:53:06 +0200:
> Hi Miquel,
>
> Am 11.04.22 um 09:23 schrieb Miquel Raynal:
> >> +static int xt26g0xa_ecc_get_status(struct spinand_device *spinand,
> >> + u8 status)
> >> +{
> >> + switch (status & XT26G0XA_STATUS_ECC_MASK) {
> >> + case XT26G0XA_STATUS_ECC_NO_DETECTED:
> >> + return 0;
> >> + case XT26G0XA_STATUS_ECC_8_CORRECTED:
> >> + return 8;
> >> + case XT26G0XA_STATUS_ECC_UNCOR_ERROR:
> >> + return -EBADMSG;
> >> + default: /* (1 << 2) through (7 << 2) are 1-7 corrected errors */
> >> + return (status & XT26G0XA_STATUS_ECC_MASK) >> 2;
> >> + }
> >> +
> >> + return -EINVAL;
> >
> > You'll never end here, right? Perhaps there are values that you cannot
> > handle correctly in the switch and you should add a bit more logic to
> > return -EINVAL if something is wrong? Otherwise you will return 0
> > above, which might be correct (I'll let you verify but in this
> > case the final "return -EINVAL" seems useless.
>
> According to the data-sheet (section 7, page 27) the switch should be
> able to handle all values of the status register. So should I remove the
> final "return -EINVAL"?
I think so, yes.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-04-11 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 16:19 [PATCH v2] mtd: spinand: Add support for XTX XT26G0xA Felix Matouschek
2022-04-11 7:23 ` Miquel Raynal
2022-04-11 19:53 ` Felix Matouschek
2022-04-11 20:03 ` Miquel Raynal [this message]
2022-04-13 15:38 ` Felix Matouschek
2022-04-13 15:56 ` Miquel Raynal
2022-04-18 13:32 ` Felix Matouschek
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=20220411220310.14e2da32@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=felix@matouschek.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=vigneshr@ti.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