RE: [PATCH v4 0/4]implement eMMC4.4 standard HW reset feature

[Dong, Chuanxiao]

> -----Original Message-----
> From: kyungmin78@xxxxxxxxx [mailto:kyungmin78@xxxxxxxxx] On Behalf Of
> Kyungmin Park
> Sent: Tuesday, December 07, 2010 9:34 AM
> To: Dong, Chuanxiao
> Cc: linux-mmc@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; cjb@xxxxxxxxxx;
> arjan@xxxxxxxxxxxxxxx; alan@xxxxxxxxxxxxxxx; akpm@xxxxxxxxxxxxxxxxxxxx; Mai,
> Leonard; Arnd Bergmann; Wolfram Sang
> Subject: Re: [PATCH v4 0/4]implement eMMC4.4 standard HW reset feature
> 
> On Tue, Dec 7, 2010 at 1:03 AM, Dong, Chuanxiao
> <chuanxiao.dong@xxxxxxxxx> wrote:
> > Hello all,
> > How about these patches? It implemented HW reset feature. When card
> occurred a timeout error during reading/writing/erasing, these patches will allow
> driver to reset eMMC card by trigger a HW reset signal.
> > Does anyone have any comments about the implementation of these patches?
> Wolfram and Arnd already pointed out the unsuitable patch headers. Thanks! :)
> 
> Hi,
> I'm not yet find a reason to use this feature. Now it uses the samsung
> and sandisk v4.41 but still no problem.
> I wonder what's the purpose and effect if it uses or not?

This feature will only be used when card occurs a timeout error during reading/writing/erasing.
When host send a command to card, for some reason, if card didn't have any response to host, then host controller will generate a timeout interrupt to indicate this command is timeout.
At this time, card maybe cannot response any command unless be reset. If driver did nothing at such scenario, RFC may be crashed. So I think when timeout error occurs, reset card is needed.
Host sends CMD0 also can reset the card, but card may be dead and cannot response any command. So this patch will pull up a GPIO line to trigger a reset signal and let eMMC card reset itself, not send a command to do that.
That is my understanding of this feature.

Thanks
Chuanxiao
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/