On Wed, Feb 21, 2024 at 11:34 AM Conor Dooley <conor@xxxxxxxxxx> wrote: > > On Tue, Feb 20, 2024 at 08:13:31PM -0800, Saravana Kannan wrote: > > I made that fix and now I'm getting this: > > $ make DT_CHECKER_FLAGS=-m dt_binding_check > > DT_SCHEMA_FILES=Documentation/devicetree/bindings/post-init-suppliers.yaml > > DTEX Documentation/devicetree/bindings/post-init-suppliers.example.dts > > LINT Documentation/devicetree/bindings > > CHKDT Documentation/devicetree/bindings/processed-schema.json > > /mnt/android/linus-tree/Documentation/devicetree/bindings/post-init-suppliers.yaml: > > 'oneOf' conditional failed, one must be fixed: > > 'unevaluatedProperties' is a required property > > 'additionalProperties' is a required property > > hint: Either unevaluatedProperties or additionalProperties > > must be present > > from schema $id: http://devicetree.org/meta-schemas/core.yaml# > > SCHEMA Documentation/devicetree/bindings/processed-schema.json > > /mnt/android/linus-tree/Documentation/devicetree/bindings/tpm/ibm,vtpm.yaml: > > ignoring, error in schema: properties > > /mnt/android/linus-tree/Documentation/devicetree/bindings/post-init-suppliers.yaml: > > ignoring, error in schema: > > /mnt/android/linus-tree/Documentation/devicetree/bindings/soc/tegra/nvidia,tegra20-pmc.yaml: > > ignoring, error in schema: allOf: 0: then: properties: pinmux > > /mnt/android/linus-tree/Documentation/devicetree/bindings/net/lantiq,pef2256.yaml: > > ignoring, error in schema: properties: lantiq,data-rate-bps > > /mnt/android/linus-tree/Documentation/devicetree/bindings/post-init-supplier.yaml: > > ignoring, error in schema: > > /mnt/android/linus-tree/Documentation/devicetree/bindings/iio/pressure/honeywell,mprls0025pa.yaml: > > ignoring, error in schema: properties: honeywell,pmax-pascal > > /mnt/android/linus-tree/Documentation/devicetree/bindings/iio/pressure/honeywell,hsc030pa.yaml: > > ignoring, error in schema: properties: honeywell,pmax-pascal > > > DTC_CHK Documentation/devicetree/bindings/post-init-suppliers.example.dtb > > Documentation/devicetree/bindings/post-init-suppliers.example.dtb:0:0: > > /example-0/clock-controller@1000: failed to match any schema with > > compatible: ['vendor,soc4-gcc', 'vendor,soc1-gcc'] > > Documentation/devicetree/bindings/post-init-suppliers.example.dtb:0:0: > > /example-0/clock-controller@1000: failed to match any schema with > > compatible: ['vendor,soc4-gcc', 'vendor,soc1-gcc'] > > Documentation/devicetree/bindings/post-init-suppliers.example.dtb:0:0: > > /example-0/clock-controller@2000: failed to match any schema with > > compatible: ['vendor,soc4-dispcc', 'vendor,soc1-dispcc'] > > Documentation/devicetree/bindings/post-init-suppliers.example.dtb:0:0: > > /example-0/clock-controller@2000: failed to match any schema with > > compatible: ['vendor,soc4-dispcc', 'vendor,soc1-dispcc'] > > FWIW, I don't see these or the other errors you see above. You really > need to get yourself a newer version of dt-schema, or else avoid > working on this using whatever castrated system google provides you with! Ok, finally found the workaround to updating these packages and the output is a lot cleaner now. > > But I guess the "oneOf" error is because the yaml is being treated as > > a description of a DT node and not a schema? > > The oneOf is due to missing "additionalProperties: true" - As far as I > understand you need that regardless of whether this is going into > dt-schema or the kernel. Ok, I added that and the errors go away. I'll send out a v3 and hopefully Rob can pick it up. -Saravana
