devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Illia Smyrnov <x0194613@ti.com>
Cc: Illia Smyrnov <illia.smyrnov@ti.com>,
	Grant Likely <grant.likely@linaro.org>,
	Rob Herring <rob.herring@calxeda.com>,
	Rob Landley <rob@landley.net>, Daniel Mack <zonque@gmail.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Tony Lindgren <tony@atomide.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	spi-devel-general@lists.sourceforge.net
Subject: Re: [PATCH 1/2] spi: spi-omap2-mcspi.c: Add dts for slave device configuration.
Date: Thu, 6 Jun 2013 11:19:19 +0100	[thread overview]
Message-ID: <20130606101919.GQ31367@sirena.org.uk> (raw)
In-Reply-To: <51B05FAE.60508@ti.com>

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

On Thu, Jun 06, 2013 at 01:08:46PM +0300, Illia Smyrnov wrote:
> On 06/05/2013 02:57 PM, Mark Brown wrote:

> Turbo mode gives the expected results not for all cases. There are
> some limitations:
> - works only if a single channel is enabled (no effect when several
> channels are enable);
> - improves the throughput on RX direction only;
> - effective only when a transfer exceeds two words. For single SPI
> word transfers OMAP TRM [1] recommends deactivate turbo mode.

> So it is useful to have the property in DT, that allow us to switch
> turbo mode off/on for certain slave.

Why?  These sound like conditions that can readily be detected at
runtime.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-06-06 10:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 11:39 [PATCH 0/2] spi: omap2-mcspi: add FIFO buffer support Illia Smyrnov
2013-06-05 11:39 ` [PATCH 1/2] spi: spi-omap2-mcspi.c: Add dts for slave device configuration Illia Smyrnov
     [not found]   ` <1370432398-7796-2-git-send-email-illia.smyrnov-l0cyMroinI0@public.gmane.org>
2013-06-05 11:57     ` Mark Brown
     [not found]       ` <20130605115734.GY31367-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-06-06 10:08         ` Illia Smyrnov
2013-06-06 10:19           ` Mark Brown [this message]
     [not found] ` <1370432398-7796-1-git-send-email-illia.smyrnov-l0cyMroinI0@public.gmane.org>
2013-06-05 11:39   ` [PATCH 2/2] spi: omap2-mcspi: Add FIFO buffer support Illia Smyrnov
2013-06-05 12:03     ` Mark Brown
     [not found]       ` <20130605120346.GZ31367-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-06-06 10:08         ` Illia Smyrnov
     [not found]           ` <51B05FB8.6050903-l0cyMroinI0@public.gmane.org>
2013-06-06 10:30             ` Mark Brown
     [not found]               ` <20130606103032.GR31367-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-06-11 17:09                 ` Illia Smyrnov

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=20130606101919.GQ31367@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=illia.smyrnov@ti.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=spi-devel-general@lists.sourceforge.net \
    --cc=tony@atomide.com \
    --cc=x0194613@ti.com \
    --cc=zonque@gmail.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).