24 May
2012
24 May
'12
5:34 p.m.
On Thursday 24 May 2012, John Stultz wrote:
Yep. Good call, that's the one! Reverting it works for me. Thanks for catching that. After a few hours of bisecting I had gone a bit braindead. :)
Playing around with the patch, it looks like its the irq assignment thats causing problems (twl6030_mmc_card_detect_config() is returning 368). I can work around it with the hack below.
Balaji: Any thoughts on a proper fix here?
It sounds like the probe function of that driver should be changed to return -EPROBEDEFER instead of -EINVAL for this case, so we can retry the probe when the interrupt number becomes available.
Arnd