From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <michael@walle.cc>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Mark Brown <broonie@kernel.org>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mtd: jedec,spi-nor: Document CPOL/CPHA support
Date: Tue, 14 Feb 2023 15:44:33 +0100 [thread overview]
Message-ID: <20230214154433.6a421c51@xps-13> (raw)
In-Reply-To: <afe470603028db9374930b0c57464b1f6d52bdd3.1676384304.git.geert+renesas@glider.be>
Hi Geert, Krzysztof, Rob,
geert+renesas@glider.be wrote on Tue, 14 Feb 2023 15:26:43 +0100:
> SPI EEPROMs typically support both SPI Mode 0 (CPOL=CPHA=0) and Mode 3
> (CPOL=CPHA=1). However, using the latter is currently flagged as an
> error by "make dtbs_check", e.g.:
>
> arch/arm/boot/dts/r8a7791-koelsch.dtb: flash@0: Unevaluated properties are not allowed ('spi-cpha', 'spi-cpol' were unexpected)
> From schema: Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml
>
> Fix this by documenting support for CPOL=CPHA=1.
>
> Fixes: 233363aba72ac638 ("spi/panel: dt-bindings: drop CPHA and CPOL from common properties")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml b/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml
> index f86255ce13af0871..bb62ac4585822982 100644
> --- a/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml
> +++ b/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml
> @@ -76,6 +76,13 @@ properties:
> If "broken-flash-reset" is present then having this property does not
> make any difference.
>
> + spi-cpol: true
> + spi-cpha: true
I see that spi-cpol and spi-cpha are described in spi-controller.yaml
which references spi-peripheral-props.yaml, but jedec,spi-nor.yaml
only references spi-peripheral-props.yaml leading to spi-cpol and
spi-cpha not being recognized as valid properties.
Wouldn't it be cleaner to to have these two properties defined in
spi-peripheral-props.yaml instead?
> +
> +dependencies:
> + spi-cpol: [ spi-cpha ]
> + spi-cpha: [ spi-cpol ]
> +
> unevaluatedProperties: false
>
> examples:
Thanks,
Miquèl
next prev parent reply other threads:[~2023-02-14 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 14:26 [PATCH] dt-bindings: mtd: jedec,spi-nor: Document CPOL/CPHA support Geert Uytterhoeven
2023-02-14 14:44 ` Miquel Raynal [this message]
2023-02-14 15:22 ` Geert Uytterhoeven
2023-02-14 15:56 ` Miquel Raynal
2023-02-17 23:27 ` Rob Herring
2023-02-16 10:38 ` Krzysztof Kozlowski
2023-03-17 8:55 ` Tudor Ambarus
2023-03-22 16:08 ` Miquel Raynal
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=20230214154433.6a421c51@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=michael@walle.cc \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--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).