From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCHv2 00/15] Get MUSB PM runtime working again Date: Tue, 17 May 2016 14:54:04 -0700 Message-ID: <20160517215403.GP5995@atomide.com> References: <1463014396-4095-1-git-send-email-tony@atomide.com> <20160517211541.GA30701@uda0271908> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20160517211541.GA30701@uda0271908> Sender: linux-usb-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Bin Liu , Felipe Balbi , Kishon Vijay Abraham I , Ivaylo Dimitrov , Sergei Shtylyov , linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-omap@vger.kernel.org * Bin Liu [160517 14:17]: > Hi Tony, > > On Wed, May 11, 2016 at 05:53:01PM -0700, Tony Lindgren wrote: > > Hi all, > > > > Here's the whole series reposted with a bunch of additional changes. > > It seems to now properly work with with multiple phy cable status > > events, and should work for Ivaylo on n900 too. > > > > Please re-review and re-test. > > While trying to test this patch set, I just found that commit 56f487c (PM > / Runtime: Update last_busy in rpm_resume) breaks dsps glue (TI am335x > device). Do you have an am335x board with has otg port on it to take a > look at this problem? The only board I know of which has an otg port is > TI am335x GP evm. Hmm sure I can take a lok. Chances are that just doing a change for s/pm_runtime_put/pm_runtime_put_sync/ will fix it. I'm wondering why it breaks though as dsps glue does not use autosuspend? It could also be a case where the parent and child PM runtime use counts get out of sync? BTW, I did give my series a quick try here on j5eco-evm and that behaved for peripheral and host enumeration. It's pretty much the same setup as on am335x I believe. 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