Re: [PATCH v4 08/15] Documentation: of: Convert graph bindings to json-schema

[Sameer Pujar]

> > > Signed-off-by: Sameer Pujar <spujar@xxxxxxxxxx>
> > > Cc: Philipp Zabel <p.zabel@xxxxxxxxxxxxxx>
> > > ---
> > >   Documentation/devicetree/bindings/graph.txt  | 128 --------------------
> The removed Documentation/devicetree/bindings/graph.txt is referenced by
> a lot of files, tree-wide. Should the references be updated in the same
> series?

May be possible to include in the same series if it is just about using 
'graph.yaml' reference instead of 'graph.txt' in various files.

...

> > > +%YAML 1.2
> > > +---
> > > +$id: http://devicetree.org/schemas/graph.yaml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: Common bindings for device graphs
> > > +
> > > +description: |
> > > +  The hierarchical organisation of the device tree is well suited to describe
> > > +  control flow to devices, but there can be more complex connections between
> > > +  devices that work together to form a logical compound device, following an
> > > +  arbitrarily complex graph.
> > > +  There already is a simple directed graph between devices tree nodes using
> > > +  phandle properties pointing to other nodes to describe connections that
> > > +  can not be inferred from device tree parent-child relationships. The device
> > > +  tree graph bindings described herein abstract more complex devices that can
> > > +  have multiple specifiable ports, each of which can be linked to one or more
> > > +  ports of other devices.
> > > +
> > > +  These common bindings do not contain any information about the direction or
> > > +  type of the connections, they just map their existence. Specific properties
> > > +  may be described by specialized bindings depending on the type of connection.
> > > +
> > > +  To see how this binding applies to video pipelines, for example, see
> > > +  Documentation/devicetree/bindings/media/video-interfaces.txt.
> > > +  Here the ports describe data interfaces, and the links between them are
> > > +  the connecting data buses. A single port with multiple connections can
> > > +  correspond to multiple devices being connected to the same physical bus.
> > > +
> > > +maintainers:
> > > +  - Philipp Zabel <p.zabel@xxxxxxxxxxxxxx>
> > > +
> > > +definitions:
> > > +
> > > +  port:
> > > +    type: object
> > > +    description: |
> > > +      If there is more than one 'port' or more than one 'endpoint' node
> > > +      or 'reg' property present in the port and/or endpoint nodes then
> > > +      '#address-cells' and '#size-cells' properties are required in relevant
> > > +      parent node.
> > reg property.
> What about #address-cells and #size-cells in port and ports nodes?
> These must either be #address-cells = <1>, #size-cells = <0>, or they
> can be absent if the parent node already has the same, or if a port node
> only contains a single endpoint.

Yes, will list these properties for port/ports.

...