From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: masonccyang@mxic.com.tw
Cc: bbrezillon@kernel.org, broonie@kernel.org,
devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms@verge.net.au>,
juliensu@mxic.com.tw, lee.jones@linaro.org,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-spi@vger.kernel.org, marek.vasut@gmail.com,
mark.rutland@arm.com, robh+dt@kernel.org
Subject: Re: [PATCH v10 3/3] dt-bindings: mfd: Document Renesas R-Car Gen3 RPC-IF controller bindings
Date: Thu, 18 Apr 2019 19:55:59 +0300 [thread overview]
Message-ID: <9bc4847f-8e7e-3627-5394-6f2b5c5972bc@cogentembedded.com> (raw)
In-Reply-To: <OFCBCE0527.706EB4F2-ON482583E0.00200707-482583E0.00208EAD@mxic.com.tw>
Hello!
On 04/18/2019 08:55 AM, masonccyang@mxic.com.tw wrote:
>> > > > Document the bindings used by the Renesas R-Car Gen3 RPC-IF
>> MFD controller.
>> > > >
>> > > > Signed-off-by: Mason Yang <masonccyang@mxic.com.tw>
>> > > > ---
>> > > > .../devicetree/bindings/mfd/mfd-renesas-rpc.txt | 37 +++++++++
>> > > +++++++++++++
>> > > > 1 file changed, 37 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..bfb3d29
>> > > > --- /dev/null
>> > > > +++ b/Documentation/devicetree/bindings/mfd/mfd-renesas-rpc.txt
>> > > > @@ -0,0 +1,37 @@
>> > > > +Renesas R-Car Gen3 RPC-IF MFD controller Device Tree Bindings
>> > > > +-------------------------------------------------------------
>> > > > +
>> > > > +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 2 entries, one for the base address of rpc-
>> > > if registers,
>> > > > + and one for the direct mapping area
>> > > > +- reg-names: should contain "regs", and "dirmap"
>> > >
>> > > The device tree describes the hardware, not the driver. Why
>> did you remove
>> > > the "wbuf" area?
>> >
>> > I don't think we should describe the hardware that driver did not
>> implement it
>> > because there are still many RPC registers we don't use them.
>>
>> I have to repeat: we describe the hardware, not the driver capabilities.
>
> how about:
>
> - 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 an optional write buffer area.
> - reg-names: should contain "regs", "dirmap" and "wbuf"(optional).
>
> is it OK ?
No, the write buffer area is always there, at least on the gen3 chips.
(I forgot which other Renesas SoC has RPC-IF as well).
> thanks & best regards,
> Mason
MBR, Sergei
next prev parent reply other threads:[~2019-04-18 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 7:37 [PATCH v10 0/3] mfd: Add Renesas R-Car Gen3 RPC-IF MFD & SPI driver Mason Yang
2019-04-15 7:37 ` [PATCH v10 1/3] mfd: Add Renesas R-Car Gen3 RPC-IF MFD controller driver Mason Yang
2019-04-15 19:57 ` Sergei Shtylyov
[not found] ` <OF8A9D093C.B3035121-ON482583DE.00065F23-482583DE.00074AC0@mxic.com.tw>
2019-04-16 18:57 ` Sergei Shtylyov
[not found] ` <OF2BD84B79.FBC5E822-ON482583DF.0020009F-482583DF.0022E315@mxic.com.tw>
2019-04-17 20:26 ` Sergei Shtylyov
2019-04-15 7:37 ` [PATCH v10 2/3] spi: Add Renesas R-Car Gen3 RPC-IF SPI " Mason Yang
2019-04-16 18:37 ` Sergei Shtylyov
2019-04-15 7:37 ` [PATCH v10 3/3] dt-bindings: mfd: Document Renesas R-Car Gen3 RPC-IF controller bindings Mason Yang
2019-04-15 16:49 ` Sergei Shtylyov
[not found] ` <OF2F61A6E6.AA7717A3-ON482583DE.0005C1EE-482583DE.00061474@mxic.com.tw>
2019-04-16 8:02 ` Sergei Shtylyov
[not found] ` <OFCBCE0527.706EB4F2-ON482583E0.00200707-482583E0.00208EAD@mxic.com.tw>
2019-04-18 16:55 ` Sergei Shtylyov [this message]
2019-04-19 15:44 ` Sergei Shtylyov
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=9bc4847f-8e7e-3627-5394-6f2b5c5972bc@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=masonccyang@mxic.com.tw \
--cc=robh+dt@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
all inboxes | Powered by JetHome®