From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Mark Brown <broonie@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: spi: renesas,sh-msiof: Miscellaneous improvements
Date: Mon, 20 Mar 2023 11:05:21 -0500 [thread overview]
Message-ID: <20230320160521.GA1771933-robh@kernel.org> (raw)
In-Reply-To: <052af97ecbaa9ba6e0d406883dd3389fa397579a.1678891999.git.geert+renesas@glider.be>
On Wed, Mar 15, 2023 at 03:54:07PM +0100, Geert Uytterhoeven wrote:
> Make "clocks" and "power-domains" required everywhere.
> Make "resets" required on R-Car Gen2 and newer (i.e. all but SH-Mobile).
Breaking the ABI is fine because ???
>
> Update the example to match reality:
> - Use interrupt binding definitions instead of hardcoded numbers,
> - Convert to new-style CPG/MSSR bindings,
> - Add missing "power-domains" and "resets" properties.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> .../bindings/spi/renesas,sh-msiof.yaml | 23 +++++++++++++++----
> 1 file changed, 19 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/spi/renesas,sh-msiof.yaml b/Documentation/devicetree/bindings/spi/renesas,sh-msiof.yaml
> index 491a695a2deb3b83..00acbbb0f65dcf57 100644
> --- a/Documentation/devicetree/bindings/spi/renesas,sh-msiof.yaml
> +++ b/Documentation/devicetree/bindings/spi/renesas,sh-msiof.yaml
> @@ -149,23 +149,38 @@ required:
> - compatible
> - reg
> - interrupts
> + - clocks
> + - power-domains
> - '#address-cells'
> - '#size-cells'
>
> +if:
> + not:
> + properties:
> + compatible:
> + contains:
> + const: renesas,sh-mobile-msiof
> +then:
> + required:
> + - resets
> +
> unevaluatedProperties: false
>
> examples:
> - |
> - #include <dt-bindings/clock/r8a7791-clock.h>
> - #include <dt-bindings/interrupt-controller/irq.h>
> + #include <dt-bindings/clock/r8a7791-cpg-mssr.h>
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/power/r8a7791-sysc.h>
>
> msiof0: spi@e6e20000 {
> compatible = "renesas,msiof-r8a7791", "renesas,rcar-gen2-msiof";
> reg = <0xe6e20000 0x0064>;
> - interrupts = <0 156 IRQ_TYPE_LEVEL_HIGH>;
> - clocks = <&mstp0_clks R8A7791_CLK_MSIOF0>;
> + interrupts = <GIC_SPI 156 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&cpg CPG_MOD 000>;
> dmas = <&dmac0 0x51>, <&dmac0 0x52>;
> dma-names = "tx", "rx";
> + power-domains = <&sysc R8A7791_PD_ALWAYS_ON>;
> + resets = <&cpg 0>;
> #address-cells = <1>;
> #size-cells = <0>;
> };
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-03-20 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 14:54 [PATCH] dt-bindings: spi: renesas,sh-msiof: Miscellaneous improvements Geert Uytterhoeven
2023-03-20 16:05 ` Rob Herring [this message]
2023-03-20 16:16 ` Geert Uytterhoeven
2023-03-20 18:50 ` Mark Brown
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=20230320160521.GA1771933-robh@kernel.org \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
/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).