Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp3305106ybi; Sun, 26 May 2019 20:10:14 -0700 (PDT) X-Google-Smtp-Source: APXvYqzwOcokwWFh18q0TaQAvU2lQpgbu775+y1+cjB7eN3ukgqZAO9GG76A/zl94T8V2YqthEpP X-Received: by 2002:a17:90a:3848:: with SMTP id l8mr28786256pjf.142.1558926614753; Sun, 26 May 2019 20:10:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558926614; cv=none; d=google.com; s=arc-20160816; b=UPedlRxeN2Ja9ZsU3JZk8BDP0ItQ0DV6U+9RRjEcuPBbdqQTJPQn5GDASCej8GqdMJ cXYeeg9IN0EC2r1VJ5zYwjgjPru0RZY8PJKDbA46WNI8XG1fVNB4/Ue8hoPElz/AFjiA FJ0kwu84i33anjiV1Tl6v2COJTyU66ZT4FO6P1p4C/dVTraoGs/dJ0HKeP4nacmciATa 5EMObmCD5Qlbiiwtox+N7X8EPQ7ZRq7/nq97s31oSEqQNhAnA6Js1L/M+JTswr01yEmE sGvQcckPpubElIL4YYEwJ4iXChaVebBTpRSPqdFIls4JFRBiHyMj5JgsRKRhxZw45b9N syMg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :references:in-reply-to:date:cc:to:from:subject:message-id; bh=zMg67qL5JSdQLF59XlXHMsJILefmB90XCU32PmA7mFw=; b=dkmMppkQXBaBNYdPbjSMoMJq4FCdxR5KRAsJW+mkHBDsTp80WCOtCRUSO3Dgxf9hoR jeOmvhnx9Ctc6Hdcp16nXGjjP7vONpAnIdGA6AK//pEREmrPYANQb/QPgp940ZhHfOPX gexIOjU8yUBMpdwAxSMVAp8t+i4W/u5DXIcJ1EMz+CJO5QN20TcoP3Tqcpsjiw3EXiib LPF8KoYFuxmxpPC+NsqNHKziXWZSf04+bQ/TwoFumIzaxvVuojvuHQaHvHqNAOV8QQoi Wn5dtyVxFh+ywHg3kCh5/Z1gzGL78zMuAyZmQVfEgLYh6cZg3/hLoaEBBjF0dTGLSNxs 303Q== 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 h1si15650378pgc.83.2019.05.26.20.09.59; Sun, 26 May 2019 20:10: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 S1726213AbfE0DIp (ORCPT + 99 others); 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, >