From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756668AbcBIJy2 (ORCPT ); Tue, 9 Feb 2016 04:54:28 -0500 Received: from mga14.intel.com ([192.55.52.115]:19176 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753132AbcBIJyU (ORCPT ); Tue, 9 Feb 2016 04:54:20 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,420,1449561600"; d="scan'208";a="899216801" Date: Tue, 9 Feb 2016 10:53:41 +0100 From: "Herrero, Gregory" To: Doug Anderson Cc: John Youn , Felipe Balbi , Kever Yang , =?utf-8?B?5ZC06Imv5bOw?= , Tao Huang , Heiko =?iso-8859-1?Q?St=FCbner?= , Stefan Wahren , "open list:ARM/Rockchip SoC..." , linux-rpi-kernel@lists.infradead.org, Julius Werner , "Kaukab, Yousaf" , Dinh Nguyen , Alan Stern , Ming Lei , John Youn , Greg Kroah-Hartman , "linux-usb@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v6 17/22] usb: dwc2: host: Manage frame nums better in scheduler Message-ID: <20160209095341.GA12324@herrerog> References: <1454034013-24657-1-git-send-email-dianders@chromium.org> <1454034013-24657-18-git-send-email-dianders@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Doug, > Hi, > > On Thu, Jan 28, 2016 at 6:20 PM, Douglas Anderson wrote: > > static void dwc2_qh_init(struct dwc2_hsotg *hsotg, struct dwc2_qh *qh, > > struct dwc2_hcd_urb *urb) > > { > > @@ -569,11 +655,6 @@ static void dwc2_qh_init(struct dwc2_hsotg *hsotg, struct dwc2_qh *qh, > > qh->ep_type == USB_ENDPOINT_XFER_ISOC, > > bytecount)); > > > > - /* Ensure frame_number corresponds to the reality */ > > - hsotg->frame_number = dwc2_hcd_get_frame_number(hsotg); > > In reviewing patches I realized that this is actually a revert of > commit dd81dd7c8178 ("usb: dwc2: host: use correct frame number during > qh init"). IMHO that patch was wrong: hsotg->frame_number is supposed > to be the frame number as of the last start of frame. If we need to > know a more recent frame number then we should query it ourselves. > > Presumably the reason for the original patch was to try to fix some of > the same problems I've addressed in my series, so I'd presume that > this doesn't add any new regressions. I haven't heard much from > Gregory Herrero about my series, but it would be nice to confirm that > this virtual revert wasn't causing problems. > This patch ("usb: dwc2: host: use correct frame number during qh init") is no more needed with your patchset. Note that your patchset is also reverting commit 08c4ffc: ("usb: dwc2: host: reset frame number after suspend") but it is no more needed as well with your patchset. I tried suspend/resume with different devices and didn't face the issue my previous commit was fixing. Regards, Gregory