diff options
| author | Marcel Ziswiler <marcel@ziswiler.com> | 2014-10-04 01:48:53 +0200 |
|---|---|---|
| committer | Tom Warren <twarren@nvidia.com> | 2014-10-22 09:30:54 -0700 |
| commit | 09fb73611ff8c247f7196a8e4f957d8696930b69 (patch) | |
| tree | 9b9128098d390ba27d640c5ba8d86b845df0b2a0 /doc/README.JFFS2_NAND | |
| parent | 4270d5afed2e815b8c8dd917a8083644b0ccdede (diff) | |
| download | u-boot-imx-09fb73611ff8c247f7196a8e4f957d8696930b69.zip u-boot-imx-09fb73611ff8c247f7196a8e4f957d8696930b69.tar.gz u-boot-imx-09fb73611ff8c247f7196a8e4f957d8696930b69.tar.bz2 | |
mmc: Tegra: Fix timeout issue seen on certain eMMC parts
During rigorous testing of our latest update infrastructure I came
across quite consistent timeouts on certain eMMC parts (e.g. Hynix
H26M21001ECR) when writing big (e.g. in excess of 400 MB) file system
images:
MMC write: dev # 0, block # 40960, count 944128 ...
mmc_send_cmd_bounced: MMC Timeout
Interrupt status 0x00000001
Interrupt status enable 0xdfff003b
Interrupt signal enable 0xdfff0002
Present status 0x01870106
mmc write failed
Comparing the various data sheets I came across the following timeout
specification:
Secure Erase/TRIM Timeout=300ms*2*10=6000ms
Unfortunately empirical testing still failed albeit much more rarely.
Increasing the timeout to 8000ms made it finally disappear entirely.
This patch allows us writing various eMMC parts without seeing any
further issues.
Signed-off-by: Marcel Ziswiler <marcel@ziswiler.com>
Signed-off-by: Tom Warren <twarren@nvidia.com>
Diffstat (limited to 'doc/README.JFFS2_NAND')
0 files changed, 0 insertions, 0 deletions