On Wed, Nov 30, 2011 at 4:36 AM, Ohad Ben-Cohen <ohad@xxxxxxxxxx> wrote: > Hi Daniel, > > On Tue, Nov 29, 2011 at 11:42 PM, Daniel Drake <dsd@xxxxxxxxxx> wrote: >> Even though I have the pleasure of working with 8686 quite a bit > > (Is there a subtle cynicism here ? :) > >> So first thing to do is to investigate the source of this error, as before: >> [ 34.637481] libertas_sdio: probe of mmc1:0001:1 failed with error -16 >> >> which is likely bubbling up from somewhere inside the mmc/sdio layer. > > Well, it sounds like Joe might need a hand here. I can't reproduce it. My suggestion is to follow the debugging steps from previous threads on this topic such as MMC runtime PM patches break libertas probe The goal is to identify the line of code that is causing this error. Use printk debugging in the codepaths mentioned earlier until the point of failure is known. Let me know if further direction is needed. > Since this regression is directly caused by commit 08da834 "mmc: > enable runtime PM by default", which you authored and have interest > in, it does make sense that you help Joe here. In case you're short of > time, then I suggest to revert 08da834 (which anyway was > experimental), and get back to it later, when you're more available. My patch simply sets a flag to enable a whole load of code written by you - code which I understand little about. I am now available to help, but given that my understanding of mmc is limited, I didn't write the code in question, and I also lack expert insight into 8686 powerup, I'm not sure how useful I can be. Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
