Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider: - [Low] The JSON Schema keyword `maxItems` is misspelled as `maxitems` in the `memory-region-names` property definition. --
commit ee391cd788a9c41587882f086abaab0871d4967e Author: Thierry Reding <[email protected]> dt-bindings: display: tegra: Document memory regions This commit adds memory-region and memory-region-names properties to the display controllers and host1x engine bindings for Tegra generations. These regions allow access to firmware-provided framebuffer memory and the video protection region. > diff --git > a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml > b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml > index 69be95afd5627..a012644eeb7d7 100644 > --- a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml > +++ b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml [ ... ] > @@ -65,7 +65,15 @@ properties: > items: > - description: phandle to the core power domain > > - memory-region: true > + memory-region: > + minItems: 1 > + maxItems: 2 > + > + memory-region-names: > + items: > + enum: [ framebuffer, protected ] > + minItems: 1 > + maxitems: 2 [Severity: Low] Is this meant to be maxItems? The lowercase spelling maxitems might be ignored by the JSON schema validator, which would fail to enforce the upper array bound limit or cause a meta-schema validation error when running make dt_binding_check. > > nvidia,head: > $ref: /schemas/types.yaml#/definitions/uint32 -- Sashiko AI review ยท https://sashiko.dev/#/patchset/[email protected]?part=2
