u-boot.git/drivers/mtd/spi, branch v2009.08-rc2

Add driver for the ST M95xxx SPI EEPROM

2009-08-09T21:45:14Z

This chip is used in a number of boards manufactured by Calao-Systems which should be supported soon. This driver provides the necessary spi_read and spi_write functions necessary to communicate with the chip. Signed-off-by: Albin Tonnerre

sf: Macronix additional chips supported

2009-07-06T22:46:20Z

new chips supported:- MX25L1605D, MX25L3205D, MX25L6405D, MX25L12855E out of which MX25L6405D and MX25L12855E tested on Kirkwood platforms Modified the Macronix flash support to use 2 bytes of device id instead of 1 This was required to support MX25L12855E Signed-off-by: Piyush Shah Signed-off-by: Prafulla Wadaskar Signed-off-by: Mike Frysinger

sf: sst: add sst25vf###b ids

2009-07-06T22:46:20Z

Signed-off-by: Mike Frysinger

sf: sst: fix sector size

2009-07-06T22:46:20Z

Looks like when I was encoding the sector sizes, I forgot to divide by 8 (due to the stupid marketing driven process that declares all sizes in useless megabits and not megabytes). Signed-off-by: Mike Frysinger

sf: new Macronix MX25xx SPI flash driver

2009-06-12T18:47:18Z

Added macronix SF driver for MTD framework MX25L12805D is supported and tested TBD: sector erase implementation, other deivces support Signed-off-by: Prafulla Wadaskar Signed-off-by: Mike Frysinger

sf: atmel: implement power-of-two write/erase funcs

2009-06-12T18:47:18Z

Signed-off-by: Todor I Mollov Signed-off-by: Mike Frysinger CC: Haavard Skinnemoen

sf: stmicro: dont send 4 bytes when reading status register

2009-04-02T16:51:28Z

I can't find anywhere in the datasheet that says the status register needs 3 dummy bytes sent to it before being able to read back the first real result. Tests on a Blackfin board show that after writing the opcode, the status register starts coming back immediately. So only write out the read status register opcode before polling the result. Signed-off-by: Mike Frysinger CC: Jason McMullan CC: TsiChung Liew

sf: set common timeouts in seconds, not milliseconds

2009-04-02T12:11:31Z

Since timeouts are only hit when there is a problem in the system, we don't want to prematurely timeout on a functioning setup. Thus having low timeouts (in milliseconds) doesn't gain us anything in the production case, but rather increases likely hood of causing problems where none otherwise exist. Signed-off-by: Mike Frysinger CC: Haavard Skinnemoen

sf: stmicro: use common page timeout define

2009-04-02T10:51:55Z

Signed-off-by: Mike Frysinger CC: Haavard Skinnemoen

sf: always read 5 bytes for the idcode

2009-04-02T10:50:21Z

Some SPI flash drivers like to have extended id information available (like the spansion flash), so rather than making it re-issue the ID cmd to get at the last 2 bytes, have the common code read 5 bytes rather than just 3. This also matches the Linux behavior where it always reads 5 id bytes from all flashes. Signed-off-by: Mike Frysinger Acked-by: Haavard Skinnemoen CC: Mingkai Hu