From: Marek Vasut <marek.vasut@gmail.com>
To: Mason Yang <masonccyang@mxic.com.tw>,
broonie@kernel.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org, boris.brezillon@bootlin.com,
linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
sergei.shtylyov@cogentembedded.com
Cc: juliensu@mxic.com.tw, Simon Horman <horms@verge.net.au>,
zhengxunli@mxic.com.tw
Subject: Re: [PATCH v4 0/2] spi: Add Renesas R-Car Gen3 RPC SPI driver
Date: Wed, 26 Dec 2018 20:06:13 +0100 [thread overview]
Message-ID: <80223417-2919-97c7-d9e3-0d0511a5a517@gmail.com> (raw)
In-Reply-To: <1545634358-17485-1-git-send-email-masonccyang@mxic.com.tw>
On 12/24/18 7:52 AM, Mason Yang wrote:
> Hi Mark,
>
> This Renesas R-Car Gen3 RPC SPI driver is based on Boris's new
> spi-mem direct mapping read/write mode [1][2].
Again, the RPC is NOT a SPI controller, it is dual SPI/HF controller.
[...]
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-12-26 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 6:52 [PATCH v4 0/2] spi: Add Renesas R-Car Gen3 RPC SPI driver Mason Yang
2018-12-24 6:52 ` [PATCH v4 1/2] spi: Add Renesas R-Car Gen3 RPC SPI controller driver Mason Yang
2018-12-25 15:49 ` Sergei Shtylyov
[not found] ` <OFC561D699.9746ACDB-ON4825836F.000CB709-4825836F.00184155@mxic.com.tw>
2018-12-26 10:57 ` Sergei Shtylyov
[not found] ` <OFE79BC6CE.BE217C13-ON48258377.001FBC09-48258377.00243859@mxic.com.tw>
2019-01-04 13:42 ` Sergei Shtylyov
2018-12-24 6:52 ` [PATCH v4 2/2] dt-bindings: spi: Document Renesas R-Car Gen3 RPC controller bindings Mason Yang
2018-12-24 8:14 ` Sergei Shtylyov
2018-12-26 19:07 ` Marek Vasut
2018-12-26 19:06 ` Marek Vasut [this message]
2018-12-27 19:08 ` [PATCH v4 0/2] spi: Add Renesas R-Car Gen3 RPC SPI driver 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=80223417-2919-97c7-d9e3-0d0511a5a517@gmail.com \
--to=marek.vasut@gmail.com \
--cc=boris.brezillon@bootlin.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.