From: Abhishek Sahu <absahu@codeaurora.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Boris Brezillon <boris.brezillon@bootlin.com>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Richard Weinberger <richard@nod.at>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, Andy Gross <andy.gross@linaro.org>,
Archit Taneja <architt@codeaurora.org>
Subject: Re: [PATCH v2 06/14] mtd: rawnand: qcom: erased page detection for uncorrectable errors only
Date: Tue, 22 May 2018 19:40:21 +0530 [thread overview]
Message-ID: <6368d5f14b40626bd590f6eda8cf1bcd@codeaurora.org> (raw)
In-Reply-To: <20180522090459.71d35004@xps13>
On 2018-05-22 12:34, Miquel Raynal wrote:
> Hi Abhishek,
>
> On Thu, 3 May 2018 17:50:33 +0530, Abhishek Sahu
> <absahu@codeaurora.org> wrote:
>
>> Following is the flow in the HW if controller tries to read erased
>> page
>
> Nit: ^ missing ':'
>
Sure. I will fix this.
>>
>> 1. First ECC uncorrectable error will be generated from ECC engine
>> since ECC engine first calculates the ECC with all 0xff and match
>> the calculated ECC with ECC code in OOB (which is again all 0xff).
>> 2. After getting ECC error, erased CW detection logic will be
>> applied which is different for BCH and RS ECC
>> a. For BCH, HW checks if all the bytes in page are 0xff and then
>> it updates the status in separate register
>> NAND_ERASED_CW_DETECT_STATUS.
>> b. For RS ECC, the HW reports the same error when reading an
>> erased CW, but it notifies that it is an erased CW by
>> placing special characters at certain offsets in the
>> buffer.
>>
>> So the erased CW detect status should be checked only if ECC engine
>> generated the uncorrectable error.
>>
>> Currently for all other operational errors also (like TIMEOUT, MPU
>> errors, etc.), the erased CW detect logic is being applied so fix this
>> and return EIO for other operational errors.
>>
>> Signed-off-by: Abhishek Sahu <absahu@codeaurora.org>
>> ---
>> * Changes from v1:
>>
>> 1. Added more detail in commit message
>> 2. Added comment before each if/else
>
> Thanks for that, it's much more ease to review :)
Thanks Miquel for your review.
Regards,
Abhishek
>
>> 3. Removed redundant check for BS_UNCORRECTABLE_BIT
>>
>> drivers/mtd/nand/raw/qcom_nandc.c | 65
>> ++++++++++++++++++++++++++-------------
>> 1 file changed, 43 insertions(+), 22 deletions(-)
>>
>
> Acked-by: Miquel Raynal <miquel.raynal@bootlin.com>
>
> Thanks,
> Miquèl
next prev parent reply other threads:[~2018-05-22 14:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 12:20 [PATCH v2 00/14] Update for QCOM NAND driver Abhishek Sahu
2018-05-03 12:20 ` [PATCH v2 01/14] mtd: rawnand: helper function for setting up ECC parameters Abhishek Sahu
2018-05-07 3:40 ` Masahiro Yamada
2018-05-07 6:01 ` Abhishek Sahu
2018-05-07 7:39 ` Boris Brezillon
2018-05-08 6:14 ` Masahiro Yamada
2018-05-08 7:21 ` Abhishek Sahu
2018-05-07 8:16 ` Boris Brezillon
2018-05-08 7:22 ` Abhishek Sahu
2018-05-03 12:20 ` [PATCH v2 02/14] mtd: rawnand: denali: use helper function for ecc setup Abhishek Sahu
2018-05-21 14:30 ` Miquel Raynal
2018-05-22 14:09 ` Abhishek Sahu
2018-05-03 12:20 ` [PATCH v2 03/14] dt-bindings: qcom_nandc: make nand-ecc-strength optional Abhishek Sahu
2018-05-03 12:20 ` Abhishek Sahu
2018-05-07 8:40 ` Boris Brezillon
2018-05-21 14:32 ` Miquel Raynal
2018-05-22 14:08 ` Abhishek Sahu
2018-05-03 12:20 ` [PATCH v2 04/14] mtd: rawnand: qcom: use the ecc strength from device parameter Abhishek Sahu
2018-05-07 8:28 ` Boris Brezillon
2018-05-08 7:26 ` Abhishek Sahu
2018-05-03 12:20 ` [PATCH v2 05/14] mtd: rawnand: qcom: wait for desc completion in all BAM channels Abhishek Sahu
2018-05-22 6:47 ` Miquel Raynal
2018-05-22 14:07 ` Abhishek Sahu
2018-05-03 12:20 ` [PATCH v2 06/14] mtd: rawnand: qcom: erased page detection for uncorrectable errors only Abhishek Sahu
2018-05-22 7:04 ` Miquel Raynal
2018-05-22 14:10 ` Abhishek Sahu [this message]
2018-05-03 12:20 ` [PATCH v2 07/14] mtd: rawnand: qcom: fix null pointer access for erased page detection Abhishek Sahu
2018-05-22 7:16 ` Miquel Raynal
2018-05-22 14:11 ` Abhishek Sahu
2018-05-03 12:20 ` [PATCH v2 08/14] mtd: rawnand: qcom: parse read errors for read oob also Abhishek Sahu
2018-05-03 12:20 ` [PATCH v2 09/14] mtd: rawnand: qcom: modify write_oob to remove read codeword part Abhishek Sahu
2018-05-22 10:02 ` Miquel Raynal
2018-05-22 14:14 ` Abhishek Sahu
2018-05-03 12:20 ` [PATCH v2 10/14] mtd: rawnand: qcom: fix return value for raw page read Abhishek Sahu
2018-05-22 12:04 ` Miquel Raynal
2018-05-22 14:15 ` Abhishek Sahu
2018-05-03 12:20 ` [PATCH v2 11/14] mtd: rawnand: qcom: minor code reorganization for bad block check Abhishek Sahu
2018-05-03 12:20 ` [PATCH v2 12/14] mtd: rawnand: qcom: check for operation errors in case of raw read Abhishek Sahu
2018-05-03 12:20 ` [PATCH v2 13/14] mtd: rawnand: qcom: helper function for " Abhishek Sahu
2018-05-03 12:20 ` [PATCH v2 14/14] mtd: rawnand: qcom: erased page bitflips detection Abhishek Sahu
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=6368d5f14b40626bd590f6eda8cf1bcd@codeaurora.org \
--to=absahu@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=architt@codeaurora.org \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
/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.