From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: MUSB peripheral DMA regression caused by driver core runtime PM change Date: Wed, 21 Oct 2015 16:41:34 -0700 Message-ID: <20151021234134.GQ3078@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline Sender: linux-usb-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Felipe Balbi Cc: Bin Liu , "Rafael J. Wysocki" , Heikki Krogerus , Andy Shevchenko , Lee Jones , linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: linux-omap@vger.kernel.org Hi all, I noticed a regresssino in v4.3-rc series to day with MUSB gadgets and DMA. Doing a git bisect between v4.2..v4.3-rc1 on it pointed to: ddef08dd00f5 ("Driver core: wakeup the parent device before trying probe") With the commit above reverted things work fine with DMA and USB gadgets. This is on omap3 with CONFIG_USB_INVENTRA_DMA selected. Selecting CONFIG_MUSB_PIO_ONLY still works even without reverting ddef08dd00f5. Anybody got ideas what might be wrong? Some wrong runtime PM usage under drivers/usb/musb? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html