[PATCH 0/5] Update for removing driver specific BBM functions

Abhishek Sahu
2018-07-06T07:53:24Z

This patch series deals mainly with removing driver specific bad block
functions and some minor fixing/cleanup.

1. When initial support for this driver was added [1], then the
plan was to remove these driver specific functions when NAND base
layer has support for doing raw read/write for bad block related
things. Moving to raw read/write seems to take more time so this patch
series implemented alternate logic for reading/writing bad block with
normal read/write itself. This alternate logic relies on some
assumption which seems to be better than driver specific functions and
provide more functionality. Some discussion regarding it has already
happened in [2].

2. Some part of code is duplicated in every read/write function
so clean up the code by making helper function.

3. Bootloaders does access protection for some of the NAND
registers which generates few write errors if it is enabled.

4. Create RAM based BBT table. Flash based BBT table can’t be
used since our bootloader does not have support for the same.

**This patch series is rebased over linux-next with PATCH [3]

[1]: http://patchwork.ozlabs.org/patch/508565/
[2]: https://patchwork.ozlabs.org/patch/920563/
[3]: https://patchwork.ozlabs.org/patch/938631/

Abhishek Sahu (5):
mtd: rawnand: qcom: remove driver specific bad block check function
mtd: rawnand: qcom: remove driver specific block_markbad function
mtd: rawnand: qcom: fix NAND register write errors
mtd: rawnand: qcom: update BBT related flags
mtd: rawnand: qcom: reorganization by removing read/write helpers

drivers/mtd/nand/raw/qcom_nandc.c | 439 ++++++++++++++------------------------
1 file changed, 162 insertions(+), 277 deletions(-)

--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc.
is a member of Code Aurora Forum, hosted by The Linux Foundation