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=-4.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, 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 5A329C282E3 for ; Mon, 27 May 2019 03:08:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2B10721707 for ; Mon, 27 May 2019 03:08:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726256AbfE0DIp (ORCPT ); Sun, 26 May 2019 23:08:45 -0400 Received: from mailgw02.mediatek.com ([1.203.163.81]:25117 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1725923AbfE0DIp (ORCPT ); Sun, 26 May 2019 23:08:45 -0400 X-UUID: 2fe144548fe644e0b5a1723aa2584b31-20190527 X-UUID: 2fe144548fe644e0b5a1723aa2584b31-20190527 Received: from mtkcas36.mediatek.inc [(172.27.4.253)] by mailgw02.mediatek.com (envelope-from ) (mailgw01.mediatek.com ESMTP with TLS) with ESMTP id 639884790; Mon, 27 May 2019 11:08:38 +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; Mon, 27 May 2019 11:08:36 +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; Mon, 27 May 2019 11:08:35 +0800 Message-ID: <1558926515.10179.439.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 , Biju Das 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: Mon, 27 May 2019 11:08:35 +0800 In-Reply-To: <20190524124445.GP1887@kuha.fi.intel.com> References: <20190520080359.GC1887@kuha.fi.intel.com> <20190520083601.GE1887@kuha.fi.intel.com> <20190521095839.GI1887@kuha.fi.intel.com> <1558517436.10179.388.camel@mhfsdcap03> <20190522142640.GN1887@kuha.fi.intel.com> <20190524124445.GP1887@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 Hi Heikki & Biju, On Fri, 2019-05-24 at 15:44 +0300, Heikki Krogerus wrote: > On Wed, May 22, 2019 at 02:57:33PM +0000, Biju Das wrote: > > Hi Heikki, > > > > Thanks for the patch > > > > > Subject: Re: [PATCH v5 4/6] usb: roles: add API to get usb_role_switch by > > > node > > > > > > On Wed, May 22, 2019 at 10:55:17AM +0000, Biju Das wrote: > > > > Hi Chunfeng Yun, > > > > > > > > Thanks for the feedback. > > > > > > > > > Subject: RE: [PATCH v5 4/6] usb: roles: add API to get > > > > > usb_role_switch by node > > > > > > > > > > Hi Biju, > > > > > On Wed, 2019-05-22 at 08:05 +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 09:45:46AM +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 > > > > > > > > > > > > > > We need to understand why is that happening? > > > > > > > > > > > > > > > > > > > Form the stack trace the parent node is > > > > > > "parent_node=hd3ss3220@47" , > > > > > instead of the "connector" node. > > > > > > That is the reason for the above error. > > > > > > > > > > > > [ 2.442429] of_graph_get_next_endpoint.part.0+0x28/0x168 > > > > > > [ 2.447889] of_fwnode_graph_get_next_endpoint+0x5c/0xb0 > > > > > > [ 2.453267] fwnode_graph_get_next_endpoint+0x20/0x30 > > > > > > [ 2.458374] device_connection_find_match+0x74/0x1a0 > > > > > > [ 2.463399] usb_role_switch_get+0x20/0x28 > > > > > > [ 2.467542] hd3ss3220_probe+0xc4/0x218 > > > > > > > > > > > > The use case is > > > > > > > > > > > > &i2c0 { > > > > > > hd3ss3220@47 { > > > > > > compatible = "ti,hd3ss3220"; > > > > > > > > > > > > usb_con: connector { > > > > > > compatible = "usb-c-connector"; > > > > > > port { > > > > > > hd3ss3220_ep: endpoint { > > > > > > remote-endpoint = > > > > > <&usb3_role_switch>; > > > > > > }; > > > > > > }; > > > > > > }; > > > > > > }; > > > > > > }; > > > > > > > > > > > > &usb3_peri0 { > > > > > > companion = <&xhci0>; > > > > > > usb-role-switch; > > > > > > > > > > > > port { > > > > > > usb3_role_switch: endpoint { > > > > > > remote-endpoint = <&hd3ss3220_ep>; > > > > > > }; > > > > > > }; > > > > > > }; > > > > > > > > > > > > Q1) How do we modify the usb_role_switch_get() function to search > > > > > > Child(connector) and child's endpoint? > > > > > How about firstly finding connector node in > > > > > fwnode_graph_devcon_match(), then search each endpoint? > > > > > > > > I have done a quick prototyping with the changes you suggested and it > > > works. > > > > > > > > - struct fwnode_handle *ep; > > > > + struct fwnode_handle *ep,*child,*tmp = fwnode; > > > > > > > > - fwnode_graph_for_each_endpoint(fwnode, ep) { > > > > + child = fwnode_get_named_child_node(fwnode, "connector"); > > > > + if (child) > > > > + tmp = child; > > > > + > > > > + fwnode_graph_for_each_endpoint(tmp, ep) { > > > > > > > > Form the stack trace the parent node is "parent_node= connector" . > > > > > > > > [ 2.440922] of_graph_get_next_endpoint.part.0+0x28/0x168 > > > > [ 2.446381] of_fwnode_graph_get_next_endpoint+0x5c/0xb0 > > > > [ 2.451758] fwnode_graph_get_next_endpoint+0x20/0x30 > > > > [ 2.456866] device_connection_find_match+0x84/0x1c0 > > > > [ 2.461888] usb_role_switch_get+0x20/0x28 > > > > > > > > Heikki, > > > > Are you ok with the above changes? > > > > > > Doesn't that mean that if we made fwnode_usb_role_switch_get() the way I > > > proposed, there is no problem? You just find the "connector" child node in > > > your driver, and pass that to fwnode_usb_role_switch_get(): > > > > Yes, That is correct. > > > > > struct fwnode_handle *connector; > > > ... > > > connector = device_get_named_child_node(&client->dev, "connector"); > > > if (IS_ERR(connector)) > > > > > > > > > hd3ss3220->role_sw = fwnode_usb_role_switch_get(connector); > > > ... > > > > > > The difference is that instead of just converting a device node of an usb role > > > switch to the usb role switch, it works just like usb_role_switch_get(), just > > > taking fwnode instead of device entry as parameter. > > > > > > I prepared the patches implementing fwnode_usb_role_switch_get() the > > > way I though it needs to work for my own tests. Please find the patches > > > attached. > > > > I have tested this patches and conform it works. > > Do you plan to post this patches to ML? > > Could make them part of this series? I'll do it, thanks > > > 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: Mon, 27 May 2019 11:08:35 +0800 Message-ID: <1558926515.10179.439.camel@mhfsdcap03> References: <20190520080359.GC1887@kuha.fi.intel.com> <20190520083601.GE1887@kuha.fi.intel.com> <20190521095839.GI1887@kuha.fi.intel.com> <1558517436.10179.388.camel@mhfsdcap03> <20190522142640.GN1887@kuha.fi.intel.com> <20190524124445.GP1887@kuha.fi.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20190524124445.GP1887@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 Hi Heikki & Biju, On Fri, 2019-05-24 at 15:44 +0300, Heikki Krogerus wrote: > On Wed, May 22, 2019 at 02:57:33PM +0000, Biju Das wrote: > > Hi Heikki, > > > > Thanks for the patch > > > > > Subject: Re: [PATCH v5 4/6] usb: roles: add API to get usb_role_switch by > > > node > > > > > > On Wed, May 22, 2019 at 10:55:17AM +0000, Biju Das wrote: > > > > Hi Chunfeng Yun, > > > > > > > > Thanks for the feedback. > > > > > > > > > Subject: RE: [PATCH v5 4/6] usb: roles: add API to get > > > > > usb_role_switch by node > > > > > > > > > > Hi Biju, > > > > > On Wed, 2019-05-22 at 08:05 +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 09:45:46AM +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 > > > > > > > > > > > > > > We need to understand why is that happening? > > > > > > > > > > > > > > > > > > > Form the stack trace the parent node is > > > > > > "parent_node=hd3ss3220@47" , > > > > > instead of the "connector" node. > > > > > > That is the reason for the above error. > > > > > > > > > > > > [ 2.442429] of_graph_get_next_endpoint.part.0+0x28/0x168 > > > > > > [ 2.447889] of_fwnode_graph_get_next_endpoint+0x5c/0xb0 > > > > > > [ 2.453267] fwnode_graph_get_next_endpoint+0x20/0x30 > > > > > > [ 2.458374] device_connection_find_match+0x74/0x1a0 > > > > > > [ 2.463399] usb_role_switch_get+0x20/0x28 > > > > > > [ 2.467542] hd3ss3220_probe+0xc4/0x218 > > > > > > > > > > > > The use case is > > > > > > > > > > > > &i2c0 { > > > > > > hd3ss3220@47 { > > > > > > compatible = "ti,hd3ss3220"; > > > > > > > > > > > > usb_con: connector { > > > > > > compatible = "usb-c-connector"; > > > > > > port { > > > > > > hd3ss3220_ep: endpoint { > > > > > > remote-endpoint = > > > > > <&usb3_role_switch>; > > > > > > }; > > > > > > }; > > > > > > }; > > > > > > }; > > > > > > }; > > > > > > > > > > > > &usb3_peri0 { > > > > > > companion = <&xhci0>; > > > > > > usb-role-switch; > > > > > > > > > > > > port { > > > > > > usb3_role_switch: endpoint { > > > > > > remote-endpoint = <&hd3ss3220_ep>; > > > > > > }; > > > > > > }; > > > > > > }; > > > > > > > > > > > > Q1) How do we modify the usb_role_switch_get() function to search > > > > > > Child(connector) and child's endpoint? > > > > > How about firstly finding connector node in > > > > > fwnode_graph_devcon_match(), then search each endpoint? > > > > > > > > I have done a quick prototyping with the changes you suggested and it > > > works. > > > > > > > > - struct fwnode_handle *ep; > > > > + struct fwnode_handle *ep,*child,*tmp = fwnode; > > > > > > > > - fwnode_graph_for_each_endpoint(fwnode, ep) { > > > > + child = fwnode_get_named_child_node(fwnode, "connector"); > > > > + if (child) > > > > + tmp = child; > > > > + > > > > + fwnode_graph_for_each_endpoint(tmp, ep) { > > > > > > > > Form the stack trace the parent node is "parent_node= connector" . > > > > > > > > [ 2.440922] of_graph_get_next_endpoint.part.0+0x28/0x168 > > > > [ 2.446381] of_fwnode_graph_get_next_endpoint+0x5c/0xb0 > > > > [ 2.451758] fwnode_graph_get_next_endpoint+0x20/0x30 > > > > [ 2.456866] device_connection_find_match+0x84/0x1c0 > > > > [ 2.461888] usb_role_switch_get+0x20/0x28 > > > > > > > > Heikki, > > > > Are you ok with the above changes? > > > > > > Doesn't that mean that if we made fwnode_usb_role_switch_get() the way I > > > proposed, there is no problem? You just find the "connector" child node in > > > your driver, and pass that to fwnode_usb_role_switch_get(): > > > > Yes, That is correct. > > > > > struct fwnode_handle *connector; > > > ... > > > connector = device_get_named_child_node(&client->dev, "connector"); > > > if (IS_ERR(connector)) > > > > > > > > > hd3ss3220->role_sw = fwnode_usb_role_switch_get(connector); > > > ... > > > > > > The difference is that instead of just converting a device node of an usb role > > > switch to the usb role switch, it works just like usb_role_switch_get(), just > > > taking fwnode instead of device entry as parameter. > > > > > > I prepared the patches implementing fwnode_usb_role_switch_get() the > > > way I though it needs to work for my own tests. Please find the patches > > > attached. > > > > I have tested this patches and conform it works. > > Do you plan to post this patches to ML? > > Could make them part of this series? I'll do it, thanks > > > 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=-4.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,T_DKIMWL_WL_HIGH,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 4E7BFC282E3 for ; Mon, 27 May 2019 03:08:54 +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 1F9BD2075C for ; Mon, 27 May 2019 03:08:54 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="lN8ZV6Um" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1F9BD2075C 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=gg+1kfDsBojH/IIJdGs5xvycoZHfj8fSazhPmNpdrrQ=; b=lN8ZV6UmtYtB5/ VmoJQJOFyVZtcY64f3GwTdGm6eZrpntzSQAOf5JIFOzKvB81pq2NsLZ+8/pZ2OVMCthMOd9CKr9wi LXM0Dd38IuYYo8I0FEeIY0x7D5ce59h9+KVQ7SaYPzeEDcbggX240g8w0OXYula5LNdaJp0xQrRdB eqSiM81z3djZptzTtNUvj4t+HCbBo6I0OI+qWtIrxNGc30wg9biukrA+akdedC2NiVMAfbYLgWkAd xoVSxEjRX7E+g0rAXmDsxo8/gUUpQ+toGLusB7kplGkiEYdXDOcfivRmXZU9z4taNMHCT220Ounj3 XTEx9FWW2USIKnXO9mNA==; 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 1hV60G-0004JG-5t; Mon, 27 May 2019 03:08:48 +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 1hV60C-0004I7-5g; Mon, 27 May 2019 03:08:46 +0000 X-UUID: 39c7d7f0bccb46de966b7e2245c20b11-20190526 X-UUID: 39c7d7f0bccb46de966b7e2245c20b11-20190526 Received: from mtkcas67.mediatek.inc [(172.29.193.45)] by mailgw02.mediatek.com (envelope-from ) (musrelay.mediatek.com ESMTP with TLS) with ESMTP id 548429554; Sun, 26 May 2019 19:08:40 -0800 Received: from MTKMBS31N1.mediatek.inc (172.27.4.69) by MTKMBS62N1.mediatek.inc (172.29.193.41) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sun, 26 May 2019 20:08:39 -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; Mon, 27 May 2019 11:08:36 +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; Mon, 27 May 2019 11:08:35 +0800 Message-ID: <1558926515.10179.439.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 , Biju Das Date: Mon, 27 May 2019 11:08:35 +0800 In-Reply-To: <20190524124445.GP1887@kuha.fi.intel.com> References: <20190520080359.GC1887@kuha.fi.intel.com> <20190520083601.GE1887@kuha.fi.intel.com> <20190521095839.GI1887@kuha.fi.intel.com> <1558517436.10179.388.camel@mhfsdcap03> <20190522142640.GN1887@kuha.fi.intel.com> <20190524124445.GP1887@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-20190526_200844_217107_81CF0C66 X-CRM114-Status: GOOD ( 35.49 ) 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 Hi Heikki & Biju, On Fri, 2019-05-24 at 15:44 +0300, Heikki Krogerus wrote: > On Wed, May 22, 2019 at 02:57:33PM +0000, Biju Das wrote: > > Hi Heikki, > > > > Thanks for the patch > > > > > Subject: Re: [PATCH v5 4/6] usb: roles: add API to get usb_role_switch by > > > node > > > > > > On Wed, May 22, 2019 at 10:55:17AM +0000, Biju Das wrote: > > > > Hi Chunfeng Yun, > > > > > > > > Thanks for the feedback. > > > > > > > > > Subject: RE: [PATCH v5 4/6] usb: roles: add API to get > > > > > usb_role_switch by node > > > > > > > > > > Hi Biju, > > > > > On Wed, 2019-05-22 at 08:05 +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 09:45:46AM +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 > > > > > > > > > > > > > > We need to understand why is that happening? > > > > > > > > > > > > > > > > > > > Form the stack trace the parent node is > > > > > > "parent_node=hd3ss3220@47" , > > > > > instead of the "connector" node. > > > > > > That is the reason for the above error. > > > > > > > > > > > > [ 2.442429] of_graph_get_next_endpoint.part.0+0x28/0x168 > > > > > > [ 2.447889] of_fwnode_graph_get_next_endpoint+0x5c/0xb0 > > > > > > [ 2.453267] fwnode_graph_get_next_endpoint+0x20/0x30 > > > > > > [ 2.458374] device_connection_find_match+0x74/0x1a0 > > > > > > [ 2.463399] usb_role_switch_get+0x20/0x28 > > > > > > [ 2.467542] hd3ss3220_probe+0xc4/0x218 > > > > > > > > > > > > The use case is > > > > > > > > > > > > &i2c0 { > > > > > > hd3ss3220@47 { > > > > > > compatible = "ti,hd3ss3220"; > > > > > > > > > > > > usb_con: connector { > > > > > > compatible = "usb-c-connector"; > > > > > > port { > > > > > > hd3ss3220_ep: endpoint { > > > > > > remote-endpoint = > > > > > <&usb3_role_switch>; > > > > > > }; > > > > > > }; > > > > > > }; > > > > > > }; > > > > > > }; > > > > > > > > > > > > &usb3_peri0 { > > > > > > companion = <&xhci0>; > > > > > > usb-role-switch; > > > > > > > > > > > > port { > > > > > > usb3_role_switch: endpoint { > > > > > > remote-endpoint = <&hd3ss3220_ep>; > > > > > > }; > > > > > > }; > > > > > > }; > > > > > > > > > > > > Q1) How do we modify the usb_role_switch_get() function to search > > > > > > Child(connector) and child's endpoint? > > > > > How about firstly finding connector node in > > > > > fwnode_graph_devcon_match(), then search each endpoint? > > > > > > > > I have done a quick prototyping with the changes you suggested and it > > > works. > > > > > > > > - struct fwnode_handle *ep; > > > > + struct fwnode_handle *ep,*child,*tmp = fwnode; > > > > > > > > - fwnode_graph_for_each_endpoint(fwnode, ep) { > > > > + child = fwnode_get_named_child_node(fwnode, "connector"); > > > > + if (child) > > > > + tmp = child; > > > > + > > > > + fwnode_graph_for_each_endpoint(tmp, ep) { > > > > > > > > Form the stack trace the parent node is "parent_node= connector" . > > > > > > > > [ 2.440922] of_graph_get_next_endpoint.part.0+0x28/0x168 > > > > [ 2.446381] of_fwnode_graph_get_next_endpoint+0x5c/0xb0 > > > > [ 2.451758] fwnode_graph_get_next_endpoint+0x20/0x30 > > > > [ 2.456866] device_connection_find_match+0x84/0x1c0 > > > > [ 2.461888] usb_role_switch_get+0x20/0x28 > > > > > > > > Heikki, > > > > Are you ok with the above changes? > > > > > > Doesn't that mean that if we made fwnode_usb_role_switch_get() the way I > > > proposed, there is no problem? You just find the "connector" child node in > > > your driver, and pass that to fwnode_usb_role_switch_get(): > > > > Yes, That is correct. > > > > > struct fwnode_handle *connector; > > > ... > > > connector = device_get_named_child_node(&client->dev, "connector"); > > > if (IS_ERR(connector)) > > > > > > > > > hd3ss3220->role_sw = fwnode_usb_role_switch_get(connector); > > > ... > > > > > > The difference is that instead of just converting a device node of an usb role > > > switch to the usb role switch, it works just like usb_role_switch_get(), just > > > taking fwnode instead of device entry as parameter. > > > > > > I prepared the patches implementing fwnode_usb_role_switch_get() the > > > way I though it needs to work for my own tests. Please find the patches > > > attached. > > > > I have tested this patches and conform it works. > > Do you plan to post this patches to ML? > > Could make them part of this series? I'll do it, thanks > > > thanks, > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel