Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp3495959pxm; Mon, 28 Feb 2022 22:28:53 -0800 (PST) X-Google-Smtp-Source: ABdhPJw7GVqW6lTRlNBoL9xN5b3652pLb160QR1DCsQVUw9wr67ZalPP3vKPBsvKexSUVhuG52Xh X-Received: by 2002:a17:903:285:b0:14f:daea:e8d9 with SMTP id j5-20020a170903028500b0014fdaeae8d9mr23715423plr.128.1646116133273; Mon, 28 Feb 2022 22:28:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646116133; cv=none; d=google.com; s=arc-20160816; b=leHikOuMQCVquAJNDOZmpBs9pJNgDRs5rkOqfknPyIAjTvPZ+EsL1cplZavNnhSd/Z 2rp7G/8c0kz5/kUltXANkuk+IkGJPKRd3Z29H1IpF+BpjYrvoWlaFZckyNcuiwGltRJL QGwb0R2HKEGpgGqSN22hIg7x9IW56KK1o38czJjL6rtkpSX3bNxY6ueyeM3X+ACVoprM D6Kqrr54/LyTQ4qWbymOHCaj0XqSYUqslf5kBroZSdg8eX6CdBQSZCd38B21a0GqDmFl 6d8udYSyUlEHdFpXK6Cyvt+/OfFgWYonrTPNB7p+XbfXnIs9stiIBhIbq0uEInf12ZFL fglQ== 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:dkim-signature; bh=DaUtZIJE57Vq9SZxZBhHAxebl5xJ9yYYEaN9hQal+Yc=; b=Y2F9sKBsA3hFGgB6E35PT6iJr/jg0v6FXunGS0neTLec+LXFymLbQ11l9LpWX+rQEl H8eV+CAK3gFCdwt8MqfY6Usfp8Re3wxtkLPZdlBHeGGU7txPTK+th5lytOT7ZbUx7v9W a+oGOvM5m2sUG2HH7AGeEEkmgAJK/HGSH+DSh/LhnsGZeRHfdkzLGfahrKc/xoQ5c0O/ umcRmJcX1TjIat5oBnQ2D5XRFEFuiDNTeRAGtEqhTtDxleVCqFKQEQnhmqgD/PvfFM+T +qB54Ojee1mtqrpjZHwFGNRoqO95Sgyqr4avIujhbl//JX3SfxSM31AQRrgVHKdUsyZ4 sigQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=zkOAS1Nu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t11-20020a170902a5cb00b0014fd9acc1easi10375421plq.156.2022.02.28.22.28.37; Mon, 28 Feb 2022 22:28:53 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=zkOAS1Nu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232096AbiCAEH6 (ORCPT + 99 others); Mon, 28 Feb 2022 23:07:58 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43968 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232186AbiCAEH5 (ORCPT ); Mon, 28 Feb 2022 23:07:57 -0500 Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7F26A4F9EA for ; Mon, 28 Feb 2022 20:07:16 -0800 (PST) Received: by mail-pj1-x1035.google.com with SMTP id g7-20020a17090a708700b001bb78857ccdso1019200pjk.1 for ; Mon, 28 Feb 2022 20:07:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=DaUtZIJE57Vq9SZxZBhHAxebl5xJ9yYYEaN9hQal+Yc=; b=zkOAS1NuNVVA37+a+9a5ZOpokz2S8PWO35PvVGMMThDauaYUOPsvyVjtc8Zr41iFQi evBontnp0ibEks/7mYoY/YuqsCVhfpUaez7NR3mQ0Sa4AfaUz3NIZ7rvzqT9zXMSljSt jicjvB603m34d1Vm7FPVEsF93+5HqkdpbTJlR8aaCL3RSFn22ck2ctV0flqmUD8K22aX rBn1xW1ZmBx4pBckCgQoMMVFxwuuIu4PoBfFW1nuuS6InmoX/5JQDMz3HQ8pbqIOzO/o WBivj9pQFfdMjgHIT5CIYTmXNNtOvZ+OWI1ZbDsQbvnZOWTjZM6+zR9aSqlKeFTtKg89 hDig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=DaUtZIJE57Vq9SZxZBhHAxebl5xJ9yYYEaN9hQal+Yc=; b=qUZM8UgFz3o/FUlpetUMmEfaYamDbUeiiG4t5qtu0TuhYnCIv5A3mJWSTQsS8kQJCx OJY5GwGUXyO5iXiSUzjiAZRbsfFx8De+y3EIT/rEJ6bFvUL6XK9f5Pd7zrxY3xz1xLHh 33wQtsEWsytO5iCPSmxzs8iVyupHiGbU+6eDMgE7x2qRUl+gJe0FqkMclBlKP6OABQao 3arjbnBsj9WDqZ1ly4PDOe8Cmh2ssBACwFgRqG504qmg1wgfzHqhjACzYkrMGajn6kbX mgruB86pHWQTU4svFosd/btBDYJ8hBlt4x7ATlKirrr4Zo8EZeTstL3GK6O/CAdugqDI Gulw== X-Gm-Message-State: AOAM531Z03FIqRj7mm6tgoX4PxIGoYPq2QJO6Bo2WBCV0+2ajX7VFPUa 2pBNCc039AXRx4iQfMhKqlH06Q== X-Received: by 2002:a17:903:2448:b0:151:8173:abf5 with SMTP id l8-20020a170903244800b001518173abf5mr1730249pls.55.1646107636043; Mon, 28 Feb 2022 20:07:16 -0800 (PST) Received: from dragon (80.251.214.228.16clouds.com. [80.251.214.228]) by smtp.gmail.com with ESMTPSA id a32-20020a631a20000000b003756899829csm11509153pga.58.2022.02.28.20.07.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 28 Feb 2022 20:07:15 -0800 (PST) Date: Tue, 1 Mar 2022 12:07:09 +0800 From: Shawn Guo To: Bhupesh Sharma Cc: linux-arm-msm@vger.kernel.org, bhupesh.linux@gmail.com, agross@kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, vkoul@kernel.org, linux-phy@lists.infradead.org, robh+dt@kernel.org, Bjorn Andersson , Rob Herring Subject: Re: [PATCH v2 7/8] dt-bindings: phy: qcom,qmp: Describe phy@ subnode properly Message-ID: <20220301040709.GF269879@dragon> References: <20220228123019.382037-1-bhupesh.sharma@linaro.org> <20220228123019.382037-8-bhupesh.sharma@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220228123019.382037-8-bhupesh.sharma@linaro.org> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 28, 2022 at 06:00:18PM +0530, Bhupesh Sharma wrote: > Currently the qcom,qmp-phy dt-binding doesn't describe > the 'reg' and '#phy-cells' properties for the phy@ subnode. > > Fix the same. > > Cc: Bjorn Andersson > Cc: Rob Herring > Signed-off-by: Bhupesh Sharma > --- > Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml > index 70e7cd75e173..f8a43acd229a 100644 > --- a/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml > +++ b/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml > @@ -115,6 +115,13 @@ patternProperties: > Each device node of QMP phy is required to have as many child nodes as > the number of lanes the PHY has. > properties: > + reg: > + minItems: 1 > + maxItems: 6 > + > + "#phy-cells": > + const: 0 > + > "#clock-cells": > enum: [ 0, 1, 2 ] While you are at it, what about these properties? clocks = <&gcc GCC_USB3_PRIM_PHY_PIPE_CLK>; clock-names = "pipe0"; clock-output-names = "usb3_phy_pipe_clk_src"; Shawn