On Thu, Aug 27, 2015 at 10:23 PM, Matt Porter <mporter@xxxxxxxxxxxx> wrote: > Convert the ti-phy.txt binding to standard YAML DT binding > format. This binding references the YAML generic PHY binding. > > Signed-off-by: Matt Porter <mporter@xxxxxxxxxxxx> > --- > Documentation/devicetree/bindings/phy/ti-phy.yaml | 166 ++++++++++++++++++++++ > 1 file changed, 166 insertions(+) > create mode 100644 Documentation/devicetree/bindings/phy/ti-phy.yaml > > diff --git a/Documentation/devicetree/bindings/phy/ti-phy.yaml b/Documentation/devicetree/bindings/phy/ti-phy.yaml > new file mode 100644 > index 0000000..ec93501 > --- /dev/null > +++ b/Documentation/devicetree/bindings/phy/ti-phy.yaml > @@ -0,0 +1,166 @@ > +%YAML 1.2 > +--- > +id: omap-control-phy > + > +title: OMAP Control PHY > + > +compatible: > + - name: "ti,control-phy-otghs" > + description: if it has otghs_control mailbox register as on OMAP4. > + - name: "ti,control-phy-usb2" > + description: if it has Power down bit in control_dev_conf register > + e.g. USB2_PHY on OMAP5. > + - name: "ti,control-phy-pipe3" > + description: if it has DPLL and individual Rx & Tx power control > + e.g. USB3 PHY and SATA PHY on OMAP5. > + - name: "ti,control-phy-pcie" > + description: for pcie to support external clock for pcie and to > + set PCS delay value. e.g. PCIE PHY in DRA7x > + - name: "ti,control-phy-usb2-dra7" > + description: if it has power down register like USB2 PHY on DRA7 > + DRA7 platform. > + - name: "ti,control-phy-usb2-am437" > + description: if it has power down register like USB2 PHY on AM437 > + platform. I'm confused. If these descriptions are multi-line, don't they need the '>' syntax? Also, I'm still confused by the "name:" field in this section. These are possible *values* for the compatible property, not the name of the field, as all other property descriptions are. ... -- Tim -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
