On Sat, Nov 6, 2010 at 11:19 PM, Daniel Drake <dsd@xxxxxxxxxx> wrote: > Thanks. > It solves the problem. Good. Did it also solve the 1st issue you had ? Anyway I'm still interested to reproduce that crash. No reason to get a kernel panic whatsoever. > > But, what you point out is quite interesting. > We currently have a (not-yet-upstream) rfkill driver for the XO-1.5, > which we also put in place for power saving reasons. Can you please elaborate ? What power saving ? How do you exactly plan to use it ? Do you plan to power off the card without taking the wlan interface down first ? > It operates by > calling mmc_stop_host(). In light of your work, I guess that wasn't > really turning off the card. Sounds like it. Chris and I briefly discussed this in LPC, and he mentioned that you might have an external power source to that card, that is not controlled by the mmc regulator, and which you disable/enable from user space just before suspending the host ? > > So, it would be great if you could get runtime PM working on this > combo, and then later we could make a real rfkill driver. The XO-1.5 problem is orthogonal to runtime PM. If your regulator really powered down your card, then everything would just have worked. > > I guess you have an XO-1.5 now. I'm happy to help you get started, I > guess this is your first time working with an XO. Drop by irc.oftc.net > #olpc-devel and I'll happily help you get started booting your own > kernel etc. Thanks. This would allow me to test generic core code on a platform which is completely different from those I have. Thanks, Ohad. > > Thanks! > 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
