Hi Tomi, Thank you for the patch. On Wed, Sep 16, 2020 at 04:10:08PM +0300, Tomi Valkeinen wrote: > Add assigned-clocks, assigned-clock-parents and dma-coherent optional > properties. > > Signed-off-by: Tomi Valkeinen <tomi.valkeinen@xxxxxx> > Reviewed-by: Rob Herring <robh@xxxxxxxxxx> > --- > .../devicetree/bindings/display/ti/ti,am65x-dss.yaml | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/Documentation/devicetree/bindings/display/ti/ti,am65x-dss.yaml b/Documentation/devicetree/bindings/display/ti/ti,am65x-dss.yaml > index 4f9185462ed3..4dc30738ee57 100644 > --- a/Documentation/devicetree/bindings/display/ti/ti,am65x-dss.yaml > +++ b/Documentation/devicetree/bindings/display/ti/ti,am65x-dss.yaml > @@ -55,6 +55,14 @@ properties: > - const: vp1 > - const: vp2 > > + assigned-clocks: > + minItems: 1 > + maxItems: 3 > + > + assigned-clock-parents: > + minItems: 1 > + maxItems: 3 > + Those properties can occur in any node that has clocks. Do we need to specify them explicitly in every schema ? > interrupts: > maxItems: 1 > > @@ -62,6 +70,9 @@ properties: > maxItems: 1 > description: phandle to the associated power domain > > + dma-coherent: > + type: boolean > + > ports: > type: object > description: -- Regards, Laurent Pinchart
