Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp695726pxj; Thu, 13 May 2021 14:52:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx7EIWL2uYfmwHmNnMNJ6OmCy2NsKp7KFIDFg+TILV3a8nUVaoFspO1lBgwMCMeUtNmy9dT X-Received: by 2002:a17:906:90cf:: with SMTP id v15mr46110719ejw.432.1620942772535; Thu, 13 May 2021 14:52:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620942772; cv=none; d=google.com; s=arc-20160816; b=cWFGGqkXG2OGpqIeKO2A7sSwaWl4dmJaXNThcMwPyfzVlL41OtIDOO7McFRp7pHMc4 mbrx7f4y9VenOEmMLVaycV3S1wYE3Q3Eu+nxeZzQSH4PUTbfSxsyBXVQyc5iCKL+Yxff bRl7x/M4bto9Y6/shQb4xcHDsvrfP1PsAmKuQnsExRY1z8AzQ8w47MAfOsgSP+MwE6tT k++pr3iPQbudl6W6r2Gi5pZ63YJ8roOoVXCuqUt6H5ENbq6AE9G8CS7xCqf1FLYof70h lz5NmtQA7jkx7PolozBftCsli/fKoq/1Vnxn7i/kh6icuwHRuXisEopcIofheDOa8pFx mnHA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=MJeKFm4a4n/nrh9ml2ikBZMqqZTRKdwyamt9KAt3ijo=; b=JWrqBo9IWcbfLUnCKqmq2pGc9oWuCEXJSp3xGbsLVTkDerGi6kDS2FrnavrtgaB4N9 YGwdO5whOU8zMmOoawSfLQ+93C80Qg2Df4VLzNUcpUeF0RnEL1UL0V+X3znFx3ouhbxH 4my0baMWO5fNe9wSk5XVYlBqoLOvID3Bxhjn068JdmwjnBHo1xVJb2zCsgfuuDSmlN5N Rmu+crhLMPazF1H33PRuM6yIsL9fSvgqm3cEJvc5ZjMZvr+oyrwn/sOVeIvCIyLlADfU YgAh2PuVCnI+b9tSZs3I9sC1LEVXMuk2yZwC9OsCiff6oOkyTsnOhhnOvRfFqmNIw0tW F1pg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dd6si4131509ejb.639.2021.05.13.14.52.28; Thu, 13 May 2021 14:52:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234550AbhEMOgt (ORCPT + 99 others); Thu, 13 May 2021 10:36:49 -0400 Received: from netrider.rowland.org ([192.131.102.5]:51319 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S234496AbhEMOgk (ORCPT ); Thu, 13 May 2021 10:36:40 -0400 Received: (qmail 968704 invoked by uid 1000); 13 May 2021 10:35:29 -0400 Date: Thu, 13 May 2021 10:35:29 -0400 From: Alan Stern To: chris.chiu@canonical.com Cc: gregkh@linuxfoundation.org, m.v.b@runbox.com, hadess@hadess.net, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 1/2] USB: Verify the port status when timeout happens during port suspend Message-ID: <20210513143529.GD967812@rowland.harvard.edu> References: <20210513041446.3082-1-chris.chiu@canonical.com> <20210513041446.3082-2-chris.chiu@canonical.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210513041446.3082-2-chris.chiu@canonical.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 13, 2021 at 12:14:45PM +0800, chris.chiu@canonical.com wrote: > From: Chris Chiu > > On the Realtek high-speed Hub(0bda:5487), the port which has wakeup > enabled_descendants will sometimes timeout when setting PORT_SUSPEND > feature. After checking the PORT_SUSPEND bit in wPortStatus, it is > already set. However, the hub will fail to activate because the > PORT_SUSPEND feature of that port is not cleared during resume. All > connected devices are lost after resume. The last two sentences of this paragraph are now inaccurate. Please fix them up to match the current patch version. > Check the port status to verify whether it's really suspended when > timeout happpens. If yes, mark it as suspended so the device can > be resumed correctly. > > Signed-off-by: Chris Chiu > --- > > Changelog: > v3: > - create a new goto target for the timeout case instead of > reset_resume > - Revise the commit title/message because reset_resume is not > required. > v2: > - create a new variable to keep the result of hub_port_status > when suspend timeout. > > drivers/usb/core/hub.c | 16 ++++++++++++++++ > 1 file changed, 16 insertions(+) > > diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c > index b2bc4b7c4289..c5d64175eaa9 100644 > --- a/drivers/usb/core/hub.c > +++ b/drivers/usb/core/hub.c > @@ -3385,6 +3385,21 @@ int usb_port_suspend(struct usb_device *udev, pm_message_t msg) > status = 0; > } > if (status) { > + if (status == -ETIMEDOUT) { > + u16 portstatus, portchange; > + Extra blank line. > + int ret = hub_port_status(hub, port1, &portstatus, > + &portchange); > + > + dev_dbg(&port_dev->dev, > + "suspend timeout, status %04x\n", portstatus); The portstatus value shouldn't be printed if ret < 0, because it won't be initialized. If you want, initialize portstatus to 0 in the declaration. Also, there should be a comment here explaining why this code is needed. It should say pretty the same thing as the patch description, but more briefly (two sentences should be sufficient). Alan Stern > + > + if (ret == 0 && port_is_suspended(hub, portstatus)) { > + status = 0; > + goto suspend_done; > + } > + } > + > dev_dbg(&port_dev->dev, "can't suspend, status %d\n", status); > > /* Try to enable USB3 LTM again */ > @@ -3401,6 +3416,7 @@ int usb_port_suspend(struct usb_device *udev, pm_message_t msg) > if (!PMSG_IS_AUTO(msg)) > status = 0; > } else { > + suspend_done: > dev_dbg(&udev->dev, "usb %ssuspend, wakeup %d\n", > (PMSG_IS_AUTO(msg) ? "auto-" : ""), > udev->do_remote_wakeup); > -- > 2.20.1 >