linux-toradex.git/drivers/mtd/devices, branch v3.12.51

mtd: devices: elm: fix elm_context_save() and elm_context_restore() functions

2014-07-29T15:01:45+00:00

commit 6938ad40cb97a52d88a763008935340729a4acc7 upstream.

These two function's switch case lack the 'break' that make them always
return error.

Signed-off-by: Ted Juan 
Acked-by: Pekon Gupta 
Signed-off-by: Brian Norris 
Signed-off-by: Jiri Slaby

mtd: m25p80: fix allocation size

2013-12-04T19:05:24+00:00

commit 778d226a1462572b51d6777cdb1d611543410cb4 upstream.

This patch fixes two memory errors:

1. During a probe failure (in mtd_device_parse_register?) the command
   buffer would not be freed.

2. The command buffer's size is determined based on the 'fast_read'
   boolean, but the assignment of fast_read is made after this
   allocation. Thus, the buffer may be allocated "too small".

To fix the first, just switch to the devres version of kzalloc.

To fix the second, increase MAX_CMD_SIZE unconditionally. It's not worth
saving a byte to fiddle around with the conditions here.

This problem was reported by Yuhang Wang a while back.

Signed-off-by: Brian Norris 
Reported-by: Yuhang Wang 
Reviewed-by: Sourav Poddar 
Signed-off-by: Greg Kroah-Hartman

mtd: m25p80: Fix 4 byte addressing mode for Micron devices.

2013-09-27T10:56:22+00:00

According to the datasheet for Micron n25q256a (N25Q256A13ESF40F) 4-byte
addressing mode should be entered as follows:


To enter or exit the 4-byte address mode, the WRITE ENABLE command
must be executed to set the write enable latch bit to 1. (Note: The
WRITE ENABLE command must NOT be executed on the N25Q256A83ESF40x and
N25Q256A83E1240x devices.) S# must be driven LOW. The effect of the
command is immediate; after the command has been executed, the write
enable latch bit is cleared to 0.


Micron's portable way to perform this for all types of Micron flash
is to first issue a write enable, then switch the addressing mode
followed by a write disable to avoid leaving the flash in a write-
able state.

Signed-off-by: Elie De Brauwer 
[Brian: reworked a bit]
Signed-off-by: Brian Norris 
Signed-off-by: David Woodhouse

mtd: chips: Add support for PMC SPI Flash chips in m25p80.c

2013-08-30T22:57:37+00:00

Add support for PMC (now Chingis, part of ISSI) Pm25LV512 (512 Kib),
Pm25LV010 (1 Mib) and Pm25LQ032 (32 Mib) SPI Flash chips.

This patch addresses two generations of PMC SPI Flash chips:

 - Pm25LV512 and Pm25LV010: these have 4KiB sectors and 32KiB
   blocks. The 4KiB sector erase uses a non-standard opcode
   (0xd7). They do not support JEDEC RDID (0x9f), and so they can only
   be detected by matching their name string with pre-configured
   platform data. Because of the cascaded acquisitions, the datasheet
   is no longer available on the current manufacturer's website,
   although it is still commonly used in some recent wireless routers
   (). The
   only public datasheet available seems to be on GeoCities:
   

 - Pm25LQ032: a newer generation flash, with 4KiB sectors and 64KiB
   blocks. It uses the standard erase and JEDEC read-ID
   opcodes. Manufacturer's datasheet is here:
   

This patch is resent in order to take into account both Brian Norris
remarks and this upstream patch:

commit e534ee4f9ca29fdb38eea4b0c53f2154fbd8c1ee
Author: Krzysztof Mazur 
Date:   Fri Feb 22 15:51:05 2013 +0100

    mtd: m25p80: introduce SST_WRITE flag for SST byte programming

    Not all SST devices implement the SST byte programming command.
    Some devices (like SST25VF064C) implement only standard m25p80 page
    write command.

    Now SPI flash devices that need sst_write() are explicitly marked
    with new SST_WRITE flag and the decision to use sst_write() is based
    on this flag instead of manufacturer id.

