Hi Rob, On Wed, May 27, 2020 at 01:12:11PM -0600, Rob Herring wrote: > On Wed, May 27, 2020 at 05:47:36PM +0200, Maxime Ripard wrote: > > The BCM283x SoCs have a display pipeline composed of several controllers > > with device tree bindings that are supported by Linux. > > > > Now that we have the DT validation in place, let's split into separate > > files and convert the device tree bindings for those controllers to > > schemas. > > > > This is just a 1:1 conversion though, and some bindings were incomplete so > > it results in example validation warnings that are going to be addressed in > > the following patches. > > > > Cc: Rob Herring <robh+dt@xxxxxxxxxx> > > Cc: devicetree@xxxxxxxxxxxxxxx > > Signed-off-by: Maxime Ripard <maxime@xxxxxxxxxx> > > --- > > Documentation/devicetree/bindings/display/brcm,bcm-vc4.txt | 174 +------------------------------------------------------------------------ > > Documentation/devicetree/bindings/display/brcm,bcm2835-dpi.yaml | 66 +++++++++++++++++++++++++++- > > Documentation/devicetree/bindings/display/brcm,bcm2835-dsi0.yaml | 73 ++++++++++++++++++++++++++++++- > > Documentation/devicetree/bindings/display/brcm,bcm2835-hdmi.yaml | 75 +++++++++++++++++++++++++++++++- > > Documentation/devicetree/bindings/display/brcm,bcm2835-hvs.yaml | 37 +++++++++++++++- > > Documentation/devicetree/bindings/display/brcm,bcm2835-pixelvalve0.yaml | 40 +++++++++++++++++- > > Documentation/devicetree/bindings/display/brcm,bcm2835-txp.yaml | 37 +++++++++++++++- > > Documentation/devicetree/bindings/display/brcm,bcm2835-v3d.yaml | 42 +++++++++++++++++- > > Documentation/devicetree/bindings/display/brcm,bcm2835-vc4.yaml | 34 ++++++++++++++- > > Documentation/devicetree/bindings/display/brcm,bcm2835-vec.yaml | 44 ++++++++++++++++++- > > MAINTAINERS | 2 +- > > 11 files changed, 449 insertions(+), 175 deletions(-) > > delete mode 100644 Documentation/devicetree/bindings/display/brcm,bcm-vc4.txt > > create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-dpi.yaml > > create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-dsi0.yaml > > create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-hdmi.yaml > > create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-hvs.yaml > > create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-pixelvalve0.yaml > > create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-txp.yaml > > create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-v3d.yaml > > create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-vc4.yaml > > create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-vec.yaml > > > > diff --git a/Documentation/devicetree/bindings/display/brcm,bcm2835-dsi0.yaml b/Documentation/devicetree/bindings/display/brcm,bcm2835-dsi0.yaml > > new file mode 100644 > > index 000000000000..3887675f844e > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/display/brcm,bcm2835-dsi0.yaml > > @@ -0,0 +1,73 @@ > > +# SPDX-License-Identifier: GPL-2.0 > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/display/brcm,bcm2835-dsi0.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: Broadcom VC4 (VideoCore4) DSI Controller > > + > > +maintainers: > > + - Eric Anholt <eric@xxxxxxxxxx> > > + > > +properties: > > + compatible: > > + enum: > > + - brcm,bcm2835-dsi0 > > + - brcm,bcm2835-dsi1 > > + > > + reg: > > + maxItems: 1 > > + > > + clocks: > > + items: > > + - description: The DSI PLL clock feeding the DSI analog PHY > > + - description: The DSI ESC clock > > + - description: The DSI pixel clock > > + > > + clock-output-names: true > > + # FIXME: The meta-schemas don't seem to allow it for now > > + # items: > > + # - description: The DSI byte clock for the PHY > > + # - description: The DSI DDR2 clock > > + # - description: The DSI DDR clock > > Doesn't pattern work for you? > > pattern: '^dsi[0-1]_byte$' That's not really what I was trying to achieve. I don't think clock-output-names should hardcode the values it expect, since the whole point is to let the "user" (ie the DT) control the clock names. If these were to be fixed, it wouldn't even be here in the first place. I just wanted to have a description of the clocks to provide a name for, but it looks like clock-output-names can't have an items below. I looked at why, couldn't really find a reason, and forgot to tell you about it, sorry > Either way, > > Reviewed-by: Rob Herring <robh@xxxxxxxxxx> Thanks! Maxime
Attachment:
signature.asc
Description: PGP signature
