| commit | 61bb0d3d235c659eb407a7032aa9ec70a914dc03 | |
| author | Antonio Borneo <borneo.antonio@gmail.com> | |
| Tue, 20 Apr 2010 04:15:49 +0000 (20 12:15 +0800) | ||
| committer | Øyvind Harboe <oyvind.harboe@zylin.com> | |
| Sun, 16 May 2010 11:39:47 +0000 (16 13:39 +0200) | ||
| tree | 3b57db977bb18b70ba8305064b9807528374c1e3 | treesnapshot (tar.gz zip) |
| parent | 89747f81f22084b255f35d92f709facd3b4553a1 | commitdiff |
NOR/CFI: identify memory accesses not using "bus_width".
Since NOR flash devices does not handle "byte enable lanes",
each read/write access involves the whole "chip_width".
When multiple devices are in parallel, usually all chips are
enabled during each access.
All such cases are compatible with flash accesses at
"bus_width" size.
Access at "bus_width" size is mandatory for write access to
avoid transferring of garbage values to flash.
During read access the flash controller should take care,
and discard unneeded bytes. Anyway, it is good practice to
use "bus_width" size also for read.
Every memory access that does not respect "bus_width" size
is marked with a "FIXME" comment.
Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com>
Since NOR flash devices does not handle "byte enable lanes",
each read/write access involves the whole "chip_width".
When multiple devices are in parallel, usually all chips are
enabled during each access.
All such cases are compatible with flash accesses at
"bus_width" size.
Access at "bus_width" size is mandatory for write access to
avoid transferring of garbage values to flash.
During read access the flash controller should take care,
and discard unneeded bytes. Anyway, it is good practice to
use "bus_width" size also for read.
Every memory access that does not respect "bus_width" size
is marked with a "FIXME" comment.
Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com>
| src/flash/nor/cfi.c | diffblobblamehistory |