On Mon, Sep 28, 2026 at 08:23:45PM +0100, Mark Brown wrote:
> On Mon, Sep 28, 2026 at 06:24:41PM +0200, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> > 
> > Convert Tegra AHUB bindings from the free-form text format to
> > json-schema.
> 
> > -- compatible : For Tegra30, must contain "nvidia,tegra30-ahub".  For Tegra114,
> > -  must contain "nvidia,tegra114-ahub".  For Tegra124, must contain
> > -  "nvidia,tegra124-ahub".  Otherwise, must contain "nvidia,<chip>-ahub",
> > -  plus at least one of the above, where <chip> is tegra132.
> 
> This documents fallbacks...
> 
> > +properties:
> > +  compatible:
> > +    enum:
> > +      - nvidia,tegra30-ahub
> > +      - nvidia,tegra114-ahub
> > +      - nvidia,tegra124-ahub
> 
> ...but this does not.

In device tree we never used nvidia,tegra132-ahub, but I guess it's
technically necessary, so I'll add that combination here, exactly as
described in the original bindings, and fix up the device tree to use
that instead.

> 
> > +  resets:
> > +    minItems: 11
> > +    maxItems: 21
> > +
> > +  reset-names:
> > +    minItems: 11
> > +    maxItems: 21
> 
> Ideally there'd be per-SoC constraints but meh.

They are there, further down below, though maybe somewhat hidden. The
per-SoC constraints define the exact items that need to go into each of
these. Though I guess I could expand a bit more and narrow down the
minItems and maxItems for each compatible.

Thierry