From: Marek Vasut <marek.vasut@gmail.com>
To: Mark Brown <broonie@kernel.org>, masonccyang@mxic.com.tw
Cc: bbrezillon@kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms@verge.net.au>,
juliensu@mxic.com.tw, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-spi@vger.kernel.org,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
zhengxunli@mxic.com.tw
Subject: Re: Applied "spi: Add Renesas R-Car Gen3 RPC-IF SPI controller driver" to the spi tree
Date: Wed, 13 Feb 2019 13:37:31 +0100 [thread overview]
Message-ID: <acb7940e-df38-97a7-8500-4825fb0f6604@gmail.com> (raw)
In-Reply-To: <20190213121635.GD7540@sirena.org.uk>
On 2/13/19 1:16 PM, Mark Brown wrote:
> On Wed, Feb 13, 2019 at 04:25:32PM +0800, masonccyang@mxic.com.tw wrote:
>
>> From current mainline branch, MFD seems support the device which is on
>> the same hardware bus(i.e, I2C, SPI, MMIO and SPMI)for multi-function
>> by Read/Write the common same registers.
>
> That's most MFDs but there are some that do some level of enumeration
> (even if it's just looking at the device ID that got registered) to
> decide what subdevices get registered, that's what people are suggesting
> here I think.
Right. Although I think some of the code could be shared between the SPI
and HF modes.
>> I am checking and not sure if MMIO of MFD could support RPC-IF for
>> different hardware bus on SPI and CFI.
>> I also doubt if this method is a correct solution for RPC-IF works
>> either in SPI mode or CFI mode.
>
> For MMIO devices MFD just passes through the parent resources.
>
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2019-02-13 12:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 6:49 [PATCH v8 0/2] spi: Add Renesas R-Car Gen3 RPC-IF SPI driver Mason Yang
2019-01-28 6:49 ` [PATCH v8 1/2] spi: Add Renesas R-Car Gen3 RPC-IF SPI controller driver Mason Yang
2019-02-12 14:22 ` Applied "spi: Add Renesas R-Car Gen3 RPC-IF SPI controller driver" to the spi tree Mark Brown
2019-02-12 14:33 ` Marek Vasut
2019-02-12 14:43 ` Mark Brown
2019-02-12 16:49 ` Mark Brown
[not found] ` <OF9C8DA179.15D69C0A-ON482583A0.00283EB5-482583A0.002E45C8@mxic.com.tw>
2019-02-13 12:16 ` Mark Brown
2019-02-13 12:37 ` Marek Vasut [this message]
[not found] ` <OF9B3A3A20.C0BF34B8-ON482583A1.002D5F3B-482583A1.00329653@mxic.com.tw>
2019-02-14 10:52 ` Marek Vasut
2019-03-07 17:50 ` [PATCH v8 1/2] spi: Add Renesas R-Car Gen3 RPC-IF SPI controller driver Sergei Shtylyov
2019-03-08 9:14 ` Geert Uytterhoeven
2019-03-08 17:32 ` Sergei Shtylyov
2019-03-22 17:43 ` Sergei Shtylyov
[not found] ` <OF7C1EB3FC.1ABCD2C2-ON482583C8.002D7A69-482583C8.002E899C@mxic.com.tw>
2019-03-25 19:12 ` Sergei Shtylyov
2019-03-26 16:42 ` Sergei Shtylyov
[not found] ` <OF5BDFBDAB.B66A1ADE-ON482583CA.0006C5C2-482583CA.0008788E@mxic.com.tw>
2019-03-27 10:20 ` Sergei Shtylyov
2019-01-28 6:49 ` [PATCH v8 2/2] dt-bindings: spi: Document Renesas R-Car Gen3 RPC-IF controller bindings Mason Yang
2019-02-12 14:22 ` Applied "dt-bindings: spi: Document Renesas R-Car Gen3 RPC-IF controller bindings" to the spi tree 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=acb7940e-df38-97a7-8500-4825fb0f6604@gmail.com \
--to=marek.vasut@gmail.com \
--cc=bbrezillon@kernel.org \
--cc=broonie@kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=juliensu@mxic.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=masonccyang@mxic.com.tw \
--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: 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).