From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 69D85ECAAD3 for ; Wed, 31 Aug 2022 16:38:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232257AbiHaQil (ORCPT ); Wed, 31 Aug 2022 12:38:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59592 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229587AbiHaQi3 (ORCPT ); Wed, 31 Aug 2022 12:38:29 -0400 Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 72BBED7D20 for ; Wed, 31 Aug 2022 09:38:28 -0700 (PDT) Received: by mail-pj1-x1032.google.com with SMTP id p8-20020a17090ad30800b001fdfc8c7567so3738777pju.1 for ; Wed, 31 Aug 2022 09:38:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gateworks-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=OaCyZzLvcCpsyTCEH1A5MS9EZVvRVfWIIgcRnBjIWNQ=; b=qIKKi3mMHcII/hptopT7BPHoIw7FFlwg4NC8lfWdKaKsPIQJdXj+RH5gDdBK1LWVan seOvLPJrVW96WV2gHcnNFHxjPCkPmP7RffnD3BP0Pwf1w3mXK8Za3UItXcazf3hPU1x5 JgUOecmjIXsajFKqKeWQm4Mnkck57YXp11dCXez4Jr7dQo6cdwgcHf3OOW8jPBrTuieO HXUAA7xy+nbzbJM7BGF6/tqKBEHESPFvtW7hGrZBpuPUQQX+bdEv+qeYMtvX8b4OUiw+ 1WSjsIvXvIDqCQ3L42aNS4g75ZqEumYMaj9P9Pg+/JR1cA/Dhml3cq0nRi3lF0xiXz0L obfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=OaCyZzLvcCpsyTCEH1A5MS9EZVvRVfWIIgcRnBjIWNQ=; b=VVjDYdIe5kkf0S03H4q1W30XghFZ8VX8H7ZL2zKg20y01tu1n/FXcxblJ7r/CrwPYO pFrcky6iTA98Up/V8LMHndkXiWA+sgisFQ7PvU/JKlhV+rt6gJhKJaHqphJF2gSz7JLM PpBSvN6wZBafqR5owg2Uxhli1ZHruz5ewSFQuTi/o7L2eCY6biusglogLQMCzwEbbrrk uvSewhUwGZyAR5N9kIGlqneTN+fm6f/MRX65DuqP4C5bzcVTd/JRPM/7yctYz7J7sP2y 7Br1GdaUGYbwVZsSf31Sq2WDV4AywKfbHlX1xm6B2d4yPyfOhHUOpL96ptY2RsSP72ok MyDQ== X-Gm-Message-State: ACgBeo1W1mX9sERdhQU6pC5hK1UKq6MtQtVx/uaoLskqF4xB6a8cQY17 sIQfh9RztqbEh5iksWn2hjPzXRIh2N4G+/CzGb0nqg== X-Google-Smtp-Source: AA6agR7I6xbpfl75ceIqVJBTjukdoUKCCOmfzwNe16ntKyJTAvN6DjpOK5/plQG24Rnw0IxxmZbTzUXRqZ9SusdgKV0= X-Received: by 2002:a17:903:41c6:b0:174:3acf:8294 with SMTP id u6-20020a17090341c600b001743acf8294mr26109933ple.118.1661963907879; Wed, 31 Aug 2022 09:38:27 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Tim Harvey Date: Wed, 31 Aug 2022 09:38:16 -0700 Message-ID: Subject: Re: imx8mp USB OTG/dual-role To: Jun Li , Alexander Stein Cc: Jacky Bai , "linux-usb@vger.kernel.org" , Linux ARM Mailing List , Rikard Falkeborn , Lucas Stach , Philippe Schenker , Felipe Balbi , Fabio Estevam , Marcel Ziswiler , Shawn Guo , Marek Vasut , Francesco Dolcini , Aisheng Dong , Sascha Hauer , dl-linux-imx , Pengutronix Kernel Team Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Tue, Aug 30, 2022 at 8:11 PM Jun Li wrote: > > Hi, > > > -----Original Message----- > > From: Jacky Bai > > Sent: Wednesday, August 31, 2022 9:18 AM > > To: tharvey@gateworks.com; linux-usb@vger.kernel.org; Linux ARM Mailing > > List ; Jun Li > > Cc: Alexander Stein ; Jun Li > > ; Rikard Falkeborn ; Lucas > > Stach ; Philippe Schenker > > ; Felipe Balbi ; Fabio > > Estevam ; Marcel Ziswiler ; > > Shawn Guo ; Marek Vasut ; Francesco > > Dolcini ; Aisheng Dong > > ; Sascha Hauer ; > > dl-linux-imx ; Pengutronix Kernel Team > > > > Subject: RE: imx8mp USB OTG/dual-role > > > > Jun, as we discussed before, any conclusion on how to handle the USB OTG > > ID pin in RM? > > The NXP datasheet for iMX8MP already changed the ID pin name to be with _DNU > suffix, RM may be updated in next version. > If legacy ID is going to be used, any normal GPIO function can be selected > for it, extcon is well supported in dwc3 controller driver. > > More comments for Tim, see below... > > > > > > > BR > > Jacky Bai > > > > > Subject: imx8mp USB OTG/dual-role > > > > > > Greetings, > > > > > > I have an imx8mp board (imx8mp-venice-gw74xx) which has a DWC3 USB > > > host controller using imx8mp PHY > > > (drivers/phy/freescale/phy-fsl-imx8mq-usb.c fsl,imx8mp-usb-phy) and > > > DWC3 host controller core (drivers/usb/dwc3/core.c snps,dwc3) with > > > imx8mp glue (drivers/usb/dwc3/dwc3-imx8mp.c fsl,imx8mp-dwc3). > > > > > > One of the 2x USB 3.0 hosts is connected to a USB Type C connector > > > using a > > > TPS25821 USB power switch and config controller which handles the CC > > > pins on and VBUS enable as well as drives the mux sel pin of a > > > USB3 mux to route the USB SS pairs to the appropriate half of the Type > > > C connector. This device has no I2C or other management bus - only > > > VBUS, FAULT#, SINK#, and POL# outputs based on CC pins. > > > > > > I'm not clear how to describe this in the device-tree in order for it > > > to function as a dual-role controller for host vs device mode. > > > > > > The TPS25821 has a FAULT# signal that routes to IMX8MP GPIO1_IO13 > > > pinmuxed as MX8MP_IOMUXC_GPIO1_IO13__USB1_OTG_OC and a SINK# signal > > > that routes to IMX8MP GPIO1_IO10 pinmuxed as > > > MX8MP_IOMUXC_GPIO1_IO10__USB1_OTG_ID. Additionally the VBUS output of > > > the TPS25821 also connected to the TypeC VBUS pin routes to the IMX8MP > > > USB1_VBUS pin. > > So TPS25821 does not need a driver. > > > > > > > I've noticed there are currently only 2 other IMX8MP boards in Linux > > > mainline that specify dr_mode="otg"; the DH electronics i.MX8M Plus > > > DHCOM SOM (imx8mp-dhcom-som.dtsi), and the Toradex i.MX8M Plus Verdin > > > SOM (imx8mp-verdin.dtsi). I'm not clear how these are hooked up or if > > > USB dual-role work on these currently. I did notice that > > NXP iMX8MP EVK has not enabled type-C port due to the SS orientation > switch binding is still in discussion, but you don't need a SW control > in your case so you are okay here. > > > > imx8mp-verdin.dtsi looks like it does not enable the phy or core via > > > status prop and uses invalid 'over-current-active-low' and > > 'disable-over-current' dt props. > > > > > > I am currently using the following with imx8mp-venice-gw74xx: > > > > > > /* USB1 - Type C front panel */ > > > &usb3_phy0 { > > > status = "okay"; > > > }; > > > > > > /* USB1 dwc3 glue */ > > > &usb3_0 { > > > fsl,over-current-active-low; > > > status = "okay"; > > > }; > > > > > > /* USB1 dwc3 core */ > > > &usb_dwc3_0 { > > > pinctrl-names = "default"; > > > pinctrl-0 = <&pinctrl_usb1>; > > > dr_mode = "otg"; > > > }; > > > > > > &iomuxc { > > > pinctrl_usb1: usb1grp { > > > fsl,pins = < > > > > > > MX8MP_IOMUXC_GPIO1_IO13__USB1_OTG_OC 0x140 > > > > > > MX8MP_IOMUXC_GPIO1_IO10__USB1_OTG_ID 0x140 > > > >; > > > }; > > > }; > > > > > > And currently v6.0-rc2 enumerates the host controller even without a > > > Type-C to host cable attached which tells me that OTG_ID isn't doing > > > its job. I vaguely recall some confusing statements on the IMX > > > community forum that these pins might not even be used on the IMX8MP. > > > > > > How should I be describing the device-tree for this scenario in order > > > to get dual-role behavior? > > Could this dts work for you? > > /* Config the "ID" pin iomux to be GPIO */ > > pinctrl_usb1: usb1grp { > fsl,pins = < > MX8MP_IOMUXC_GPIO1_IO13__USB1_OTG_OC 0x140 > MX8MP_IOMUXC_GPIO1_IO10__GPIO1_IO10 0x140 > >; > }; > > extcon_usb: extcon_iddig { > compatible = "linux,extcon-usb-gpio"; > id-gpio = <&gpio1 10 GPIO_ACTIVE_HIGH>; > }; > > &usb_dwc3_0 { > pinctrl-names = "default"; > pinctrl-0 = <&pinctrl_usb1>; > extcon = <&extcon_usb> > dr_mode = "otg"; > }; > > Li Jun Jun, Thank you, this does appear to work as intended as dual-role. I was not aware of linux,extcon-usb-gpio. And thanks also Alexander, your usb-dual-role via connector method works as well. Which method is preferred, using extcon or using usb-role-switch via a connector as in Alexander's patch? Additionally, where is it appropriate to put the pinctrl for the OC and ID pins in the usb_dwc3_0 (dwc3 core) node, the usb3_0 (dwc3 glue) node, or the usb3_phy0 (phy) node? Best Regards, Tim From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 27FB5ECAAD1 for ; Wed, 31 Aug 2022 16:39:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=zDQczQ8dHkp3jXhln9ffR+JzKlooidVIBmt8ykOJ2PI=; b=VHxigFJBl+oQmo zm0DAtCBLNqH6ZOx8R8zDzRd9eruUCLZ9jazKyvoGRgnGb/VxwUrBmhHByy4qyK5DnUFAgLM7PM4Z ppImUOWO2DX6rcn13eIbnnOUDNHTMQi9+T+mSwWlR/dGiw+pX/VBPGsKYTcNZGJnktOUgBNNgAU5G uS97JntiOuIOxwGQWta5b0C6TVFZVjVgRZtJSvYfcyIOkaVUsqSeurqqqFYKEGIflHNsK9NflhLDJ joPWk2hgHRE4xRahxsTYdbtazWUDsIj2Ye71lJtZLwAElrLEz6EQw1Nj0C3/imjdtmrwZkho1qWI1 abb3gfqHz1CFDDZazvqg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oTQjZ-007FLC-Q0; Wed, 31 Aug 2022 16:38:33 +0000 Received: from mail-pj1-x1033.google.com ([2607:f8b0:4864:20::1033]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oTQjW-007FKn-QF for linux-arm-kernel@lists.infradead.org; Wed, 31 Aug 2022 16:38:32 +0000 Received: by mail-pj1-x1033.google.com with SMTP id i7-20020a17090adc0700b001fd7ccbec3cso3993492pjv.0 for ; Wed, 31 Aug 2022 09:38:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gateworks-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=OaCyZzLvcCpsyTCEH1A5MS9EZVvRVfWIIgcRnBjIWNQ=; b=qIKKi3mMHcII/hptopT7BPHoIw7FFlwg4NC8lfWdKaKsPIQJdXj+RH5gDdBK1LWVan seOvLPJrVW96WV2gHcnNFHxjPCkPmP7RffnD3BP0Pwf1w3mXK8Za3UItXcazf3hPU1x5 JgUOecmjIXsajFKqKeWQm4Mnkck57YXp11dCXez4Jr7dQo6cdwgcHf3OOW8jPBrTuieO HXUAA7xy+nbzbJM7BGF6/tqKBEHESPFvtW7hGrZBpuPUQQX+bdEv+qeYMtvX8b4OUiw+ 1WSjsIvXvIDqCQ3L42aNS4g75ZqEumYMaj9P9Pg+/JR1cA/Dhml3cq0nRi3lF0xiXz0L obfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=OaCyZzLvcCpsyTCEH1A5MS9EZVvRVfWIIgcRnBjIWNQ=; b=KuSpHwbdPJBwZbQYGyyMDvaPhDCMo03TSVk4lht38C151cc5gvoI+5bmeX2D3DDjHr asTlg3sR+J2iX35opgmTWpwOSlTqUqKcMrS9KWL1RerOWM1Bw6kinHuRQuvCCT6Q7aQZ MUeLofFU8fZbnmeH36JxdmY26fsksQ3ztb+lyU0NlmFe20Sg3k8gk6vAU9DpPaPjDHRP l3Xg2zPFmXU5VT2hIHhtK1u4j7WPy9mTNHM2S+KfjgSMlWzafdB1XkvmX+gMq5bW0vz7 DhPOOF7ATa1rgQIgJ/N5uy4yKJ5QlV/J9BIQ3CMggQcgW/N9AP3rGmD5qu7kKmpdSaWF +5KQ== X-Gm-Message-State: ACgBeo0ss/OY7KfAziU8ujc6KaQawk3iwreHM4Uq2RL9ufnY0cXj5722 wTsezCrnxou0KY1yi5lFUuH0exTPz6S+Ij/XFD8urg== X-Google-Smtp-Source: AA6agR7I6xbpfl75ceIqVJBTjukdoUKCCOmfzwNe16ntKyJTAvN6DjpOK5/plQG24Rnw0IxxmZbTzUXRqZ9SusdgKV0= X-Received: by 2002:a17:903:41c6:b0:174:3acf:8294 with SMTP id u6-20020a17090341c600b001743acf8294mr26109933ple.118.1661963907879; Wed, 31 Aug 2022 09:38:27 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Tim Harvey Date: Wed, 31 Aug 2022 09:38:16 -0700 Message-ID: Subject: Re: imx8mp USB OTG/dual-role To: Jun Li , Alexander Stein Cc: Jacky Bai , "linux-usb@vger.kernel.org" , Linux ARM Mailing List , Rikard Falkeborn , Lucas Stach , Philippe Schenker , Felipe Balbi , Fabio Estevam , Marcel Ziswiler , Shawn Guo , Marek Vasut , Francesco Dolcini , Aisheng Dong , Sascha Hauer , dl-linux-imx , Pengutronix Kernel Team X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220831_093831_129490_78421166 X-CRM114-Status: GOOD ( 40.71 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Aug 30, 2022 at 8:11 PM Jun Li wrote: > > Hi, > > > -----Original Message----- > > From: Jacky Bai > > Sent: Wednesday, August 31, 2022 9:18 AM > > To: tharvey@gateworks.com; linux-usb@vger.kernel.org; Linux ARM Mailing > > List ; Jun Li > > Cc: Alexander Stein ; Jun Li > > ; Rikard Falkeborn ; Lucas > > Stach ; Philippe Schenker > > ; Felipe Balbi ; Fabio > > Estevam ; Marcel Ziswiler ; > > Shawn Guo ; Marek Vasut ; Francesco > > Dolcini ; Aisheng Dong > > ; Sascha Hauer ; > > dl-linux-imx ; Pengutronix Kernel Team > > > > Subject: RE: imx8mp USB OTG/dual-role > > > > Jun, as we discussed before, any conclusion on how to handle the USB OTG > > ID pin in RM? > > The NXP datasheet for iMX8MP already changed the ID pin name to be with _DNU > suffix, RM may be updated in next version. > If legacy ID is going to be used, any normal GPIO function can be selected > for it, extcon is well supported in dwc3 controller driver. > > More comments for Tim, see below... > > > > > > > BR > > Jacky Bai > > > > > Subject: imx8mp USB OTG/dual-role > > > > > > Greetings, > > > > > > I have an imx8mp board (imx8mp-venice-gw74xx) which has a DWC3 USB > > > host controller using imx8mp PHY > > > (drivers/phy/freescale/phy-fsl-imx8mq-usb.c fsl,imx8mp-usb-phy) and > > > DWC3 host controller core (drivers/usb/dwc3/core.c snps,dwc3) with > > > imx8mp glue (drivers/usb/dwc3/dwc3-imx8mp.c fsl,imx8mp-dwc3). > > > > > > One of the 2x USB 3.0 hosts is connected to a USB Type C connector > > > using a > > > TPS25821 USB power switch and config controller which handles the CC > > > pins on and VBUS enable as well as drives the mux sel pin of a > > > USB3 mux to route the USB SS pairs to the appropriate half of the Type > > > C connector. This device has no I2C or other management bus - only > > > VBUS, FAULT#, SINK#, and POL# outputs based on CC pins. > > > > > > I'm not clear how to describe this in the device-tree in order for it > > > to function as a dual-role controller for host vs device mode. > > > > > > The TPS25821 has a FAULT# signal that routes to IMX8MP GPIO1_IO13 > > > pinmuxed as MX8MP_IOMUXC_GPIO1_IO13__USB1_OTG_OC and a SINK# signal > > > that routes to IMX8MP GPIO1_IO10 pinmuxed as > > > MX8MP_IOMUXC_GPIO1_IO10__USB1_OTG_ID. Additionally the VBUS output of > > > the TPS25821 also connected to the TypeC VBUS pin routes to the IMX8MP > > > USB1_VBUS pin. > > So TPS25821 does not need a driver. > > > > > > > I've noticed there are currently only 2 other IMX8MP boards in Linux > > > mainline that specify dr_mode="otg"; the DH electronics i.MX8M Plus > > > DHCOM SOM (imx8mp-dhcom-som.dtsi), and the Toradex i.MX8M Plus Verdin > > > SOM (imx8mp-verdin.dtsi). I'm not clear how these are hooked up or if > > > USB dual-role work on these currently. I did notice that > > NXP iMX8MP EVK has not enabled type-C port due to the SS orientation > switch binding is still in discussion, but you don't need a SW control > in your case so you are okay here. > > > > imx8mp-verdin.dtsi looks like it does not enable the phy or core via > > > status prop and uses invalid 'over-current-active-low' and > > 'disable-over-current' dt props. > > > > > > I am currently using the following with imx8mp-venice-gw74xx: > > > > > > /* USB1 - Type C front panel */ > > > &usb3_phy0 { > > > status = "okay"; > > > }; > > > > > > /* USB1 dwc3 glue */ > > > &usb3_0 { > > > fsl,over-current-active-low; > > > status = "okay"; > > > }; > > > > > > /* USB1 dwc3 core */ > > > &usb_dwc3_0 { > > > pinctrl-names = "default"; > > > pinctrl-0 = <&pinctrl_usb1>; > > > dr_mode = "otg"; > > > }; > > > > > > &iomuxc { > > > pinctrl_usb1: usb1grp { > > > fsl,pins = < > > > > > > MX8MP_IOMUXC_GPIO1_IO13__USB1_OTG_OC 0x140 > > > > > > MX8MP_IOMUXC_GPIO1_IO10__USB1_OTG_ID 0x140 > > > >; > > > }; > > > }; > > > > > > And currently v6.0-rc2 enumerates the host controller even without a > > > Type-C to host cable attached which tells me that OTG_ID isn't doing > > > its job. I vaguely recall some confusing statements on the IMX > > > community forum that these pins might not even be used on the IMX8MP. > > > > > > How should I be describing the device-tree for this scenario in order > > > to get dual-role behavior? > > Could this dts work for you? > > /* Config the "ID" pin iomux to be GPIO */ > > pinctrl_usb1: usb1grp { > fsl,pins = < > MX8MP_IOMUXC_GPIO1_IO13__USB1_OTG_OC 0x140 > MX8MP_IOMUXC_GPIO1_IO10__GPIO1_IO10 0x140 > >; > }; > > extcon_usb: extcon_iddig { > compatible = "linux,extcon-usb-gpio"; > id-gpio = <&gpio1 10 GPIO_ACTIVE_HIGH>; > }; > > &usb_dwc3_0 { > pinctrl-names = "default"; > pinctrl-0 = <&pinctrl_usb1>; > extcon = <&extcon_usb> > dr_mode = "otg"; > }; > > Li Jun Jun, Thank you, this does appear to work as intended as dual-role. I was not aware of linux,extcon-usb-gpio. And thanks also Alexander, your usb-dual-role via connector method works as well. Which method is preferred, using extcon or using usb-role-switch via a connector as in Alexander's patch? Additionally, where is it appropriate to put the pinctrl for the OC and ID pins in the usb_dwc3_0 (dwc3 core) node, the usb3_0 (dwc3 glue) node, or the usb3_phy0 (phy) node? Best Regards, Tim _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel