LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com> To: Rob Herring <robh@kernel.org>, Mason Yang <masonccyang@mxic.com.tw> Cc: broonie@kernel.org, linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org, bbrezillon@kernel.org, linux-renesas-soc@vger.kernel.org, Geert Uytterhoeven <geert+renesas@glider.be>, lee.jones@linaro.org, sergei.shtylyov@cogentembedded.com, mark.rutland@arm.com, devicetree@vger.kernel.org, juliensu@mxic.com.tw, Simon Horman <horms@verge.net.au>, zhengxunli@mxic.com.tw Subject: Re: [PATCH v12 3/3] dt-bindings: mfd: Document Renesas R-Car Gen3 RPC-IF MFD bindings Date: Wed, 24 Apr 2019 23:54:30 +0200 [thread overview] Message-ID: <65853dc2-6f3c-1494-7e72-54877797cdd2@gmail.com> (raw) In-Reply-To: <20190424212356.GA27103@bogus> On 4/24/19 11:23 PM, Rob Herring wrote: > On Wed, Apr 24, 2019 at 03:55:36PM +0800, Mason Yang wrote: >> Document the bindings used by the Renesas R-Car Gen3 RPC-IF MFD. >> >> Signed-off-by: Mason Yang <masonccyang@mxic.com.tw> >> --- >> .../devicetree/bindings/mfd/mfd-renesas-rpc.txt | 40 ++++++++++++++++++++++ >> 1 file changed, 40 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/mfd/mfd-renesas-rpc.txt >> >> diff --git a/Documentation/devicetree/bindings/mfd/mfd-renesas-rpc.txt b/Documentation/devicetree/bindings/mfd/mfd-renesas-rpc.txt >> new file mode 100644 >> index 0000000..668b822 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/mfd/mfd-renesas-rpc.txt >> @@ -0,0 +1,40 @@ >> +Renesas R-Car Gen3 RPC-IF MFD Device Tree Bindings >> +-------------------------------------------------- > > Looks like a SPI flash controller from the example. What makes it an > MFD? It supports both SPI NOR and HyperFlash (CFI-compliant flash with different bus interface). >> + >> +Required properties: >> +- compatible: should be an SoC-specific compatible value, followed by >> + "renesas,rcar-gen3-rpc" as a fallback. >> + supported SoC-specific values are: >> + "renesas,r8a77995-rpc" (R-Car D3) >> +- reg: should contain three register areas: >> + first for the base address of RPC-IF registers, >> + second for the direct mapping read mode and >> + third for the write buffer area. >> +- reg-names: should contain "regs", "dirmap" and "wbuf" >> +- clocks: should contain 1 entries for the module's clock >> +- clock-names: should contain "rpc" >> +- #address-cells: should be 1 >> +- #size-cells: should be 0 >> + >> +Example: >> + >> + rpc: rpc-if@ee200000 { >> + compatible = "renesas,r8a77995-rpc", "renesas,rcar-gen3-rpc"; >> + reg = <0 0xee200000 0 0x200>, <0 0x08000000 0 0x4000000>, >> + <0 0xee208000 0 0x100>; >> + reg-names = "regs", "dirmap", "wbuf"; >> + clocks = <&cpg CPG_MOD 917>; >> + clock-names = "rpc"; >> + power-domains = <&sysc R8A77995_PD_ALWAYS_ON>; >> + resets = <&cpg 917>; >> + #address-cells = <1>; >> + #size-cells = <0>; >> + >> + flash@0 { >> + compatible = "jedec,spi-nor"; >> + reg = <0>; >> + spi-max-frequency = <40000000>; >> + spi-tx-bus-width = <1>; >> + spi-rx-bus-width = <1>; >> + }; >> + }; >> -- >> 1.9.1 >> -- Best regards, Marek Vasut
next prev parent reply other threads:[~2019-04-24 21:54 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-24 7:55 [PATCH v12 0/3] mfd: Add Renesas R-Car Gen3 RPC-IF MFD & SPI driver Mason Yang 2019-04-24 7:55 ` [PATCH v12 1/3] mfd: Add Renesas R-Car Gen3 RPC-IF MFD driver Mason Yang 2019-04-24 7:55 ` [PATCH v12 2/3] spi: Add Renesas R-Car Gen3 RPC-IF SPI controller driver Mason Yang 2019-05-14 6:52 ` Lee Jones 2019-05-15 5:55 ` masonccyang 2019-05-15 7:16 ` Lee Jones 2019-04-24 7:55 ` [PATCH v12 3/3] dt-bindings: mfd: Document Renesas R-Car Gen3 RPC-IF MFD bindings Mason Yang 2019-04-24 21:23 ` Rob Herring 2019-04-24 21:54 ` Marek Vasut [this message] 2019-04-25 23:07 ` Rob Herring 2019-04-26 1:44 ` Marek Vasut 2019-05-07 12:57 ` Lee Jones [not found] ` <OF08A5650B.8AE8977C-ON482583F4.000E5B1E-482583F4.000F7215@mxic.com.tw> 2019-05-08 3:52 ` Marek Vasut 2019-05-08 6:11 ` Lee Jones [not found] ` <OFE86674B9.06D723A0-ON482583F5.000AD50C-482583F5.000BA075@mxic.com.tw> 2019-05-09 19:23 ` Sergei Shtylyov [not found] ` <OFB19BCE91.6EBBAA77-ON482583F6.000234E2-482583F6.00061290@mxic.com.tw> 2019-05-13 7:11 ` Geert Uytterhoeven [not found] ` <OFD932ABFC.E3FFCEB8-ON482583F9.003412B1-482583F9.0034D5CA@mxic.com.tw> 2019-05-13 14:43 ` Geert Uytterhoeven 2019-05-14 2:33 ` masonccyang 2019-05-13 19:08 ` Sergei Shtylyov 2019-05-14 9:46 ` masonccyang 2019-05-14 10:07 ` Geert Uytterhoeven 2019-05-14 20:27 ` Sergei Shtylyov 2019-05-20 7:23 ` masonccyang 2019-05-20 7:44 ` Geert Uytterhoeven 2019-05-21 1:28 ` masonccyang 2019-05-22 16:32 ` Sergei Shtylyov 2019-05-22 17:05 ` Geert Uytterhoeven 2019-05-22 17:23 ` Sergei Shtylyov 2019-05-22 17:44 ` Geert Uytterhoeven [not found] ` <OFAD9AA573.86373900-ON482583FA.0034781A-482583FA.0035B40C@LocalDomain> 2019-05-14 10:00 ` masonccyang
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=65853dc2-6f3c-1494-7e72-54877797cdd2@gmail.com \ --to=marek.vasut@gmail.com \ --cc=bbrezillon@kernel.org \ --cc=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=geert+renesas@glider.be \ --cc=horms@verge.net.au \ --cc=juliensu@mxic.com.tw \ --cc=lee.jones@linaro.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=linux-spi@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=masonccyang@mxic.com.tw \ --cc=robh@kernel.org \ --cc=sergei.shtylyov@cogentembedded.com \ --cc=zhengxunli@mxic.com.tw \ /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: linkBe 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).