Signed-off-by: Gabor Juhos 
Signed-off-by: Michel Stempin 
[Brian: fixed conflict]
Signed-off-by: Brian Norris 
Signed-off-by: David Woodhouse

mtd: bcm47xxsflash: writing support

2013-08-30T20:52:20+00:00

Tested with BCM4706.

Signed-off-by: Rafał Miłecki 
Signed-off-by: Brian Norris 
Signed-off-by: David Woodhouse

mtd: bcm47xxsflash: implement erasing support

2013-08-30T20:52:15+00:00

Signed-off-by: Rafał Miłecki 
Signed-off-by: Brian Norris 
Signed-off-by: David Woodhouse

mtd: bcm47xxsflash: convert to module_platform_driver instead of init/exit

2013-08-30T20:52:14+00:00

convert to module_platform_driver instead of init/exit

Suggested-by: Andy Shevchenko 
Signed-off-by: Libo chen 
Signed-off-by: Brian Norris 
Signed-off-by: David Woodhouse

mtd: bcm47xxsflash: convert kzalloc to avoid invalid access

2013-08-30T20:52:10+00:00

mtd is just member of bcm47xxsflash, so we should free bcm47xxsflash not
its member. So I use devm_kazlloc instead of kazlloc to avoid it.

* Changelog:
   convert to devm_kzalloc

Signed-off-by: Libo chen 
Suggested-by: Andy Shevchenko 
Reviewed-by: Andy Shevchenko 
[Brian: fixed conflicts]
Signed-off-by: Brian Norris 

Signed-off-by: David Woodhouse

mtd: spear_smi: add missing __iomem annotation

2013-08-30T20:51:48+00:00

Added missing __iomem annotation in order to fix the following
sparse warnings:

drivers/mtd/devices/spear_smi.c:566:13: warning: incorrect type in assignment (different address spaces)
drivers/mtd/devices/spear_smi.c:566:13:    expected void *src
drivers/mtd/devices/spear_smi.c:566:13:    got void [noderef] *
drivers/mtd/devices/spear_smi.c:586:9: warning: incorrect type in argument 2 (different address spaces)
drivers/mtd/devices/spear_smi.c:586:9:    expected void const volatile [noderef] *
drivers/mtd/devices/spear_smi.c:586:9:    got unsigned char [usertype] *
drivers/mtd/devices/spear_smi.c:659:14: warning: incorrect type in assignment (different address spaces)
drivers/mtd/devices/spear_smi.c:659:14:    expected void *dest
drivers/mtd/devices/spear_smi.c:659:14:    got void [noderef] *
drivers/mtd/devices/spear_smi.c:620:9: warning: incorrect type in argument 1 (different address spaces)
drivers/mtd/devices/spear_smi.c:620:9:    expected void volatile [noderef] *
drivers/mtd/devices/spear_smi.c:620:9:    got void *dest
drivers/mtd/devices/spear_smi.c:620:9: warning: incorrect type in argument 1 (different address spaces)
drivers/mtd/devices/spear_smi.c:620:9:    expected void volatile [noderef] *
drivers/mtd/devices/spear_smi.c:620:9:    got void *dest
drivers/mtd/devices/spear_smi.c:620:9: warning: incorrect type in argument 1 (different address spaces)
drivers/mtd/devices/spear_smi.c:620:9:    expected void volatile [noderef] *
drivers/mtd/devices/spear_smi.c:620:9:    got void *dest

Signed-off-by: Jingoo Han 
Signed-off-by: Brian Norris 
Signed-off-by: David Woodhouse

mtd: m25p80: add support for mr25h10

2013-08-30T20:44:10+00:00

This adds support for the Everspin mr25h10 MRAM chip to the m25p80
driver.

Signed-off-by: Sascha Hauer 
Acked-by: Marek Vasut 
Signed-off-by: Artem Bityutskiy 
Signed-off-by: Brian Norris 
Signed-off-by: David Woodhouse