Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp3119101pxb; Fri, 12 Feb 2021 09:36:19 -0800 (PST) X-Google-Smtp-Source: ABdhPJyeBJODwBJBhj1ltaXkptt5wZMKrTe0IfrCg98arf/m467AVK4v7e2Cg1ZwviGeuetPetuz X-Received: by 2002:a50:d4d9:: with SMTP id e25mr4499270edj.183.1613151379542; Fri, 12 Feb 2021 09:36:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613151379; cv=none; d=google.com; s=arc-20160816; b=PHD6iZuFwIbX6aq8tLShhcAnE4oe5z99OkjvNbsxt5eI+h4jsxGNsHGVrBzTZN3y0O gqHtAXCLhOPauNaAB/h005xSQi3PrHlf5OYxYQRF981+JrbBwySWOb94s46Afi4q6vp9 sE0bkJ7cOrijLqnYTEmFfYEeg0yzopYI5jyauSmoFunONUKp/NNtwZM0C4//Rk+opPip C6eydlJz4iQgd2GCCiRe+3weGclXe0Obr9wUIUHrFhug8328wjiVr+aSE8OQlGdO1U1e BiOkTke08sRhY0UCSJFzxThJNcEHM0IP3vDwYJo4Gmab4wNoi/8pN4mMuu+x4b+Ohv9V 62FA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=ql649ilkfbYgpEPGcXqlFJzATUL8Qn5BMRqVJvwrR+M=; b=KXgvMofDPwzO4dWulAbM1/aPtH/UTajdqQ2YRUoW43XyEa4wz+XU0XoTh9Au2UxQCT 0Im+VM8EjmezCik1g7B+yx+ZMF6PhNsex2lrtnwYkvfxx0BZZGdltOy2jhT1Lg7M6wG9 XvavTh2iEJo1Hh6I01LXhf0AO/eC4u3KiVh5EhdDKOO9kPRHbh+ldw2Clfd9GWH3KVKk Zf+e1kj+Qdw89/kCz0CzFREZ4YmJjrPokOSgSnF6PoA7Uw41TSQv7qCC/eZn+KZs2Yfc JGywDSQ04qiRQUQl7kjYufzert7Ds6yK2pdzTdyEuBlLCgH7N1l5XKajNFieNsOrRydV SMeA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o17si7021695edq.357.2021.02.12.09.35.54; Fri, 12 Feb 2021 09:36:19 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230491AbhBLReU (ORCPT + 99 others); Fri, 12 Feb 2021 12:34:20 -0500 Received: from mail.baikalelectronics.com ([87.245.175.226]:40276 "EHLO mail.baikalelectronics.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229451AbhBLReD (ORCPT ); Fri, 12 Feb 2021 12:34:03 -0500 Date: Fri, 12 Feb 2021 20:33:15 +0300 From: Serge Semin To: Bjorn Andersson CC: Serge Semin , Rob Herring , Felipe Balbi , Krzysztof Kozlowski , Florian Fainelli , Greg Kroah-Hartman , Andy Gross , Linux USB List , linux-arm-msm , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v6 09/10] usb: dwc3: qcom: Detect DWC3 DT-nodes with "usb"-prefixed names Message-ID: <20210212173315.jgr6kata2yxrbkuu@mobilestation> References: <20210210172850.20849-1-Sergey.Semin@baikalelectronics.ru> <20210210172850.20849-10-Sergey.Semin@baikalelectronics.ru> <20210210184051.ncvvs5xgyo7o3uzq@mobilestation> <20210210193325.inp7rgpsfr624zhd@mobilestation> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20210210193325.inp7rgpsfr624zhd@mobilestation> X-ClientProxiedBy: MAIL.baikal.int (192.168.51.25) To mail (192.168.51.25) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 10, 2021 at 10:33:26PM +0300, Serge Semin wrote: > On Wed, Feb 10, 2021 at 12:56:59PM -0600, Bjorn Andersson wrote: > > On Wed 10 Feb 12:40 CST 2021, Serge Semin wrote: > > > > > On Wed, Feb 10, 2021 at 12:17:27PM -0600, Rob Herring wrote: > > > > On Wed, Feb 10, 2021 at 11:29 AM Serge Semin > > > > wrote: > > > > > > > > > > In accordance with the USB HCD/DRD schema all the USB controllers are > > > > > supposed to have DT-nodes named with prefix "^usb(@.*)?". Since the > > > > > existing DT-nodes will be renamed in a subsequent patch let's first make > > > > > sure the DWC3 Qualcomm driver supports them and second falls back to the > > > > > deprecated naming so not to fail on the legacy DTS-files passed to the > > > > > newer kernels. > > > > > > > > > > Signed-off-by: Serge Semin > > > > > Reviewed-by: Bjorn Andersson > > > > > --- > > > > > drivers/usb/dwc3/dwc3-qcom.c | 3 ++- > > > > > 1 file changed, 2 insertions(+), 1 deletion(-) > > > > > > > > > > diff --git a/drivers/usb/dwc3/dwc3-qcom.c b/drivers/usb/dwc3/dwc3-qcom.c > > > > > index c703d552bbcf..49ad8d507d37 100644 > > > > > --- a/drivers/usb/dwc3/dwc3-qcom.c > > > > > +++ b/drivers/usb/dwc3/dwc3-qcom.c > > > > > @@ -630,7 +630,8 @@ static int dwc3_qcom_of_register_core(struct platform_device *pdev) > > > > > struct device *dev = &pdev->dev; > > > > > int ret; > > > > > > > > > > - dwc3_np = of_get_child_by_name(np, "dwc3"); > > > > > + dwc3_np = of_get_child_by_name(np, "usb") ?: > > > > > + of_get_child_by_name(np, "dwc3"); > > > > > > > > > > > Is there some reason using compatible instead wouldn't work here? > > > > > > I don't know for sure. The fix has been requested in the framework of > > > this discussion: > > > https://lore.kernel.org/linux-usb/20201020115959.2658-30-Sergey.Semin@baikalelectronics.ru/#t > > > by the driver maintainer Bjorn. To get a firm answer it's better to > > > have him asked. > > > > My feedback was simply that it has to catch both cases, I didn't > > consider the fact that we have a compatible to match against. > > > > > As I see it having of_get_compatible_child() utilized > > > here would also work. At least for the available in kernel dt-files. > > > See the affected dts-es in: > > > https://lore.kernel.org/linux-usb/20210210172850.20849-11-Sergey.Semin@baikalelectronics.ru/ > > > > > > A problem may happen if some older versions of DTS-es had another > > > compatible string in the dwc3 sub-node... > > > > > > > Afaict all Qualcomm dts files has "snps,dwc3", so you can match against > > that instead. > > Ok then. I'll replace of_get_child_by_name() here with > of_get_compatible_child() matching just against "snps,dwc3" in v7. Can you > confirm that noone ever had a Qcom-based hardware described with dts having > the "synopsys,dwc3" compatible used as the DWC USB3 sub-node here? That > string has been marked as deprecated recently because the vendor-prefix > was changed sometime ago, but the original driver still accept it. > > Alternatively to be on a safe side we could match against both > compatibles here as Rob suggests. What do you think? Bjorn, any comment on the question above? So I could respin the series with this patch updated. Also note, since the patch's gonna be changed I'll have to remove your Reviewed-by tag unless u explicitly say I shouldn't. -Sergey > > -Sergey > > > > > Regards, > > Bjorn