From: Mark Brown <broonie@kernel.org>
To: Illia Smyrnov <illia.smyrnov@ti.com>
Cc: 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: Wed, 5 Jun 2013 12:57:34 +0100 [thread overview]
Message-ID: <20130605115734.GY31367@sirena.org.uk> (raw)
In-Reply-To: <1370432398-7796-2-git-send-email-illia.smyrnov@ti.com>
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
On Wed, Jun 05, 2013 at 02:39:57PM +0300, Illia Smyrnov wrote:
> +SPI Controller specific data in SPI slave nodes:
> +- The spi slave nodes can provide the following information which is used
> + by the spi controller:
> + - ti,spi-turbo-mode: Set turbo mode for this device.
> +
What is turb mode and why would we not want to just enable it all the
time? Based on this documentation it's not really possible to tell...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-05 11:58 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
2013-06-05 11:57 ` Mark Brown [this message]
2013-06-06 10:08 ` Illia Smyrnov
2013-06-06 10:19 ` Mark Brown
2013-06-05 11:39 ` [PATCH 2/2] spi: omap2-mcspi: Add FIFO buffer support Illia Smyrnov
2013-06-05 12:03 ` Mark Brown
2013-06-06 10:08 ` Illia Smyrnov
2013-06-06 10:30 ` Mark Brown
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=20130605115734.GY31367@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=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
all inboxes | Powered by JetHome®