Any more feedback on this? I don't mind having to maintain my own patch to revert the change to core/host.c to disable runtime PM, but I'm a bit concerned by the commit comment: "... Enable this trivially for a release or two. If no problems are reported, we will follow up with a more extensive patch to remove this flag altogether. If problems are reported, we can look at whitelist/blacklist possibilities as before." Certainly for my use case I'd appreciate keeping this flag around! Cheers, Joe -----Original Message----- From: Ohad Ben-Cohen <ohad@xxxxxxxxxx> To: Joe Woodward <jw@xxxxxxxxxxxxxx> Cc: Daniel Drake <dsd@xxxxxxxxxx>, linux-mmc@xxxxxxxxxxxxxxx Date: Fri, 18 Nov 2011 14:15:03 +0200 Subject: Re: mmc: sdio: runtime PM and 8686 problems > On Fri, Nov 18, 2011 at 12:00 PM, Joe Woodward <jw@xxxxxxxxxxxxxx> > wrote: > > I'm assuming these changes have already made it to the mainline, and > therefore are in the 3.2rc2 build I was testing... > > Most probably, yeah. > > > Is there anything I can do to debug further the problems I'm seeing? > > Let's wait for Daniel to take a look, as he got libertas and sd8686 > working with SDIO runtime PM. > -- > 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 -- 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
