From: Cao Minh Hiep <cm-hiep@jinso.co.jp>
To: geert+renesas@glider.be
Cc: broonie@kernel.org, linux-spi@vger.kernel.org,
kuninori.morimoto.gx@renesas.com,
yoshihiro.shimoda.uh@renesas.com, ryusuke.sakato.bx@renesas.com,
linux-sh@vger.kernel.org
Subject: [PATCH v3 0/1] spi: Using Trigger number to transmit/receive data
Date: Thu, 23 Oct 2014 12:14:12 +0900 [thread overview]
Message-ID: <1414034053-14750-1-git-send-email-cm-hiep@jinso.co.jp> (raw)
From: Hiep Cao Minh <cm-hiep@jinso.co.jp>
Hi Geert-san,
I have updated a new version of the QSPI patch (verion 3), that I modified as
your comments. This patch supports for r8a7790 SOC and developed base on the
upstream-stable-v3.17 and have tested on the Lager board.
Please consider the following patches for the r8a7790 Soc.
Version 2:
Added the DMA support on it.In order to use DMA When the DMA is available.
This patch supports for r8a7790 SOC and developed base on the upstream-v3.17-rc7
and have tested on the Lager board.
Version 1:
This is the patch of QSPI that support for r8a7790 SOC. The pupose of
this patch is to transmit and receive the 32 bytes of data when the data
already has prepared on Transmit/Receive Buffer. Using Transmit/Receive
Buffer Data Trigger Number to do that instead transmits/receives a byte
of data. With this patch will improve the speed of transfer data.
This patch was developed base on the upstream-v3.17-rc5 and have
tested on the Lager board.
Best Regards,
Cao Minh Hiep
Hiep Cao Minh (1):
spi: Using Trigger number to transmit/receive data
drivers/spi/spi-rspi.c | 124 ++++++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 117 insertions(+), 7 deletions(-)
--
1.9.1
next reply other threads:[~2014-10-23 3:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 3:14 Cao Minh Hiep [this message]
[not found] ` <1414034053-14750-1-git-send-email-cm-hiep-HEF513clHfp3+QwDJ9on6Q@public.gmane.org>
2014-10-23 3:14 ` [PATCH v3 1/1] spi: Using Trigger number to transmit/receive data Cao Minh Hiep
[not found] ` <1414034053-14750-2-git-send-email-cm-hiep-HEF513clHfp3+QwDJ9on6Q@public.gmane.org>
2015-03-30 4:30 ` Mark Brown
2015-03-31 5:24 ` Cao Minh Hiep
2015-04-07 18:51 ` Geert Uytterhoeven
2015-04-20 7:04 ` Cao Minh Hiep
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=1414034053-14750-1-git-send-email-cm-hiep@jinso.co.jp \
--to=cm-hiep@jinso.co.jp \
--cc=broonie@kernel.org \
--cc=geert+renesas@glider.be \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-sh@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=ryusuke.sakato.bx@renesas.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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).