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 X-Spam-Level: X-Spam-Status: No, score=-7.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E6DDCC072A4 for ; Wed, 22 May 2019 03:38:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id ABC65217F9 for ; Wed, 22 May 2019 03:38:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728314AbfEVDiD (ORCPT ); Tue, 21 May 2019 23:38:03 -0400 Received: from mailgw02.mediatek.com ([1.203.163.81]:33743 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1727681AbfEVDiD (ORCPT ); Tue, 21 May 2019 23:38:03 -0400 X-UUID: 1af16d7cb5dc42c0abeb575eabeb4e99-20190522 X-UUID: 1af16d7cb5dc42c0abeb575eabeb4e99-20190522 Received: from mtkcas36.mediatek.inc [(172.27.4.253)] by mailgw02.mediatek.com (envelope-from ) (mailgw01.mediatek.com ESMTP with TLS) with ESMTP id 2060629758; Wed, 22 May 2019 11:37:45 +0800 Received: from MTKCAS36.mediatek.inc (172.27.4.186) by MTKMBS31N1.mediatek.inc (172.27.4.69) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 22 May 2019 11:37:43 +0800 Received: from [10.17.3.153] (172.27.4.253) by MTKCAS36.mediatek.inc (172.27.4.170) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Wed, 22 May 2019 11:37:42 +0800 Message-ID: <1558496262.10179.379.camel@mhfsdcap03> Subject: Re: [PATCH v5 4/6] usb: roles: add API to get usb_role_switch by node From: Chunfeng Yun To: Heikki Krogerus CC: Biju Das , Rob Herring , Greg Kroah-Hartman , Mark Rutland , Matthias Brugger , "Adam Thomson" , Li Jun , Badhri Jagan Sridharan , Hans de Goede , Andy Shevchenko , Min Guo , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-usb@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-mediatek@lists.infradead.org" , Linus Walleij Date: Wed, 22 May 2019 11:37:42 +0800 In-Reply-To: <20190521103304.GJ1887@kuha.fi.intel.com> References: <1557823643-8616-1-git-send-email-chunfeng.yun@mediatek.com> <1557823643-8616-5-git-send-email-chunfeng.yun@mediatek.com> <20190517103736.GA1490@kuha.fi.intel.com> <20190517130511.GA1887@kuha.fi.intel.com> <1558319951.10179.352.camel@mhfsdcap03> <20190520080359.GC1887@kuha.fi.intel.com> <20190520083601.GE1887@kuha.fi.intel.com> <1558424104.10179.365.camel@mhfsdcap03> <20190521103304.GJ1887@kuha.fi.intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2019-05-21 at 13:33 +0300, Heikki Krogerus wrote: > On Tue, May 21, 2019 at 03:35:04PM +0800, Chunfeng Yun wrote: > > Hi, > > On Mon, 2019-05-20 at 09:45 +0000, Biju Das wrote: > > > > > > Hi Heikki, > > > > > > Thanks for the feedback. > > > > > > > Subject: Re: [PATCH v5 4/6] usb: roles: add API to get usb_role_switch by > > > > node > > > > > > > > On Mon, May 20, 2019 at 08:06:41AM +0000, Biju Das wrote: > > > > > Hi Heikki, > > > > > > > > > > > Subject: Re: [PATCH v5 4/6] usb: roles: add API to get > > > > > > usb_role_switch by node > > > > > > > > > > > > On Mon, May 20, 2019 at 10:39:11AM +0800, Chunfeng Yun wrote: > > > > > > > Hi, > > > > > > > On Fri, 2019-05-17 at 16:05 +0300, Heikki Krogerus wrote: > > > > > > > > Hi, > > > > > > > > > > > > > > > > On Fri, May 17, 2019 at 01:37:36PM +0300, Heikki Krogerus wrote: > > > > > > > > > On Tue, May 14, 2019 at 04:47:21PM +0800, Chunfeng Yun wrote: > > > > > > > > > > Add fwnode_usb_role_switch_get() to make easier to get > > > > > > > > > > usb_role_switch by fwnode which register it. > > > > > > > > > > It's useful when there is not device_connection registered > > > > > > > > > > between two drivers and only knows the fwnode which register > > > > > > > > > > usb_role_switch. > > > > > > > > > > > > > > > > > > > > Signed-off-by: Chunfeng Yun > > > > > > > > > > Tested-by: Biju Das > > > > > > > > > > > > > > > > > > Acked-by: Heikki Krogerus > > > > > > > > > > > > > > > > Hold on. I just noticed Rob's comment on patch 2/6, where he > > > > > > > > points out that you don't need to use device graph since the > > > > > > > > controller is the parent of the connector. Doesn't that mean you > > > > > > > > don't really need this API? > > > > > > > No, I still need it. > > > > > > > The change is about the way how to get fwnode; when use device > > > > > > > graph, get fwnode by of_graph_get_remote_node(); but now will get > > > > > > > fwnode by of_get_parent(); > > > > > > > > > > > > OK, I get that, but I'm still not convinced about if something like > > > > > > this function is needed at all. I also have concerns regarding how > > > > > > you are using the function. I'll explain in comment to the patch 5/6 in this > > > > series... > > > > > > > > > > FYI, Currently I am also using this api in my patch series. > > > > > https://patchwork.kernel.org/patch/10944637/ > > > > > > > > Yes, and I have the same question for you I jusb asked in comment I added > > > > to the patch 5/6 of this series. Why isn't usb_role_switch_get() enough? > > > > > > Currently no issue. It will work with this api as well, since the port node is part of controller node. > > > For eg:- > > > https://patchwork.kernel.org/patch/10944627/ > > > > > > However if any one adds port node inside the connector node, then this api may won't work as expected. > > > Currently I get below error > > > > > > [ 2.299703] OF: graph: no port node found in /soc/i2c@e6500000/hd3ss3220@47 > > > > > > For eg:- > > > > > > hd3ss3220@47 { > > > compatible = "ti,hd3ss3220"; > > > ... > > > .... > > > usb_con: connector { > > > .... > > > .... > > > port { > > > hd3ss3220_ep: endpoint@0 { > > > reg = <0>; > > > remote-endpoint = <&usb3peri_role_switch>; > > > }; > > > }; > > > }; > > > }; > > > > > > Regards, > > > Biju > > > > I tested 3 cases: > > > > case 1: > > > > connector { > > compatible = "linux,typeb-conn-gpio", "usb-b-connector"; > > label = "micro-USB"; > > type = "micro"; > > id-gpios = <&pio 12 GPIO_ACTIVE_HIGH>; > > vbus-supply = <&usb_p0_vbus>; > > > > port { > > bconn_ep: endpoint@0 { > > remote-endpoint = <&usb_role_sw>; > > }; > > }; > > }; > > > > &mtu3 { > > usb-role-switch; > > > > port { > > usb_role_sw: endpoint@0 { > > remote-endpoint = <&bconn_ep>; > > }; > > }; > > }; > > > > the driver of connector could use usb_role_switch_get(dev) to get > > mtu3's USB Role Switch. (dev is the device of connector) > > > > case 2: > > > > &mtu3 { > > usb-role-switch; > > > > connector { > > compatible = "linux,typeb-conn-gpio", "usb-b-connector"; > > label = "micro-USB"; > > type = "micro"; > > id-gpios = <&pio 12 GPIO_ACTIVE_HIGH>; > > vbus-supply = <&usb_p0_vbus>; > > }; > > }; > > > > the driver of connector using usb_role_switch_get(dev) failed to get > > mtu3's USB Role Switch. > > error log: > > #OF: graph: no port node found in /usb@11271000/connector > > this is because connector hasn't child node connected to remote > > endpoint which register USB Role Switch > > > > case 3: > > > > rsw_iddig: role_sw_iddig { > > compatible = "linux,typeb-conn-gpio"; > > status = "okay"; > > > > connector { > > compatible = "usb-b-connector"; > > label = "micro-USB"; > > type = "micro"; > > id-gpios = <&pio 12 GPIO_ACTIVE_HIGH>; > > vbus-supply = <&usb_p0_vbus>; > > > > port { > > bconn_ep: endpoint@0 { > > remote-endpoint = <&usb_role_sw>; > > }; > > }; > > }; > > }; > > > > &mtu3 { > > usb-role-switch; > > > > port { > > usb_role_sw: endpoint@0 { > > remote-endpoint = <&bconn_ep>; > > }; > > }; > > }; > > > > > > the driver of connector using usb_role_switch_get(dev) also failed to > > get mtu3's USB Role Switch. Because usb_role_switch_get() only search > > its child nodes (connector node), but not child's child (port node) > > This case is the same as Biju's > > > > Usually type-c is similar with case 3; > > the next version v6 of this series will use case 2 as Rob suggested, > > see [v5, 2/6] > > > > for case 2, will need the new API fwnode_usb_role_switch_get(); > > Thanks for the explanation. > > In this case, if I understood this correctly, the USB controller, which > is also the role switch, is the parent of the connector. So shouldn't > we simply consider that in the current API? It's better if can be added into the current API. I'll try it. > > diff --git a/drivers/usb/roles/class.c b/drivers/usb/roles/class.c > index f45d8df5cfb8..2f898167b99a 100644 > --- a/drivers/usb/roles/class.c > +++ b/drivers/usb/roles/class.c > @@ -125,6 +125,13 @@ struct usb_role_switch *usb_role_switch_get(struct device *dev) > { > struct usb_role_switch *sw; > > + /* > + * Simplest case is that a connector is looking for the controller, > + * which is its parent. > + */ > + if (device_property_present(dev->parent, "usb-role-switch")) > + return to_role_switch(dev->parent); > + > sw = device_connection_find_match(dev, "usb-role-switch", NULL, > usb_role_switch_match); > > > > for case 3, use the new API, or need modify usb_role_switch_get(); > > I did not completely understand this case, but isn't it the same as > case 2 in the end, after you change it as Rob suggested? I'm afraid not, their bindings are different, see connector/usb-connector.txt > > > thanks, > From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chunfeng Yun Subject: Re: [PATCH v5 4/6] usb: roles: add API to get usb_role_switch by node Date: Wed, 22 May 2019 11:37:42 +0800 Message-ID: <1558496262.10179.379.camel@mhfsdcap03> References: <1557823643-8616-1-git-send-email-chunfeng.yun@mediatek.com> <1557823643-8616-5-git-send-email-chunfeng.yun@mediatek.com> <20190517103736.GA1490@kuha.fi.intel.com> <20190517130511.GA1887@kuha.fi.intel.com> <1558319951.10179.352.camel@mhfsdcap03> <20190520080359.GC1887@kuha.fi.intel.com> <20190520083601.GE1887@kuha.fi.intel.com> <1558424104.10179.365.camel@mhfsdcap03> <20190521103304.GJ1887@kuha.fi.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20190521103304.GJ1887@kuha.fi.intel.com> Sender: linux-kernel-owner@vger.kernel.org To: Heikki Krogerus Cc: Biju Das , Rob Herring , Greg Kroah-Hartman , Mark Rutland , Matthias Brugger , Adam Thomson , Li Jun , Badhri Jagan Sridharan , Hans de Goede , Andy Shevchenko , Min Guo , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-usb@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-mediatek@lists.infradead.org" List-Id: devicetree@vger.kernel.org On Tue, 2019-05-21 at 13:33 +0300, Heikki Krogerus wrote: > On Tue, May 21, 2019 at 03:35:04PM +0800, Chunfeng Yun wrote: > > Hi, > > On Mon, 2019-05-20 at 09:45 +0000, Biju Das wrote: > > > > > > Hi Heikki, > > > > > > Thanks for the feedback. > > > > > > > Subject: Re: [PATCH v5 4/6] usb: roles: add API to get usb_role_switch by > > > > node > > > > > > > > On Mon, May 20, 2019 at 08:06:41AM +0000, Biju Das wrote: > > > > > Hi Heikki, > > > > > > > > > > > Subject: Re: [PATCH v5 4/6] usb: roles: add API to get > > > > > > usb_role_switch by node > > > > > > > > > > > > On Mon, May 20, 2019 at 10:39:11AM +0800, Chunfeng Yun wrote: > > > > > > > Hi, > > > > > > > On Fri, 2019-05-17 at 16:05 +0300, Heikki Krogerus wrote: > > > > > > > > Hi, > > > > > > > > > > > > > > > > On Fri, May 17, 2019 at 01:37:36PM +0300, Heikki Krogerus wrote: > > > > > > > > > On Tue, May 14, 2019 at 04:47:21PM +0800, Chunfeng Yun wrote: > > > > > > > > > > Add fwnode_usb_role_switch_get() to make easier to get > > > > > > > > > > usb_role_switch by fwnode which register it. > > > > > > > > > > It's useful when there is not device_connection registered > > > > > > > > > > between two drivers and only knows the fwnode which register > > > > > > > > > > usb_role_switch. > > > > > > > > > > > > > > > > > > > > Signed-off-by: Chunfeng Yun > > > > > > > > > > Tested-by: Biju Das > > > > > > > > > > > > > > > > > > Acked-by: Heikki Krogerus > > > > > > > > > > > > > > > > Hold on. I just noticed Rob's comment on patch 2/6, where he > > > > > > > > points out that you don't need to use device graph since the > > > > > > > > controller is the parent of the connector. Doesn't that mean you > > > > > > > > don't really need this API? > > > > > > > No, I still need it. > > > > > > > The change is about the way how to get fwnode; when use device > > > > > > > graph, get fwnode by of_graph_get_remote_node(); but now will get > > > > > > > fwnode by of_get_parent(); > > > > > > > > > > > > OK, I get that, but I'm still not convinced about if something like > > > > > > this function is needed at all. I also have concerns regarding how > > > > > > you are using the function. I'll explain in comment to the patch 5/6 in this > > > > series... > > > > > > > > > > FYI, Currently I am also using this api in my patch series. > > > > > https://patchwork.kernel.org/patch/10944637/ > > > > > > > > Yes, and I have the same question for you I jusb asked in comment I added > > > > to the patch 5/6 of this series. Why isn't usb_role_switch_get() enough? > > > > > > Currently no issue. It will work with this api as well, since the port node is part of controller node. > > > For eg:- > > > https://patchwork.kernel.org/patch/10944627/ > > > > > > However if any one adds port node inside the connector node, then this api may won't work as expected. > > > Currently I get below error > > > > > > [ 2.299703] OF: graph: no port node found in /soc/i2c@e6500000/hd3ss3220@47 > > > > > > For eg:- > > > > > > hd3ss3220@47 { > > > compatible = "ti,hd3ss3220"; > > > ... > > > .... > > > usb_con: connector { > > > .... > > > .... > > > port { > > > hd3ss3220_ep: endpoint@0 { > > > reg = <0>; > > > remote-endpoint = <&usb3peri_role_switch>; > > > }; > > > }; > > > }; > > > }; > > > > > > Regards, > > > Biju > > > > I tested 3 cases: > > > > case 1: > > > > connector { > > compatible = "linux,typeb-conn-gpio", "usb-b-connector"; > > label = "micro-USB"; > > type = "micro"; > > id-gpios = <&pio 12 GPIO_ACTIVE_HIGH>; > > vbus-supply = <&usb_p0_vbus>; > > > > port { > > bconn_ep: endpoint@0 { > > remote-endpoint = <&usb_role_sw>; > > }; > > }; > > }; > > > > &mtu3 { > > usb-role-switch; > > > > port { > > usb_role_sw: endpoint@0 { > > remote-endpoint = <&bconn_ep>; > > }; > > }; > > }; > > > > the driver of connector could use usb_role_switch_get(dev) to get > > mtu3's USB Role Switch. (dev is the device of connector) > > > > case 2: > > > > &mtu3 { > > usb-role-switch; > > > > connector { > > compatible = "linux,typeb-conn-gpio", "usb-b-connector"; > > label = "micro-USB"; > > type = "micro"; > > id-gpios = <&pio 12 GPIO_ACTIVE_HIGH>; > > vbus-supply = <&usb_p0_vbus>; > > }; > > }; > > > > the driver of connector using usb_role_switch_get(dev) failed to get > > mtu3's USB Role Switch. > > error log: > > #OF: graph: no port node found in /usb@11271000/connector > > this is because connector hasn't child node connected to remote > > endpoint which register USB Role Switch > > > > case 3: > > > > rsw_iddig: role_sw_iddig { > > compatible = "linux,typeb-conn-gpio"; > > status = "okay"; > > > > connector { > > compatible = "usb-b-connector"; > > label = "micro-USB"; > > type = "micro"; > > id-gpios = <&pio 12 GPIO_ACTIVE_HIGH>; > > vbus-supply = <&usb_p0_vbus>; > > > > port { > > bconn_ep: endpoint@0 { > > remote-endpoint = <&usb_role_sw>; > > }; > > }; > > }; > > }; > > > > &mtu3 { > > usb-role-switch; > > > > port { > > usb_role_sw: endpoint@0 { > > remote-endpoint = <&bconn_ep>; > > }; > > }; > > }; > > > > > > the driver of connector using usb_role_switch_get(dev) also failed to > > get mtu3's USB Role Switch. Because usb_role_switch_get() only search > > its child nodes (connector node), but not child's child (port node) > > This case is the same as Biju's > > > > Usually type-c is similar with case 3; > > the next version v6 of this series will use case 2 as Rob suggested, > > see [v5, 2/6] > > > > for case 2, will need the new API fwnode_usb_role_switch_get(); > > Thanks for the explanation. > > In this case, if I understood this correctly, the USB controller, which > is also the role switch, is the parent of the connector. So shouldn't > we simply consider that in the current API? It's better if can be added into the current API. I'll try it. > > diff --git a/drivers/usb/roles/class.c b/drivers/usb/roles/class.c > index f45d8df5cfb8..2f898167b99a 100644 > --- a/drivers/usb/roles/class.c > +++ b/drivers/usb/roles/class.c > @@ -125,6 +125,13 @@ struct usb_role_switch *usb_role_switch_get(struct device *dev) > { > struct usb_role_switch *sw; > > + /* > + * Simplest case is that a connector is looking for the controller, > + * which is its parent. > + */ > + if (device_property_present(dev->parent, "usb-role-switch")) > + return to_role_switch(dev->parent); > + > sw = device_connection_find_match(dev, "usb-role-switch", NULL, > usb_role_switch_match); > > > > for case 3, use the new API, or need modify usb_role_switch_get(); > > I did not completely understand this case, but isn't it the same as > case 2 in the end, after you change it as Rob suggested? I'm afraid not, their bindings are different, see connector/usb-connector.txt > > > thanks, > 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 X-Spam-Level: X-Spam-Status: No, score=-7.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,UNPARSEABLE_RELAY,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DD4D9C072A4 for ; Wed, 22 May 2019 03:38:14 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id B12952081C for ; Wed, 22 May 2019 03:38:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="ukXBQHog" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B12952081C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=mediatek.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Date:To:From:Subject:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=mTqHnIplIxG2tdzzUCunVJcrIMquHbTQuzs0p7z7esc=; b=ukXBQHogrwSwyP dtejWHEnd3Adp3iHrESsUnYYgBuphgC14LoL1UjcW7X1N96NmH2Uxd7PsVLELY9a0PIU/yvIN41WE Mx5iPUk0raKLnA2HoopITNKiZcuIl5cnlqLnc1C3AYzSJjfk6nciQRK7krLZabue9FzZJPVcShQpd E0dcgq6y6ijEane1Nfb8gIaz6MT7esI9OQuD3OP2SA7QgprJAIn1WyBor3fhNRp7I+oPB+M20iRl1 +43v6mNerdllGS7q19mUg7RXGvH27IAuGGyN3aBRk58EJmueE+tRD2QgYf8VISTr4RNFfcd04BUIu OvHjbxIUOulv+dg5mZvw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hTI4s-0004N2-Do; Wed, 22 May 2019 03:38:06 +0000 Received: from mailgw02.mediatek.com ([216.200.240.185]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hTI4n-0004M9-BF; Wed, 22 May 2019 03:38:03 +0000 X-UUID: 936fd9d9f23b430c9ec331ddba257371-20190521 X-UUID: 936fd9d9f23b430c9ec331ddba257371-20190521 Received: from mtkcas66.mediatek.inc [(172.29.193.44)] by mailgw02.mediatek.com (envelope-from ) (musrelay.mediatek.com ESMTP with TLS) with ESMTP id 1237621317; Tue, 21 May 2019 19:37:47 -0800 Received: from MTKMBS31N1.mediatek.inc (172.27.4.69) by MTKMBS62N2.mediatek.inc (172.29.193.42) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 21 May 2019 20:37:45 -0700 Received: from MTKCAS36.mediatek.inc (172.27.4.186) by MTKMBS31N1.mediatek.inc (172.27.4.69) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 22 May 2019 11:37:43 +0800 Received: from [10.17.3.153] (172.27.4.253) by MTKCAS36.mediatek.inc (172.27.4.170) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Wed, 22 May 2019 11:37:42 +0800 Message-ID: <1558496262.10179.379.camel@mhfsdcap03> Subject: Re: [PATCH v5 4/6] usb: roles: add API to get usb_role_switch by node From: Chunfeng Yun To: Heikki Krogerus Date: Wed, 22 May 2019 11:37:42 +0800 In-Reply-To: <20190521103304.GJ1887@kuha.fi.intel.com> References: <1557823643-8616-1-git-send-email-chunfeng.yun@mediatek.com> <1557823643-8616-5-git-send-email-chunfeng.yun@mediatek.com> <20190517103736.GA1490@kuha.fi.intel.com> <20190517130511.GA1887@kuha.fi.intel.com> <1558319951.10179.352.camel@mhfsdcap03> <20190520080359.GC1887@kuha.fi.intel.com> <20190520083601.GE1887@kuha.fi.intel.com> <1558424104.10179.365.camel@mhfsdcap03> <20190521103304.GJ1887@kuha.fi.intel.com> X-Mailer: Evolution 3.2.3-0ubuntu6 MIME-Version: 1.0 X-MTK: N X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190521_203801_396432_C200BED9 X-CRM114-Status: GOOD ( 37.01 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , "devicetree@vger.kernel.org" , Hans de Goede , Greg Kroah-Hartman , Linus Walleij , "linux-usb@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Biju Das , Badhri Jagan Sridharan , Andy Shevchenko , Rob Herring , "linux-mediatek@lists.infradead.org" , Min Guo , Matthias Brugger , Adam Thomson , "linux-arm-kernel@lists.infradead.org" , Li Jun Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, 2019-05-21 at 13:33 +0300, Heikki Krogerus wrote: > On Tue, May 21, 2019 at 03:35:04PM +0800, Chunfeng Yun wrote: > > Hi, > > On Mon, 2019-05-20 at 09:45 +0000, Biju Das wrote: > > > > > > Hi Heikki, > > > > > > Thanks for the feedback. > > > > > > > Subject: Re: [PATCH v5 4/6] usb: roles: add API to get usb_role_switch by > > > > node > > > > > > > > On Mon, May 20, 2019 at 08:06:41AM +0000, Biju Das wrote: > > > > > Hi Heikki, > > > > > > > > > > > Subject: Re: [PATCH v5 4/6] usb: roles: add API to get > > > > > > usb_role_switch by node > > > > > > > > > > > > On Mon, May 20, 2019 at 10:39:11AM +0800, Chunfeng Yun wrote: > > > > > > > Hi, > > > > > > > On Fri, 2019-05-17 at 16:05 +0300, Heikki Krogerus wrote: > > > > > > > > Hi, > > > > > > > > > > > > > > > > On Fri, May 17, 2019 at 01:37:36PM +0300, Heikki Krogerus wrote: > > > > > > > > > On Tue, May 14, 2019 at 04:47:21PM +0800, Chunfeng Yun wrote: > > > > > > > > > > Add fwnode_usb_role_switch_get() to make easier to get > > > > > > > > > > usb_role_switch by fwnode which register it. > > > > > > > > > > It's useful when there is not device_connection registered > > > > > > > > > > between two drivers and only knows the fwnode which register > > > > > > > > > > usb_role_switch. > > > > > > > > > > > > > > > > > > > > Signed-off-by: Chunfeng Yun > > > > > > > > > > Tested-by: Biju Das > > > > > > > > > > > > > > > > > > Acked-by: Heikki Krogerus > > > > > > > > > > > > > > > > Hold on. I just noticed Rob's comment on patch 2/6, where he > > > > > > > > points out that you don't need to use device graph since the > > > > > > > > controller is the parent of the connector. Doesn't that mean you > > > > > > > > don't really need this API? > > > > > > > No, I still need it. > > > > > > > The change is about the way how to get fwnode; when use device > > > > > > > graph, get fwnode by of_graph_get_remote_node(); but now will get > > > > > > > fwnode by of_get_parent(); > > > > > > > > > > > > OK, I get that, but I'm still not convinced about if something like > > > > > > this function is needed at all. I also have concerns regarding how > > > > > > you are using the function. I'll explain in comment to the patch 5/6 in this > > > > series... > > > > > > > > > > FYI, Currently I am also using this api in my patch series. > > > > > https://patchwork.kernel.org/patch/10944637/ > > > > > > > > Yes, and I have the same question for you I jusb asked in comment I added > > > > to the patch 5/6 of this series. Why isn't usb_role_switch_get() enough? > > > > > > Currently no issue. It will work with this api as well, since the port node is part of controller node. > > > For eg:- > > > https://patchwork.kernel.org/patch/10944627/ > > > > > > However if any one adds port node inside the connector node, then this api may won't work as expected. > > > Currently I get below error > > > > > > [ 2.299703] OF: graph: no port node found in /soc/i2c@e6500000/hd3ss3220@47 > > > > > > For eg:- > > > > > > hd3ss3220@47 { > > > compatible = "ti,hd3ss3220"; > > > ... > > > .... > > > usb_con: connector { > > > .... > > > .... > > > port { > > > hd3ss3220_ep: endpoint@0 { > > > reg = <0>; > > > remote-endpoint = <&usb3peri_role_switch>; > > > }; > > > }; > > > }; > > > }; > > > > > > Regards, > > > Biju > > > > I tested 3 cases: > > > > case 1: > > > > connector { > > compatible = "linux,typeb-conn-gpio", "usb-b-connector"; > > label = "micro-USB"; > > type = "micro"; > > id-gpios = <&pio 12 GPIO_ACTIVE_HIGH>; > > vbus-supply = <&usb_p0_vbus>; > > > > port { > > bconn_ep: endpoint@0 { > > remote-endpoint = <&usb_role_sw>; > > }; > > }; > > }; > > > > &mtu3 { > > usb-role-switch; > > > > port { > > usb_role_sw: endpoint@0 { > > remote-endpoint = <&bconn_ep>; > > }; > > }; > > }; > > > > the driver of connector could use usb_role_switch_get(dev) to get > > mtu3's USB Role Switch. (dev is the device of connector) > > > > case 2: > > > > &mtu3 { > > usb-role-switch; > > > > connector { > > compatible = "linux,typeb-conn-gpio", "usb-b-connector"; > > label = "micro-USB"; > > type = "micro"; > > id-gpios = <&pio 12 GPIO_ACTIVE_HIGH>; > > vbus-supply = <&usb_p0_vbus>; > > }; > > }; > > > > the driver of connector using usb_role_switch_get(dev) failed to get > > mtu3's USB Role Switch. > > error log: > > #OF: graph: no port node found in /usb@11271000/connector > > this is because connector hasn't child node connected to remote > > endpoint which register USB Role Switch > > > > case 3: > > > > rsw_iddig: role_sw_iddig { > > compatible = "linux,typeb-conn-gpio"; > > status = "okay"; > > > > connector { > > compatible = "usb-b-connector"; > > label = "micro-USB"; > > type = "micro"; > > id-gpios = <&pio 12 GPIO_ACTIVE_HIGH>; > > vbus-supply = <&usb_p0_vbus>; > > > > port { > > bconn_ep: endpoint@0 { > > remote-endpoint = <&usb_role_sw>; > > }; > > }; > > }; > > }; > > > > &mtu3 { > > usb-role-switch; > > > > port { > > usb_role_sw: endpoint@0 { > > remote-endpoint = <&bconn_ep>; > > }; > > }; > > }; > > > > > > the driver of connector using usb_role_switch_get(dev) also failed to > > get mtu3's USB Role Switch. Because usb_role_switch_get() only search > > its child nodes (connector node), but not child's child (port node) > > This case is the same as Biju's > > > > Usually type-c is similar with case 3; > > the next version v6 of this series will use case 2 as Rob suggested, > > see [v5, 2/6] > > > > for case 2, will need the new API fwnode_usb_role_switch_get(); > > Thanks for the explanation. > > In this case, if I understood this correctly, the USB controller, which > is also the role switch, is the parent of the connector. So shouldn't > we simply consider that in the current API? It's better if can be added into the current API. I'll try it. > > diff --git a/drivers/usb/roles/class.c b/drivers/usb/roles/class.c > index f45d8df5cfb8..2f898167b99a 100644 > --- a/drivers/usb/roles/class.c > +++ b/drivers/usb/roles/class.c > @@ -125,6 +125,13 @@ struct usb_role_switch *usb_role_switch_get(struct device *dev) > { > struct usb_role_switch *sw; > > + /* > + * Simplest case is that a connector is looking for the controller, > + * which is its parent. > + */ > + if (device_property_present(dev->parent, "usb-role-switch")) > + return to_role_switch(dev->parent); > + > sw = device_connection_find_match(dev, "usb-role-switch", NULL, > usb_role_switch_match); > > > > for case 3, use the new API, or need modify usb_role_switch_get(); > > I did not completely understand this case, but isn't it the same as > case 2 in the end, after you change it as Rob suggested? I'm afraid not, their bindings are different, see connector/usb-connector.txt > > > thanks, > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel