[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210517214607.GA3253863@robh.at.kernel.org>
Date: Mon, 17 May 2021 16:46:07 -0500
From: Rob Herring <robh@...nel.org>
To: Stephen Boyd <swboyd@...omium.org>
Cc: Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Kishon Vijay Abraham I <kishon@...com>,
Rob Clark <robdclark@...il.com>, Vinod Koul <vkoul@...nel.org>,
sbillaka@...eaurora.org, linux-arm-msm@...r.kernel.org,
linux-phy@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: phy: Introduce Qualcomm eDP/DP PHY
binding
On Tue, May 11, 2021 at 10:24:06AM -0700, Stephen Boyd wrote:
> Quoting Bjorn Andersson (2021-05-10 21:19:29)
> > diff --git a/Documentation/devicetree/bindings/phy/qcom,edp-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,edp-phy.yaml
> > new file mode 100644
> > index 000000000000..c258e4f7e332
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/phy/qcom,edp-phy.yaml
> > @@ -0,0 +1,69 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +
> > +%YAML 1.2
> > +---
> > +$id: "http://devicetree.org/schemas/phy/qcom,edp-phy.yaml#"
> > +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> > +
> > +title: Qualcomm DP/eDP PHY
> > +
> > +maintainers:
> > + - Bjorn Andersson <bjorn.andersson@...aro.org>
> > +
> > +description:
> > + The Qualcomm DP/eDP PHY is found in a number of Qualcomm platform and
> > + provides the physical interface for DisplayPort and Embedded Display Port.
> > +
> > +properties:
> > + compatible:
> > + enum:
> > + - qcom,sc8180x-dp-phy
> > + - qcom,sc8180x-edp-phy
Is there a difference in DP and eDP?
> > +
> > + reg:
> > + items:
> > + - description: PHY base register block
> > + - description: tx0 register block
> > + - description: tx1 register block
> > + - description: PLL register block
> > +
> > + clocks:
> > + maxItems: 2
>
> Can this be items: - const: again? I think having maxItems means you can
> have one or two items, which wouldn't match the number of clock-names
> then.
No, it's implicitly 'minItems: 2'. But you can have 'items' if a
description of each clock is useful.
>
> > +
> > + clock-names:
> > + items:
> > + - const: aux
> > + - const: cfg_ahb
> > +
Powered by blists - more mailing lists