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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 5AAB0C43217 for ; Tue, 18 Oct 2022 09:41:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=jBptJLWXjtvddABsqS74vLlWKBbEbHCtOULnSpErrUo=; b=Tc9JoLJDGdkTkI f7GXp1lSVnONSsMoJdz1pxA07u7g4o05fmZKmUXr8B3OVb2w9KA1qBIaIdksDxp3g5wfiS87wMtA5 BPCi04RmMX0l1Qp471nR/5RBPmp/LPbKD0Lq1WSvX99kusjvqle11DUFPUc6U17EdEWLbejIiVA47 Bsg/aM1IuF5G9CUlH8HOH4ud2VMRWMPnR54imw+y+iqnRqMTI2j6c7JuXCEABtseXnyuWTRE6jcrm 3A8B2EDvNxqpaGqEC2cjvhhsVTx/emlgI/JWMCDWde5CSCMr1f/vSx/HwV+EkquMXalekAGQCyED4 +ASaGFfv+mMGT8KREZIA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1okj5v-0057s5-PW; Tue, 18 Oct 2022 09:41:07 +0000 Received: from sin.source.kernel.org ([145.40.73.55]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1okj5s-0057gm-FR for linux-phy@lists.infradead.org; Tue, 18 Oct 2022 09:41:06 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sin.source.kernel.org (Postfix) with ESMTPS id 21913CE1C38; Tue, 18 Oct 2022 09:41:02 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 066FCC433D6; Tue, 18 Oct 2022 09:41:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1666086060; bh=dBRtFaZHv2zChbhx1tx9d4AuEegiV59h3N2IOeis6QE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=BPUgbmbZ2JFJ+7nVnGWJQezOogS6KNbQYKEDjLuKwrhLPRd7kaP0oFsm7ACcjXszp ycxTxqeG1YETgQFXGb0JWXqNU1b0GSV8JQOkS8+JELZFkP3scnLJX2F5zRC/PUXD5V o+esx1NuDw4+kDsprDr+arFMUcRDJBvV3m64tGMA7da3TACb8x7mXGpvTJZlC2SULQ UClLbELT7gTSu6aeo8kQJSClbC5+UaiRFKw776Yw+XCWpfjQ5BF49F+oEMo+c9gPhy G/D4MkuffCugJatLS80nDjiIba0G3fcAaOxYiUYWoADNBr1aQllTBX2GEpalhiXXpu 6rX+gBOlTKU6w== Received: from johan by xi.lan with local (Exim 4.94.2) (envelope-from ) id 1okj5b-00025V-Ea; Tue, 18 Oct 2022 11:40:48 +0200 Date: Tue, 18 Oct 2022 11:40:47 +0200 From: Johan Hovold To: Krzysztof Kozlowski Cc: Johan Hovold , Vinod Koul , Andy Gross , Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , Dmitry Baryshkov , linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 10/15] dt-bindings: phy: qcom,qmp-pcie: add sc8280xp bindings Message-ID: References: <20221017145328.22090-1-johan+linaro@kernel.org> <20221017145328.22090-11-johan+linaro@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221018_024104_882917_F0B943AD X-CRM114-Status: GOOD ( 25.91 ) X-BeenThere: linux-phy@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Linux Phy Mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-phy" Errors-To: linux-phy-bounces+linux-phy=archiver.kernel.org@lists.infradead.org On Mon, Oct 17, 2022 at 01:20:49PM -0400, Krzysztof Kozlowski wrote: > On 17/10/2022 10:53, Johan Hovold wrote: > > Add bindings for the PCIe QMP PHYs found on SC8280XP. > > > > The PCIe2 and PCIe3 controllers and PHYs on SC8280XP can be used in > > 4-lane mode or as separate controllers and PHYs in 2-lane mode (e.g. as > > PCIe2A and PCIe2B). > > > > The configuration for a specific system can be read from a TCSR register. > > > > Signed-off-by: Johan Hovold > > --- > > .../bindings/phy/qcom,qmp-pcie-phy.yaml | 163 ++++++++++++++++++ > > 1 file changed, 163 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/phy/qcom,qmp-pcie-phy.yaml > > > > diff --git a/Documentation/devicetree/bindings/phy/qcom,qmp-pcie-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,qmp-pcie-phy.yaml > > new file mode 100644 > > index 000000000000..82da95eaa9d6 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/phy/qcom,qmp-pcie-phy.yaml > > Filename based on compatible, so for example: > > qcom,sc8280xp-qmp-pcie-phy.yaml Ok, but as I mentioned in my reply to the previous patch, this file is the one that is expected to be extended with new bindings. I can't seem to find where this naming scheme is documented now even if I'm quite sure I've seen it before. Do you have a pointer? And does this imply that the file name should also include the gen infix of one of the original compatibles (e.g. "qcom,sc8280xp-qmp-gen3x4-pcie-phy.yaml")? > > @@ -0,0 +1,163 @@ > > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/phy/qcom,qmp-pcie-phy.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: Qualcomm QMP PHY controller (PCIe) > > + > > +maintainers: > > + - Vinod Koul > > + > > +description: > > + QMP PHY controller supports physical layer functionality for a number of > > + controllers on Qualcomm chipsets, such as, PCIe, UFS, and USB. > > + > > +properties: > > + compatible: > > + enum: > > + - qcom,sc8280xp-qmp-gen3x1-pcie-phy > > + - qcom,sc8280xp-qmp-gen3x2-pcie-phy > > + - qcom,sc8280xp-qmp-gen3x4-pcie-phy > > + qcom,4ln-config-sel: > > + description: 4-lane configuration as TCSR syscon phandle, register offset > > + and bit number > > + $ref: /schemas/types.yaml#/definitions/phandle-array > > + items: > > + maxItems: 3 > > You have only one phandle, so you need to describe the items and limit > their number, like here: > > https://elixir.bootlin.com/linux/v5.18-rc1/source/Documentation/devicetree/bindings/soc/samsung/exynos-usi.yaml#L42 > > This allows you to skip most of property description. Ah, thanks, makes perfect sense. I based this one of the in-tree bindings which had been reviewed by Rob and must have thought it was some special phandle-array notation to express the same. Johan -- linux-phy mailing list linux-phy@lists.infradead.org https://lists.infradead.org/mailman/listinfo/linux-phy