diff options
| author | Prabhakar Kushwaha <prabhakar@freescale.com> | 2012-09-12 22:26:05 +0000 |
|---|---|---|
| committer | Scott Wood <scottwood@freescale.com> | 2012-11-26 15:41:28 -0600 |
| commit | 79da5e3d5d6be28d1c82265bbeb0ff4633fc5535 (patch) | |
| tree | 12b4f4e349b1e6d638e30116cf290d8ac7d4bd5a /arch/m68k/lib/traps.c | |
| parent | 10635afa5371a4ab7bfae949dd9bbcbb62cf0f95 (diff) | |
| download | u-boot-imx-79da5e3d5d6be28d1c82265bbeb0ff4633fc5535.zip u-boot-imx-79da5e3d5d6be28d1c82265bbeb0ff4633fc5535.tar.gz u-boot-imx-79da5e3d5d6be28d1c82265bbeb0ff4633fc5535.tar.bz2 | |
driver/mtd:IFC NAND:Initialise internal SRAM before any write
IFC-1.1.0 uses 28nm techenology for SRAM. This tech has known limitaion for
SRAM i.e. "byte select" is not supported. Hence Read Modify Write is
implemented in IFC for any "system side write" into sram buffer. Reading an
uninitialized memory results in ECC Error from sram wrapper.
Hence we must initialize/prefill SRAM buffer by any data before writing
anything in SRAM from system side. To initialize SRAM user can use "READID"
NAND command with read bytes equal to SRAM size. It will be a one time
activity post boot
Signed-off-by: Prabhakar Kushwaha <prabhakar@freescale.com>
[scottwood@freescale.com: fix fsl_ifc_sram_init prototype]
Signed-off-by: Scott Wood <scottwood@freescale.com>
Diffstat (limited to 'arch/m68k/lib/traps.c')
0 files changed, 0 insertions, 0 deletions