> On Mon, 31 May 2021 10:51:09 +0800, Ming Qian wrote: > > Add devicetree binding documentation for IMX8Q Video Processing Unit > > IP > > > > Signed-off-by: Ming Qian <ming.qian@xxxxxxx> > > Signed-off-by: Shijie Qin <shijie.qin@xxxxxxx> > > Signed-off-by: Zhou Peng <eagle.zhou@xxxxxxx> > > --- > > .../bindings/media/nxp,imx8q-vpu.yaml | 201 > ++++++++++++++++++ > > 1 file changed, 201 insertions(+) > > create mode 100644 > > Documentation/devicetree/bindings/media/nxp,imx8q-vpu.yaml > > > > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' > on your patch (DT_CHECKER_FLAGS is new in v5.13): > > yamllint warnings/errors: > ./Documentation/devicetree/bindings/media/nxp,imx8q-vpu.yaml:24:9: > [warning] wrong indentation: expected 10 but found 8 (indentation) > ./Documentation/devicetree/bindings/media/nxp,imx8q-vpu.yaml:67:13: > [warning] wrong indentation: expected 10 but found 12 (indentation) > ./Documentation/devicetree/bindings/media/nxp,imx8q-vpu.yaml:94:7: > [warning] wrong indentation: expected 8 but found 6 (indentation) > > dtschema/dtc warnings/errors: > /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/media > /nxp,imx8q-vpu.yaml: properties:mu_m0: Additional properties are not > allowed ('vpu_core' was unexpected) > hint: Keywords must be a subset of known json-schema keywords > from schema $id: > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdevicetr > ee.org%2Fmeta-schemas%2Fkeywords.yaml%23&data=04%7C01%7Cmin > g.qian%40nxp.com%7Ce1c1c81d4bf349f4551408d92501bba0%7C686ea1d3b > c2b4c6fa92cd99c5c301635%7C0%7C0%7C637581511648466898%7CUnkno > wn%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1ha > WwiLCJXVCI6Mn0%3D%7C1000&sdata=z5K2eJR%2FKDI7GZbxzI733VSgAI > R%2FI4sx9Visl21IJe8%3D&reserved=0 > /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/media > /nxp,imx8q-vpu.yaml: properties:mu_m0: 'vpu_core' is not one of ['$ref', > 'additionalItems', 'additionalProperties', 'allOf', 'anyOf', 'const', 'contains', > 'default', 'dependencies', 'deprecated', 'description', 'else', 'enum', > 'exclusiveMaximum', 'exclusiveMinimum', 'items', 'if', 'minItems', 'minimum', > 'maxItems', 'maximum', 'multipleOf', 'not', 'oneOf', 'pattern', > 'patternProperties', 'properties', 'required', 'then', 'type', 'typeSize', > 'unevaluatedProperties', 'uniqueItems'] > from schema $id: > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdevicetr > ee.org%2Fmeta-schemas%2Fkeywords.yaml%23&data=04%7C01%7Cmin > g.qian%40nxp.com%7Ce1c1c81d4bf349f4551408d92501bba0%7C686ea1d3b > c2b4c6fa92cd99c5c301635%7C0%7C0%7C637581511648466898%7CUnkno > wn%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1ha > WwiLCJXVCI6Mn0%3D%7C1000&sdata=z5K2eJR%2FKDI7GZbxzI733VSgAI > R%2FI4sx9Visl21IJe8%3D&reserved=0 > /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/media > /nxp,imx8q-vpu.yaml: 'oneOf' conditional failed, one must be fixed: > 'unevaluatedProperties' is a required property > 'additionalProperties' is a required property > hint: A schema with a "$ref" to another schema either can define all > properties used and use "additionalProperties" or can use > "unevaluatedProperties" > from schema $id: > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdevicetr > ee.org%2Fmeta-schemas%2Fbase.yaml%23&data=04%7C01%7Cming.qia > n%40nxp.com%7Ce1c1c81d4bf349f4551408d92501bba0%7C686ea1d3bc2b4 > c6fa92cd99c5c301635%7C0%7C0%7C637581511648466898%7CUnknown%7 > CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiL > CJXVCI6Mn0%3D%7C1000&sdata=5XtViMjNpB5Xk6d82g%2FCb54xz2J2jK > crmhXa5cusqNA%3D&reserved=0 > /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/media > /nxp,imx8q-vpu.yaml: ignoring, error in schema: properties: mu_m0 > warning: no schema found in > file: ./Documentation/devicetree/bindings/media/nxp,imx8q-vpu.yaml > Documentation/devicetree/bindings/media/nxp,imx8q-vpu.example.dt.yaml:0: > 0: /example-0/vpu-bus@2c000000: failed to match any schema with > compatible: ['nxp,imx8qm-vpu', 'simple-bus'] > Documentation/devicetree/bindings/media/nxp,imx8q-vpu.example.dt.yaml:0: > 0: /example-0/vpu-bus@2c000000/vpu_decoder@2d080000: failed to match > any schema with compatible: ['nxp,imx8q-vpu-decoder'] > Documentation/devicetree/bindings/media/nxp,imx8q-vpu.example.dt.yaml:0: > 0: /example-0/vpu-bus@2c000000/vpu_encoder@2d090000: failed to match > any schema with compatible: ['nxp,imx8q-vpu-encoder'] > Documentation/devicetree/bindings/media/nxp,imx8q-vpu.example.dt.yaml:0: > 0: /example-0/vpu-bus@2c000000/vpu_encoder@2d0a0000: failed to match > any schema with compatible: ['nxp,imx8q-vpu-encoder'] > > See > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchw > ork.ozlabs.org%2Fpatch%2F1485530&data=04%7C01%7Cming.qian%40n > xp.com%7Ce1c1c81d4bf349f4551408d92501bba0%7C686ea1d3bc2b4c6fa92 > cd99c5c301635%7C0%7C0%7C637581511648466898%7CUnknown%7CTWF > pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC > I6Mn0%3D%7C1000&sdata=UuQ%2Fc7p6ybq5AQPNjxUHRqYCImyKvVeY > 9UQCfeiE94g%3D&reserved=0 > > This check can fail if there are any dependencies. The base for a patch series is > generally the most recent rc1. > > If you already ran 'make dt_binding_check' and didn't see the above error(s), > then make sure 'yamllint' is installed and dt-schema is up to > date: > > pip3 install dtschema --upgrade > > Please check and re-submit. Hi Rob, I have found the problem, I 'll fix it and re-submit soon