[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2671d488-82a1-8720-d9a1-03554d955a38@gmail.com>
Date: Tue, 18 Jun 2019 14:01:40 +0200
From: Marek Vasut <marek.vasut@...il.com>
To: masonccyang@...c.com.tw, Lee Jones <lee.jones@...aro.org>
Cc: bbrezillon@...nel.org, broonie@...nel.org,
devicetree@...r.kernel.org,
Geert Uytterhoeven <geert+renesas@...der.be>,
Simon Horman <horms@...ge.net.au>, juliensu@...c.com.tw,
linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
linux-spi@...r.kernel.org, mark.rutland@....com,
miquel.raynal@...tlin.com, robh+dt@...nel.org,
Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
Subject: Re: [PATCH v13 3/3] dt-bindings: mfd: Document Renesas R-Car Gen3
RPC-IF controller bindings
On 6/6/19 9:40 AM, masonccyang@...c.com.tw wrote:
[...]
> RPC-IF works either in SPI or HyperFlash is decided by external hardware
> pins
> configuration and it can NOT switch it's operation mode in the run time.
> This is not like my understanding of MFD.
Which external hardware pins decide the RPC configuration ?
It seems to me like PHYCNT register, PHYMEM bitfield, selects what
device is connected, and then a couple of other bits control the
communication, but I see nothing which would be tied to any external
configuration pins.
[...]
--
Best regards,
Marek Vasut
Powered by blists - more mailing lists