public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Rommel Custodio <sessyargc+uboot@gmail.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 02:34:31 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120924T041306-650@post.gmane.org> (raw)
In-Reply-To: 505FB847.7020707@samsung.com

Hello Jaehoon,

> I didn't think so..Our environment is support the
> CONFIG_SYS_MMC_MAX_BLK_COUNT.

This is defined in mmc.c right after the include definitions.
The comment says that:
  Set block count limit because of 16 bit
  register limit on some hardware

So my use of this define is a bit of a hack too.


> 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.

I think timeout value was from original creator/maintainer
of SD/MMC code.

When trying to read big data off of the SD card, I get the
timeout too on my platform (ml507). My test consist of reading
a 26Mb file from the SD card in PIO and DMA mode.

When the timeout is displayed in the serial console, the block
count register is not yet zero but there is no error in the
interrupt status register. The block count value shows the
same value when I perform the same test.

For my use, CONFIG_SYS_MMC_MAX_BLK_COUNT = 0x1000 in my
environment. I did not modify any of the timeout values.


> 
> Actually i want to remove the timeout value in that function.
> But then we should be prevent the infinite loop.

The infinite loop that you mention does not occur in my
situation.

> 
> Anyway, thanks for your comment. I will check the your opinion.

HTH

(replying via gmane since i just joined the list)

  reply	other threads:[~2012-09-24  2:34 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
2012-09-24  2:34     ` Rommel Custodio [this message]
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=loom.20120924T041306-650@post.gmane.org \
    --to=sessyargc+uboot@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox