From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jaehoon Chung Date: Mon, 24 Sep 2012 10:32:55 +0900 Subject: [U-Boot] [PATCH 1/3] mmc: sdhci: increase the timeout value for data transfer In-Reply-To: References: <505C09DA.8030102@samsung.com> Message-ID: <505FB847.7020707@samsung.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Rommel, I didn't think so..Our environment is support the CONFIG_SYS_MMC_MAX_BLK_COUNT. Did you know how get the timeout value "1000"? If the timeout value "1000" is reasonable, i want to know what basis. Well, i don't think that my timeout value is reasonable. Actually i want to remove the timeout value in that function. But then we should be prevent the infinite loop. Anyway, thanks for your comment. I will check the your opinion. Best Regards, Jaehoon Chung On 09/21/2012 06:48 PM, Rommel Custodio wrote: > > Jaehoon Chung samsung.com> writes: > >> >> Timeout value is tunable. >> When run read/write operation, sometime returned the timeout error. >> Because the timeout value is too short. > > Hello, > > I think it is better to fine tune CONFIG_SYS_MMC_MAX_BLK_COUNT. > This gets assigned to mmc->b_max, unless you specifically set > mmc->b_max value during mmc_register(). > > b_max is important since when you adjust b_max properly, > mmc_bread() and mmc_bwrite() will properly partition the > read/write operation (in b_max blocks) so that the timeout > does not occur. > > All the best, > Rommel > > (replying via gmane since i just joined the list) > > > _______________________________________________ > U-Boot mailing list > U-Boot at lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot >