Seeing something similar but the details are a little different.  My kernel is 
somewhat old but ...
Seeing this with sd card and android.
card is removed/inserted/removed/inserted etc very quickly during power 
operations.  After 20-30 times
a problem occurs.  this can be anything from file system errors, partition not 
recognized or a kernel hang.

My thought is this is not a quirk issue but power down needs to be delayed 
during the power up
sequence until processing has been completed in the mmc layer.  Any thoughts on 
how to 
debug this would be welcome.  When the hang happens the system is not dead (as 
in 
console output showing card insert/remove still happens but console is locked 
etc.

thanks,

Philip

I do not think a quirk is the answer.  
On Jun 16, 2011, at 10:27 AM, Daniel Drake wrote:

> On 13 June 2011 20:52, Ohad Ben-Cohen <o...@wizery.com> wrote:
>> We need to debug the suspend/resume path. Now that we have the other
>> runtime pm paths working, we can pretty much tell there's no hw issue
>> at hand.
> 
> Found it. It's a timing issue. In our other tests we had not yet hit
> the case when power is removed then immediately restored.  However,
> during resume, the card is powered up, powered down, powered up, and
> then probed by libertas.
> 
> A msleep(250) is needed during power_restore. Then the reset works fine.
> 
> Why is there so much power flipping going on during resume? Is this a
> bug? Shouldn't it power it up, realise it has a driver already loaded,
> and go straight into probe?
> 
> But even if that gets fixed, we still need to fix the case where the
> network interface is brought down then up immediately (another way to
> trigger the issue). Would you suggest a card quirk for that? Adding
> another 250ms to the already-slow libertas powerup routine would be a
> bit painful, would you support the added complexity needed to make the
> 250ms delay only occur when >250ms has passed since it was powered
> off?
> 
> Thanks,
> Daniel
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to