linux-toradex.git/include/linux/mtd/nand.h, branch v3.0.29

mtd: nand: renumber conflicting BBT flags

2011-05-25T00:49:43+00:00

The NAND_USE_FLASH_BBT_NO_OOB and NAND_CREATE_EMPTY_BBT flags conflict
with the NAND_BBT_SCANBYTE1AND6 and NAND_BBT_DYNAMICSTRUCT flags,
respectively. This change will allow us to utilize these options
independently.

Signed-off-by: Brian Norris 
Signed-off-by: Artem Bityutskiy 
Signed-off-by: David Woodhouse

Fix common misspellings

2011-03-31T14:26:23+00:00

Fixes generated by 'codespell' and manually reviewed.

Signed-off-by: Lucas De Marchi

mtd: nand: add software BCH ECC support

2011-03-11T17:49:08+00:00

This patch adds software BCH ECC support to mtd, in order to handle recent
NAND device ecc requirements (4 bits or more).

It does so by adding a new ecc mode (NAND_ECC_SOFT_BCH) for use by board
drivers, and a new Kconfig option to enable BCH support. It relies on the
generic BCH library introduced in a previous patch.

When a board driver uses mode NAND_ECC_SOFT_BCH, it should also set fields
chip->ecc.size and chip->ecc.bytes to select BCH ecc data size and required
error correction capability. See nand_bch_init() documentation for details.

It has been tested on the following platforms using mtd-utils, UBI and
UBIFS: x86 (with nandsim), arm926ejs.

Signed-off-by: Ivan Djelic 
Signed-off-by: David Woodhouse

mtd: fix nand kernel-doc warnings

2010-12-03T16:31:24+00:00

Warning(include/linux/mtd/nand.h:543): No description found for parameter 'badblockbits'
Warning(drivers/mtd/nand/nand_bbt.c:1101): No description found for parameter 'mtd'

Signed-off-by: Randy Dunlap 
Cc:	David Woodhouse 
Cc:	linux-mtd@lists.infradead.org
Signed-off-by: Artem Bityutskiy 
Signed-off-by: David Woodhouse

mtd: remove junk tabs in nand.h

2010-10-24T23:56:51+00:00

Remove tabs between type and name.

Signed-off-by: Sebastian Andrzej Siewior 
Signed-off-by: Artem Bityutskiy 
Signed-off-by: David Woodhouse

mtd: cleanup nand.h

2010-10-24T23:56:32+00:00

- *var instead of * var
- proper multiline comment
- func(args) instead of func (args)
- 80 lines

So from
|total: 2 errors, 37 warnings, 654 lines checked
we got to one warning.

Signed-off-by: Sebastian Andrzej Siewior 
Signed-off-by: Artem Bityutskiy 
Signed-off-by: David Woodhouse

mtd: nand: introduce NAND_CREATE_EMPTY_BBT

2010-10-24T23:54:37+00:00

it will create an empty BBT table without considering vendor's BBT
information. Vendor's information may be unavailable if the NAND
controller has a different DATA & OOB layout or this information may be
allready purged.

Signed-off-by: Sebastian Andrzej Siewior 
Signed-off-by: David Woodhouse

mtd: nand: add support for BBT without OOB

2010-10-24T23:53:48+00:00

The first (sixt) byte in the OOB area contains vendor's bad block
information. During identification of the NAND chip this information is
collected by scanning the complete chip.
The option NAND_USE_FLASH_BBT is used to store this information in a sector so
we don't have to scan the complete flash. Unfortunately the code stores
a marker in order to recognize the BBT in the OOB area. This will fail
if the OOB area is completely used for ECC.
This patch introduces the option NAND_USE_FLASH_BBT_NO_OOB which has to be
used with NAND_USE_FLASH_BBT. It will then store BBT on flash without
touching the OOB area. The BBT format on flash remains same except the
first page starts with the recognition pattern followed by the version byte.
This change was tested in nandsim and it looks good so far :)

Signed-off-by: Sebastian Andrzej Siewior 
Signed-off-by: David Woodhouse

mtd: add init_size hook for NAND driver

2010-10-24T23:49:57+00:00

Not all the NAND devices have all the information in additional
id bytes.

So add a hook in the nand_chip{} is a good method to calculate the
right value of oobsize, erasesize and so on.

Without the hook,you will get the wrong value, and you have to hack
in the ->scan_bbt() to change the wrong value which make the code
mess.

Signed-off-by: Huang Shijie 
Signed-off-by: David Woodhouse

mtd: nand: add support for reading ONFI parameters from NAND device

2010-10-24T22:46:34+00:00

This patch adds support for reading NAND device ONFI parameters and use
the ONFI informations to define its geometry. In case the device supports
ONFI, the onfi_version field in struct nand_chip contains the version (BCD)
and the onfi_params structure can be used by drivers to set up timings and
such. We currently only support ONFI 1.0 parameters.

Signed-off-by: Brian Norris 
Signed-off-by: Matthieu Castet 
Signed-off-by: Maxime Bizon 
Signed-off-by: Florian Fainelli 
Signed-off-by: David Woodhouse