From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <michael@walle.cc>, <linux-mtd@lists.infradead.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org,
Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
Manivannan Sadhasivam <mani@kernel.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Christian Marangi <ansuelsmth@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH 0/3] Fix a couple of missing unevaluated properties
Date: Tue, 6 Jun 2023 18:23:28 +0200 [thread overview]
Message-ID: <20230606182328.2ac7f0da@xps-13> (raw)
In-Reply-To: <20230606103057.137711-1-miquel.raynal@bootlin.com>
Hello,
miquel.raynal@bootlin.com wrote on Tue, 6 Jun 2023 12:30:54 +0200:
> 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@linaro.org/
The discussion pointed above has lead to another observation which also
needs to be fixed in this series. A v2 is coming soon.
> 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(-)
>
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2023-06-06 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 10:30 [PATCH 0/3] Fix a couple of missing unevaluated properties Miquel Raynal
2023-06-06 10:30 ` [PATCH 1/3] dt-bindings: mtd: qcom: Fix a property position Miquel Raynal
2023-06-06 10:30 ` [PATCH 2/3] dt-bindings: mtd: qcom: Prevent NAND chip unevaluated properties Miquel Raynal
2023-06-06 10:30 ` [PATCH 3/3] dt-bindings: mtd: ingenic: " Miquel Raynal
2023-06-06 16:23 ` Miquel Raynal [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230606182328.2ac7f0da@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mani@kernel.org \
--cc=michael@walle.cc \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=tudor.ambarus@linaro.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).