[U-Boot] Nokia N900 - eMMC not working after commit 02f3029f1810b99869254d0cf0a71946a008a728

[Lei Wen]

Hi Macpaul,

On Mon, Nov 14, 2011 at 2:14 PM, Macpaul Lin <macpaul at gmail.com> wrote:
> HI Lei Wen,
>
> 2011/11/12 Macpaul Lin <macpaul at gmail.com>:
>> Hi Lei Wen,
>>
>> 2011/11/12 Lei Wen <adrian.wenl at gmail.com>:
>>> Hi Pali,
>>>
>> I have got 3 times retry fail on CMD8 also with FTSDC010 in recent, too.
>> But I'm not sure where the problem is and hasn't start to check bisect
>> with the commits.
>> It works really fine before.
>> That's why I asked Andy to stop review the performance improvement of FTSDC010.
>> Maybe we'll need to check it again where the affect is started.--
>> Best regards,
>> Macpaul Lin
>>
>
> I have done the testing of the commit related to mmc generic stack of
> Lei Wen's commit.
> The problem indeed occur when we add 3 retry to CMD8.
> After reverting this patch with the origin ftsdc010 driver (which is
> in master branch alredy),
> all works fine again.
>
> The following is the command flow with origin mmc stack.
> When I'm using card which version is SD 1.10, the CMD8 will timeout
> directly then card identification will continue.
>
> cmd 0
> cmd: 8
> ftsdc010_pio_check_status: RSP timeout: sta: 00000004 cmd 8
> cmd: 55
> cmd: 41
> cmd: 55...
>
> If we add 3 retry to CMD8, the card will reply timeout 3 times than stop.
> It won't go to CMD55.
> cmd: 0
> cmd: 8
> ftsdc010_pio_check_status: RSP timeout: sta: 00000404 cmd 8
> cmd: 8
> ftsdc010_pio_check_status: RSP timeout: sta: 00000404 cmd 8
> cmd: 8
> ftsdc010_pio_check_status: RSP timeout: sta: 00000404 cmd 8
>
>
I see...
It seems some socs always treat cmd8 as failed...?
I think it is reasonable to add a quirk configuration surround the judgement
of cmd8 execution, so that even it is failed anyway, it could still go on with
the following cmd sequence. If this quirk is not defined, and return behavior
is still kept.

What do you think for this?

Thanks,
Lei