diff options
author | Chris Packham <chris.packham@alliedtelesis.co.nz> | 2017-06-09 05:58:31 +0200 |
---|---|---|
committer | Brian Norris <computersforpeace@gmail.com> | 2017-06-13 19:00:55 +0200 |
commit | 1eeef2d7483a7e3f8d2dd2a5b9939b3b814dc549 (patch) | |
tree | d640a89b2e161c18606348a885fd5434e5d143a9 /Documentation/devicetree | |
parent | mtd: subpagetest: fix wrong written check in function write_eraseblock2 (diff) | |
download | linux-1eeef2d7483a7e3f8d2dd2a5b9939b3b814dc549.tar.xz linux-1eeef2d7483a7e3f8d2dd2a5b9939b3b814dc549.zip |
mtd: handle partitioning on devices with 0 erasesize
erasesize is meaningful for flash devices but for SRAM there is no
concept of an erase block so erasesize is set to 0. When partitioning
these devices instead of ensuring partitions fall on erasesize
boundaries we ensure they fall on writesize boundaries.
Helped-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Diffstat (limited to 'Documentation/devicetree')
0 files changed, 0 insertions, 0 deletions