diff options
| author | Chris Packham <[email protected]> | 2017-06-09 15:58:31 +1200 |
|---|---|---|
| committer | Brian Norris <[email protected]> | 2017-06-13 10:00:55 -0700 |
| commit | 1eeef2d7483a7e3f8d2dd2a5b9939b3b814dc549 (patch) | |
| tree | d640a89b2e161c18606348a885fd5434e5d143a9 /tools/perf/scripts/python/call-graph-from-sql.py | |
| parent | c46adf0976eacadd60920da5b8bf8e27299183bd (diff) | |
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 <[email protected]>
Signed-off-by: Chris Packham <[email protected]>
Acked-by: Boris Brezillon <[email protected]>
Signed-off-by: Brian Norris <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-sql.py')
0 files changed, 0 insertions, 0 deletions