вт, 19 серп. 2025 р. о 23:27 Rob Herring <r...@kernel.org> пише:
>
> On Tue, Aug 19, 2025 at 03:16:16PM +0300, Svyatoslav Ryhel wrote:
> > Parallel VI interface found in Tegra30 is exactly the same as Tegra20 has.
>
> That's not what the compatible schema says. 'exactly the same' implies a
> fallback to whatever it is exactly the same as.
>
> >
> > Signed-off-by: Svyatoslav Ryhel <clamo...@gmail.com>
> > ---
> > .../devicetree/bindings/display/tegra/nvidia,tegra20-vip.yaml | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git
> > a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-vip.yaml
> > b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-vip.yaml
> > index 14294edb8d8c..39e9b3297dbd 100644
> > ---
> > a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-vip.yaml
> > +++
> > b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-vip.yaml
> > @@ -13,6 +13,7 @@ properties:
> > compatible:
> > enum:
> > - nvidia,tegra20-vip
> > + - nvidia,tegra30-vip
> >
Rob, may I use this:
properties:
compatible:
one0f:
- const: nvidia,tegra20-vip
- items:
- const: nvidia,tegra30-vip
- const: nvidia,tegra20-vip
Among all Tegra SoC only 2 have VIP support Tegra20 and Tegra30.
Tegra30 is backwards compatible with Tegra20 so we can use fallback.
There should be no new generation added to this schema.
OR should I use enum?
properties:
compatible:
one0f:
- enum:
- nvidia,tegra20-vip
- items:
- const: nvidia,tegra30-vip
- const: nvidia,tegra20-vip
> > ports:
> > $ref: /schemas/graph.yaml#/properties/ports
> > --
> > 2.48.1
> >
