Felipe, On Fri, Aug 12, 2011 at 9:40 AM, Pandita, Vikram <vikram.pandita@xxxxxx> wrote: > > On Fri, Aug 12, 2011 at 6:55 AM, Pandita, Vikram <vikram.pandita@xxxxxx> wrote: > > On Fri, Aug 12, 2011 at 2:01 AM, Felipe Balbi <balbi@xxxxxx> wrote: > >> Hi, > >> > >> (sorry for top-posting) > >> > >> Moiz, are we going to have another set of this ? > > > > The problem was with pm_runtime() functions getting called from atomic > > context and we did a work around by calling the runtime functions from > > a work queue. > > That seems to fix the issue. We will post that out as an alternative > > to marking the irq_safe and thus causing the parent to never idle. > > > > Here is the new post: > https://patchwork.kernel.org/patch/1061282/ The patch was posted because of the runtime calls inside musb_gadget_pullup() within interrupt-disable context. This was actually fixed by syncing with a patch in open-source whering actually these calls were done outside the irq_save() calls. https://lkml.org/lkml/2011/7/20/357 Similar problem was also for the run-time pm calls done from the musb_otg_notifications() which is in atomic context. This has been fixed by Vikrams patch. > > [.....] > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Regards Moiz Sonasath Android Kernel Team -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
