As discussed with Krzysztof and Chris, it seems like each NAND controller binding should actually explicitely list all the allowed properties in a schema and use "unevaluatedProperties: false" in both the NAND controller and the NAND chip sections. While this restriction always applied on the controller side, this was not enforced on the chips side AFAIR. Link: https://lore.kernel.org/all/a23dd485-a3d9-e31f-be3e-0ab293fcfc4a@xxxxxxxxxx/ While converting Marvell controller bindings, Chris explicitely pointed similar bindings which would also trigger errors when using "unevaluatedProperties: false" because of the reg/partitions/etc properties not being described. Here is an attempt at making these more precise and robust. These change made me realize the qcom,boot-partition property description was broken, so here is a fix for it. Thanks, Miquèl Miquel Raynal (3): dt-bindings: mtd: qcom: Fix a property position dt-bindings: mtd: qcom: Prevent NAND chip unevaluated properties dt-bindings: mtd: ingenic: Prevent NAND chip unevaluated properties .../devicetree/bindings/mtd/ingenic,nand.yaml | 11 +++++ .../devicetree/bindings/mtd/qcom,nandc.yaml | 47 ++++++++++++------- 2 files changed, 42 insertions(+), 16 deletions(-) -- 2.34.1
