On Mon, Jul 29, 2019 at 8:23 AM Torsten Duwe <duwe@xxxxxx> wrote: > > On Fri, Jul 26, 2019 at 06:36:01PM +0200, Maxime Ripard wrote: > > > + > > > + dvdd12-supply: > > > + maxItems: 1 > > > + description: Regulator for 1.2V digital core power. > > > + $ref: /schemas/types.yaml#/definitions/phandle > > > + > > > + dvdd25-supply: > > > + maxItems: 1 > > > + description: Regulator for 2.5V digital core power. > > > + $ref: /schemas/types.yaml#/definitions/phandle > > > > There's no need to specify the type here, all the properties ending in > > -supply are already checked for that type > > Ok, thanks for the hint. > > > > + ports: > > > + type: object > > > + minItems: 1 > > > + maxItems: 2 > > > + description: | > > > + Video port 0 for LVTTL input, > > > + Video port 1 for eDP output (panel or connector) > > > + using the DT bindings defined in > > > + Documentation/devicetree/bindings/media/video-interfaces.txt > > > > You should probably describe the port@0 and port@1 nodes here as > > well. It would allow you to express that the port 0 is mandatory and > > the port 1 optional, which got dropped in the conversion. > > I would have liked to, but have not discovered yet a comprehensive source > of information about recommended syntax and semantics of the YAML schemes. The language is json-schema. > Is there some central reference for these types of issues? I mean not the > "here is a git repo with the meta-schemes" but sort of a cookbook? Documentation/devicetree/writing-schema.md (soon .rst) and Documentation/devicetree/bindings/example-schema.yaml attempt to do this. Any feedback on them would be helpful. For this case specifically, we do need to define a common graph schema, but haven't yet. You can assume we do and only really need to capture what Maxime said above. Rob _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
