[PATCH v3 0/9] Better solution for the OMAP fix

[Miquel Raynal]

Hello,

I recently got a bug report regarding the OMAP driver. We fixed it and
merged the fix. This fix was involving accessing BCH internal values
from within the OMAP driver which is far from ideal.

Now that the urgence is gone, here is a series to do it "the proper
way".

Cheers,
Miquèl

Main changes in v3:
* Export the number of ECC steps
* Add a 'get number of ECC bytes per step' helper.

Miquel Raynal (9):
  mtd: nand: Let ECC engines advertize the exact number of steps
  mtd: nand: ecc-bch: Populate the public nsteps field
  mtd: nand: ecc-hamming: Populate the public nsteps field
  mtd: nand: Add a helper to retrieve the number of ECC steps
  mtd: nand: Add a helper to retrieve the number of ECC bytes per step
  mtd: rawnand: Try not to use the ECC private structures
  mtd: rawnand: omap: Use ECC information from the generic structures
  mtd: nand: ecc-bch: Use the public nsteps field
  mtd: nand: ecc-hamming: Use the public nsteps field

 drivers/mtd/nand/ecc-sw-bch.c           | 10 +++++-----
 drivers/mtd/nand/ecc-sw-hamming.c       | 10 +++++-----
 drivers/mtd/nand/raw/nand_base.c        | 16 +++++++---------
 drivers/mtd/nand/raw/omap2.c            | 14 ++++++++------
 include/linux/mtd/nand-ecc-sw-bch.h     |  2 --
 include/linux/mtd/nand-ecc-sw-hamming.h |  2 --
 include/linux/mtd/nand.h                | 22 ++++++++++++++++++++++
 7 files changed, 47 insertions(+), 29 deletions(-)

-- 
2.20.1