On Sun, Aug 18, 2024 at 07:44:22PM +0200, Krzysztof Kozlowski wrote: > On 18/08/2024 19:41, Laurent Pinchart wrote: > > Hi Krzysztof, > > > > Thank you for the patch. > > > > On Sun, Aug 18, 2024 at 07:30:02PM +0200, Krzysztof Kozlowski wrote: > >> Each variable-length property like interrupts or resets must have fixed > >> constraints on number of items for given variant in binding. The > >> clauses in "if:then:" block should define both limits: upper and lower. > > > > I thought that, when only one of minItems or maxItems was specified, the > > other automatically defaulted to the same value. I'm pretty sure I > > recall Rob asking me to drop one of the two in some bindings. Has the > > rule changes ? Is it documented somewhere ? > > New dtschema changed it and, even if previous behavior is restored, the > size in if:then: always had to be constrained. You could have skipped > one side of limit if it was equal to outer/top-level limit, e.g: > > properties: > clocks: > minItems: 1 > maxItems: 2 > > > if:then:properties: > clocks: > minItems: 2 Where can I find a description of the behaviour of the new dtschema (hopefully with some documentation) ? -- Regards, Laurent Pinchart
