Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp6360015yba; Thu, 11 Apr 2019 18:25:15 -0700 (PDT) X-Google-Smtp-Source: APXvYqwXszDSu1DwYa5r0obLZGH1UHAM/ud7fxdq/BjftXGHoS+nhtDHeQn45TvH/OZ+Kv2UBFek X-Received: by 2002:a62:e418:: with SMTP id r24mr53712585pfh.52.1555032315019; Thu, 11 Apr 2019 18:25:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555032315; cv=none; d=google.com; s=arc-20160816; b=c9+KN684KNqIBwvhNdkEBLZAXnVFdiPZr4JyBsMa++NcegE/sl823H9jIPH1jHLm7+ NubC4a90ZFzuqjHnmGOQ+usF4JUxrtCbsEe6ghRmAEh3M35vdn/Di69BfnraaINIx98Q pMXnGwZjGBCQb4iDHqeH6EbZPsTJ2IPUGl6opQu/bsE3Kf4NywaI1cX7ZtziR5QzSc9l mwumajnWT9Bc6gV8IbXqMfk1C07Biylt2BQKk0xYrJqMlhWtuROKdyvIoDWFNPB/JV6q o3mbTfELI7JcGoJjkdwuBiCDyp7CUC+T4cYd5bGkwAJuS+goBulKclnZiLm6d1ImzNoQ STbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject:cc; bh=VtnSnDYPEJdtgVxf8WCncy2lney0ILzYBERghGkOObA=; b=sSuDu9bFRzCxRwbVsPrwyhzFF7tzr611k6PdUFDQtI5wFjow7sWQBGDKB+dqv8MhiA OfHtKrkJchOfsCfo32+xfJar10XO4Ne5sU51VKNbHZMH6HEuD/fOk1wWusZaiJ0WRaC7 ktYYB26MXm850XZ44qTOrx6SJPe7uFZcIimVuvDldqQOQ7TLs4e9jMif9InakVqyKqR+ X4f3d0FzZMxQn9gdMTkCytAEQZ+eDa6Qq96HBKFb+mDKoZO7FsumCHAjamA9JOpT6mnN iJ5NlhR05blubbsC15Lsgeh8ZkY/yPBKQj+v1jKm3pQc9jHm2Tg1d11+oznFxsnQipVI oMyA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w11si26702336plz.403.2019.04.11.18.24.59; Thu, 11 Apr 2019 18:25:14 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726851AbfDLBX4 (ORCPT + 99 others); Thu, 11 Apr 2019 21:23:56 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:6168 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726636AbfDLBXz (ORCPT ); Thu, 11 Apr 2019 21:23:55 -0400 Received: from DGGEMS414-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id C91B793732090A697CCC; Fri, 12 Apr 2019 09:23:53 +0800 (CST) Received: from [127.0.0.1] (10.142.63.192) by DGGEMS414-HUB.china.huawei.com (10.3.19.214) with Microsoft SMTP Server id 14.3.408.0; Fri, 12 Apr 2019 09:23:44 +0800 CC: , Linux USB List , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , lkml , "Zhuangluan Su" , Kongfei , , butao , , , Li Pengcheng , , YiPing Xu , , Yudongbin , Zang Leigang , Jun Li , Valentin Schneider , Felipe Balbi , Greg Kroah-Hartman , Heikki Krogerus Subject: Re: [PATCH v5 10/13] usb: dwc3: Registering a role switch in the DRD code. To: John Stultz References: <20190329041409.70138-1-chenyu56@huawei.com> <20190329041409.70138-11-chenyu56@huawei.com> From: Chen Yu Message-ID: <7d5ba117-735e-3fb0-97f7-33be328a4ae6@huawei.com> Date: Fri, 12 Apr 2019 09:23:42 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.142.63.192] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi John, On 2019/4/12 8:48, John Stultz wrote: > On Thu, Mar 28, 2019 at 9:14 PM Yu Chen wrote: >> >> The Type-C drivers use USB role switch API to inform the >> system about the negotiated data role, so registering a role >> switch in the DRD code in order to support platforms with >> USB Type-C connectors. >> > > Hey Yu Chen! > Thanks so much for sending these patches out! I have run into some > troubles on bootup where things aren't working properly at first, that > seem to be due to state initialization races. In chasing those down, > I've found some other quirks I wanted to bring up. > >> --- a/drivers/usb/dwc3/drd.c >> +++ b/drivers/usb/dwc3/drd.c >> @@ -479,6 +479,43 @@ static struct extcon_dev *dwc3_get_extcon(struct dwc3 *dwc) >> return edev; >> } >> >> +static int dwc3_usb_role_switch_set(struct device *dev, enum usb_role role) >> +{ >> + struct dwc3 *dwc = dev_get_drvdata(dev); >> + u32 mode; >> + >> + switch (role) { >> + case USB_ROLE_HOST: >> + mode = DWC3_GCTL_PRTCAP_HOST; >> + break; >> + case USB_ROLE_DEVICE: >> + mode = DWC3_GCTL_PRTCAP_DEVICE; >> + break; >> + default: >> + if (dwc->role_switch_default_mode == USB_DR_MODE_HOST) >> + mode = DWC3_GCTL_PRTCAP_HOST; >> + else >> + mode = DWC3_GCTL_PRTCAP_DEVICE; >> + break; >> + } >> + >> + dwc3_set_mode(dwc, mode); >> + return 0; >> +} >> + >> +static enum usb_role dwc3_usb_role_switch_get(struct device *dev) >> +{ >> + struct dwc3 *dwc = dev_get_drvdata(dev); >> + unsigned long flags; >> + enum usb_role role; >> + >> + spin_lock_irqsave(&dwc->lock, flags); >> + role = dwc->current_otg_role; >> + spin_unlock_irqrestore(&dwc->lock, flags); >> + >> + return role; >> +} >> + > > So the two functions above are a bit asymmetric. The > dwc3_usb_role_switch_set() can put the device into host or device > mode, which eventually sets the current_dr_role value. However on the > dwc3_usb_role_switch_get() we return the current_otg_role value. > current_otg_role isn't set unless current_dr_role is > DWC3_GCTL_PRTCAP_OTG, which doesn't seem to happen here. > > I suspect in dwc3_usb_role_switch_get() we should return > current_dr_role, unless current_dr_role==DWC3_GCTL_PRTCAP_OTG, in > which case we'd want to return current_otg_role. > > Does that make sense? > Yes, you are right! The dwc3_usb_role_switch_get() should return current_dr_role . Actually if we register the dwc3_role_switch, the current_dr_role would not be DWC3_GCTL_PRTCAP_OTG. > Nothing really actually use this dwc3_usb_role_switch_get() yet, so > this was easy to overlook, and I only caught it as I was trying to > debug some of the initialization races. > > thanks > -john > > . >