u-boot.git/include/flash.h, branch v2015.10

ARMv7M: add STM32F1 support

2015-05-28T12:18:24+00:00

Add ARMv7M STM32F1 support including clocks, timer, gpio, and flash.

Signed-off-by: Matt Porter

ARMv7M: Add STM32F4 support

2015-04-22T16:14:55+00:00

Signed-off-by: Kamil Lulko 
Reviewed-by: Tom Rini

mtd: Handle 29LV800BT

2014-11-19T07:48:41+00:00

The device id makes u-boot think that this chip needs
cfi_reverse_geometry(), which is not the case.
Add it to jedec_flash, so it is handled properly.

Signed-off-by: Dirk Eibach 
Signed-off-by: Stefan Roese

Coding Style cleanup: remove trailing white space

2013-10-14T20:06:53+00:00

Signed-off-by: Wolfgang Denk

Add GPL-2.0+ SPDX-License-Identifier to source files

2013-07-24T13:44:38+00:00

Signed-off-by: Wolfgang Denk 
[trini: Fixup common/cmd_io.c]
Signed-off-by: Tom Rini

mtd/cfi: add support for SST 4KB sector granularity

2013-01-10T13:39:13+00:00

Add support for SST 4KB sector granularity.

Many recent SST flashes, i.e. SST39VF3201B and similar of this family
are declared CFI-conformant from SST. They support CFI query, but implement
2 different sector sizes in the same memory: a 64KB sector (they call it
"block", std AMD erase cmd=0x30), and a 4KB sector (they call it "sector",
erase cmd=0x50). Also, CFI query on these chips, reading from address 0x2dh
of cfi query struct, detects a number of secotrs for the 4KB granularity
(flinfo shows it).

For all other aspects, they are CFI compliant, so, as Linux do, i think
it's a good idea to handle these chips in the CFI driver, with a fixup
to allow 4KB granularity, as should be expected, instead of 64KB.

Signed-off-by: Angelo Dureghello 
Signed-off-by: Stefan Rose

arm: Remove support for lpc2292

2012-10-26T20:35:20+00:00

This stuff has been rotting in the tree for a year now. Remove it.

Signed-off-by: Marek Vasut

cfi: Make the flash erase and write operations abortable

2012-09-03T09:24:27+00:00

Check for ctrlc() in operations that take time and loop over the flash
addresses.

In netconsole, tstc() is expensive.  Only check once in a while to not
slow down the operation significantly.

Signed-off-by: Joe Hershberger 
Signed-off-by: Stefan Roese

mtd/cfi_flash: fix write problems for Numonyx P33/30 32 MBit flashs

2012-08-13T12:34:44+00:00

commit 54652991
Work around bug in Numonyx P33/P30 256-Mbit 65nm flash chips

fixes a problem for Numonyx P33/P30 flashes for 256-Mbit, but this leads
to problems for smaller versions of this chip e.g. the 32Mbit version
with deviceid 0x16 on mgcoge. So move the code for this work around to
an own function and check previously manufacturer id and device id to
not break other flashes which don't need this work around.

Signed-off-by: Holger Brunck 
Signed-off-by: Heiko Schocher 
cc: Stefan Roese 
cc: Philippe De Muyter 
cc: Gerlando Falauto 
Signed-off-by: Stefan Roese

mtd, cfi: introduce void flash_protect_default(void)

2011-04-07T08:20:22+00:00

collect code which protects default sectors in a function, called
flash_protect_default. So boardspecific code can call it too.

Signed-off-by: Heiko Schocher 
Signed-off-by: Stefan Roese