linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cao Minh Hiep <cm-hiep@jinso.co.jp>
To: Mark Brown <broonie@kernel.org>
Cc: geert+renesas@glider.be, 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: Re: [PATCH v3 1/1] spi: Using Trigger number to transmit/receive data
Date: Tue, 31 Mar 2015 14:24:38 +0900	[thread overview]
Message-ID: <551A2F96.2050000@jinso.co.jp> (raw)
In-Reply-To: <20150330043049.GE1568@sirena.org.uk>

Hi Mark-san

On 2015年03月30日 13:30, Mark Brown wrote:
> On Thu, Oct 23, 2014 at 12:14:13PM +0900, Cao Minh Hiep wrote:
>> From: Hiep Cao Minh <cm-hiep@jinso.co.jp>
>>
>> In order to transmit and receive data when have 32 bytes of data that
>> ready has prepared on Transmit/Receive Buffer to transmit or receive.
>> Instead transmits/receives a byte data using Transmit/Receive Buffer
>> Data Triggering Number will improve the speed of transfer data.
> Applied, thanks.  It'd have helped to be more explicit about what a
> "trigger number" is here - it's not a commonly used term.  "Trigger
> level" is more normal.
Thank you very much!
Hiep.

  reply	other threads:[~2015-03-31  5:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23  3:14 [PATCH v3 0/1] spi: Using Trigger number to transmit/receive data Cao Minh Hiep
     [not found] ` <1414034053-14750-1-git-send-email-cm-hiep-HEF513clHfp3+QwDJ9on6Q@public.gmane.org>
2014-10-23  3:14   ` [PATCH v3 1/1] " 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 [this message]
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=551A2F96.2050000@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).