From: Mark Brown <broonie@kernel.org>
To: Stefan Agner <stefan@agner.ch>
Cc: "BhuvanChandra.DV" <bhuvanchandra.dv@toradex.com>,
Li.Xiubo@freescale.com, mark.rutland@arm.com,
shawn.guo@linaro.org, robh+dt@kernel.org, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, B44548@freescale.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH 7/7] spi: spi-fsl-dspi: Add support for TCFQ transfer mode
Date: Fri, 30 Jan 2015 13:30:33 +0100 [thread overview]
Message-ID: <20150130123033.GC26617@finisterre.sirena.org.uk> (raw)
In-Reply-To: <1a28f3439386e1132ae0f3ab80666305@agner.ch>
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
On Thu, Jan 29, 2015 at 07:10:31PM +0100, Stefan Agner wrote:
> It would be interesting to know what the authors original motivation
> implementing this feature was. Reading the email of the original
> patchset indicates that there are platforms where only TCF is supported:
> <quote>
> For adopting of different platform, either of them is a way of DSPI
> transfer data.
> </quote>
> However, I don't know which platform that would be. Also, it seems that
> Chao Fu's email is not valid anymore.
It's not clear to me if the above means that this is due to hardware
differences or due to tuning for the platform.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-02-07 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 11:03 [PATCH 6/7] spi: spi-fsl-dspi: split the resuable code Bhuvanchandra DV
2015-01-27 11:03 ` [PATCH 7/7] spi: spi-fsl-dspi: Add support for TCFQ transfer mode Bhuvanchandra DV
2015-01-28 19:03 ` Mark Brown
[not found] ` <1422533049999.91114@toradex.com>
2015-01-29 12:13 ` Mark Brown
[not found] ` <1422536382672.21760@toradex.com>
2015-01-29 18:10 ` Stefan Agner
2015-01-30 12:30 ` Mark Brown [this message]
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=20150130123033.GC26617@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=B44548@freescale.com \
--cc=Li.Xiubo@freescale.com \
--cc=bhuvanchandra.dv@toradex.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=stefan@agner.ch \
/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).