Re: [U-Boot] [PATCH] mmc:sdhci: Fix card ready status timeout.

2013-09-16 Thread Pantelis Antoniou
Hi there, On Sep 13, 2013, at 3:59 PM, Przemyslaw Marczak wrote: > Dear Pantelis, > > On 09/09/2013 02:58 PM, Przemyslaw Marczak wrote: >> According to JEDEC eMMC specification, after data transfer >> (multiple or single block) host must wait for card ready >> status. This is done by waiting for

Re: [U-Boot] [PATCH] mmc:sdhci: Fix card ready status timeout.

2013-09-13 Thread Przemyslaw Marczak
Dear Pantelis, On 09/09/2013 02:58 PM, Przemyslaw Marczak wrote: According to JEDEC eMMC specification, after data transfer (multiple or single block) host must wait for card ready status. This is done by waiting for command and data lines to be at idle state after transfer. JEDEC does not speci

[U-Boot] [PATCH] mmc:sdhci: Fix card ready status timeout.

2013-09-09 Thread Przemyslaw Marczak
According to JEDEC eMMC specification, after data transfer (multiple or single block) host must wait for card ready status. This is done by waiting for command and data lines to be at idle state after transfer. JEDEC does not specify maximum timeout. Before this change max timeout was 10 ms but in

Re: [U-Boot] [PATCH] mmc:sdhci: Fix card ready status timeout.

2013-09-06 Thread Pantelis Antoniou
Hi there, On Sep 6, 2013, at 6:23 PM, Przemyslaw Marczak wrote: > Hello Pantelis, > > > On 09/06/2013 03:24 PM, Pantelis Antoniou wrote: >> Hi there, >> >> Can we have a config option for these two values instead of magic numbers? >> >> With the defaults being set at 10 & 200 ms. >> >> Regard

Re: [U-Boot] [PATCH] mmc:sdhci: Fix card ready status timeout.

2013-09-06 Thread Przemyslaw Marczak
Hello Pantelis, > On 09/06/2013 03:24 PM, Pantelis Antoniou wrote: Hi there, Can we have a config option for these two values instead of magic numbers? With the defaults being set at 10 & 200 ms. Regards -- Pantelis I'm not sure that this option is needed. Some cards I/O errors can be avo

Re: [U-Boot] [PATCH] mmc:sdhci: Fix card ready status timeout.

2013-09-06 Thread Pantelis Antoniou
Hi there, On Sep 3, 2013, at 3:50 PM, Przemyslaw Marczak wrote: > According to JEDEC eMMC specification, after data transfer > (multiple or single block) host must wait for card ready > status. This is done by waiting for command and data lines > to be at idle state after transfer. JEDEC does not

[U-Boot] [PATCH] mmc:sdhci: Fix card ready status timeout.

2013-09-03 Thread Przemyslaw Marczak
According to JEDEC eMMC specification, after data transfer (multiple or single block) host must wait for card ready status. This is done by waiting for command and data lines to be at idle state after transfer. JEDEC does not specify maximum timeout. Before this change max timeout was 10 ms but in

Re: [U-Boot] [PATCH] mmc:sdhci: Fix card ready status timeout.

2013-09-02 Thread Przemyslaw Marczak
On 08/29/2013 05:16 AM, Jaehoon Chung wrote: Hi Przemyslaw, Could you give me the test-case? I want to test this problem. On 08/29/2013 01:49 AM, Przemyslaw Marczak wrote: According to JEDEC eMMC specification, after data transfer (multiple or single block) host must wait for card ready status

Re: [U-Boot] [PATCH] mmc:sdhci: Fix card ready status timeout.

2013-08-28 Thread Jaehoon Chung
Hi Przemyslaw, Could you give me the test-case? I want to test this problem. On 08/29/2013 01:49 AM, Przemyslaw Marczak wrote: > According to JEDEC eMMC specification, after data transfer > (multiple or single block) host must wait for card ready > status. This is done by waiting for command and

[U-Boot] [PATCH] mmc:sdhci: Fix card ready status timeout.

2013-08-28 Thread Przemyslaw Marczak
According to JEDEC eMMC specification, after data transfer (multiple or single block) host must wait for card ready status. This is done by waiting for command and data lines to be at idle state after transfer. JEDEC does not specify maximum timeout. Before this change max timeout was 10 ms but in