u-boot.git/drivers/mtd, branch v2015.04

lpc32xx: mtd: nand: add MLC NAND controller

2015-04-10T12:22:56+00:00

The controller's Reed-Solomon ECC hardware is
used except of course for raw reads and writes.
It covers in- and out-of-band data together.

The SPL framework is supported.

Signed-off-by: Albert ARIBAUD (3ADEV)

Merge branch 'master' of git://git.denx.de/u-boot-atmel

2015-03-31T23:15:59+00:00

ARM: at91: atmel_nand: Support flash based BBT

2015-03-31T23:04:28+00:00

Add support for on-flash bad block table. This makes U-Boot handle an existing
BBT correctly.

Signed-off-by: David Dueck 
Reviewed-by: Boris BREZILLON 
CC: Boris BREZILLON 
CC: Josh Wu 
CC: Andreas Bießmann 
CC: Scott Wood 
Acked-by: Josh Wu

mtd: vf610_nfc: specify transfer size before each transfer

2015-03-31T04:35:27+00:00

Testing showed, that commands like STATUS made the buffer dirty
when executed with NFC_SECSZ set to the page size. It looks
like the controller transfers bogus data when this register
is configured. When setting it to 0, the buffer does not get
altered while the status command still seems to work flawless.

Signed-off-by: Stefan Agner

mtd: vf610_nfc: mark page as dirty on block erase

2015-03-31T04:33:42+00:00

The driver tries to re-use the page buffer by storing the page
number of the current page in the buffer. The page is only read
if the requested page number is not currently in the buffer. When
a block is erased, the page number is marked as invalid if the
erased page equals the one currently in the cache. However, since
a erase block consists of multiple pages, also other page numbers
could be affected.

The commands to reproduce this issue (on a written page):
> nand dump 0x800
> nand erase 0x0 0x20000
> nand dump 0x800

The second nand dump command returns the data from the buffer,
while in fact the page is erased (0xff).

Avoid the hassle to calculate whether the page is affected or not,
but set the page buffer unconditionally to invalid instead.

Signed-off-by: Stefan Agner

nand: yaffs: Remove the "nand write.yaffs" command

2015-03-31T04:24:39+00:00

This command is only enabled by one board, complicates the NAND code,
and doesn't appear to have been functioning properly for several
years.  If there are no bad blocks in the NAND region being written
nand_write_skip_bad() will take the shortcut of calling nand_write()
which bypasses the special yaffs handling.  This causes invalid YAFFS
data to be written. See
http://lists.denx.de/pipermail/u-boot/2011-September/102830.html for
an example and a potential workaround.

U-Boot still retains the ability to mount and access YAFFS partitions
via CONFIG_YAFFS2.

Signed-off-by: Peter Tyser

nand: Remove CONFIG_MTD_NAND_VERIFY_WRITE

2015-03-31T04:24:39+00:00

The CONFIG_MTD_NAND_VERIFY_WRITE has been removed from Linux for some
time and a more generic method of NAND verification now exists in U-Boot.

Signed-off-by: Peter Tyser 
Tested-by: Heiko Schocher 
Acked-by: Heiko Schocher

nand: Add verification functions

2015-03-31T04:24:38+00:00

Add nand_verify() and nand_verify_page_oob().  nand_verify() verifies
NAND contents against an arbitrarily sized buffer using ECC while
nand_verify_page_oob() verifies a NAND page's contents and OOB.

Signed-off-by: Peter Tyser 
Tested-by: Heiko Schocher 
Acked-by: Heiko Schocher

mtd: nand: mxs: fix PIO_WORDs in mxs_nand_write_buf()

2015-03-31T03:25:54+00:00

There is only one pio_word in this DMA transaction so data field must be 1.

Signed-off-by: Luca Ellero

mtd: nand: mxs: fix PIO_WORDs in mxs_nand_read_buf()

2015-03-31T03:25:47+00:00

There is only one pio_word in this DMA transaction so data field must be 1.

Signed-off-by: Luca Ellero