All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] mmc: sdhci: increase the timeout value for data transfer
Date: Mon, 24 Sep 2012 10:32:55 +0900	[thread overview]
Message-ID: <505FB847.7020707@samsung.com> (raw)
In-Reply-To: <loom.20120921T113549-684@post.gmane.org>

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 <jh80.chung <at> 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
> 

  reply	other threads:[~2012-09-24  1:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21  6:31 [U-Boot] [PATCH 1/3] mmc: sdhci: increase the timeout value for data transfer Jaehoon Chung
2012-09-21  9:48 ` Rommel Custodio
2012-09-24  1:32   ` Jaehoon Chung [this message]
2012-09-24  2:34     ` Rommel Custodio
2012-09-24  5:23       ` Jaehoon Chung
2012-09-24 19:57         ` Mela Custodio
2012-09-25  1:33           ` Jaehoon Chung

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=505FB847.7020707@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.