From: Michal Simek <monstr@monstr.eu>
To: sourav <sourav.poddar@ti.com>
Cc: Harini Katakam <harinik@xilinx.com>,
broonie@kernel.org, grant.likely@linaro.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] SPI: Add driver for Cadence SPI controller
Date: Fri, 04 Apr 2014 12:02:13 +0200 [thread overview]
Message-ID: <533E8325.5000503@monstr.eu> (raw)
In-Reply-To: <533E7A3C.3060302@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
Hi Sourav
On 04/04/2014 11:24 AM, sourav wrote:
> HI,
> On Friday 04 April 2014 02:34 PM, sourav wrote:
>> Hi Harini,
>> On Thursday 03 April 2014 04:40 PM, Harini Katakam wrote:
>>> Add driver for Cadence SPI controller. This is used in Xilinx Zynq.
>>>
>>> Signed-off-by: Harini Katakam<harinik@xilinx.com>
>>> ---
>> I had looked at cadence qspi controller. What I can see is that your
>> patch implements "normal spi ode of operation" ? and the patch looks fine.
>> But, to avail the maximum throughput, I see cadence qspi supports
>> direct/indirect mode of operations, as well as read data capture logic.
>>
>> So, do you intent to add any of the above in your driver?
>>
> Looks like, I got a bit confused. This is not cadence QSPI controller but only SPI controller.
> Sorry for the noise.
Look at this one
http://www.spinics.net/lists/kernel/msg1716894.html
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-04-04 10:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 11:10 Harini Katakam
2014-04-03 11:10 ` [PATCH v2 2/2] devicetree: Add devicetree bindings documentation for Cadence SPI Harini Katakam
2014-04-03 21:34 ` Mark Brown
2014-04-04 3:00 ` Harini Katakam
2014-04-04 8:09 ` Geert Uytterhoeven
2014-04-04 11:16 ` Michal Simek
2014-04-04 10:09 ` Mark Brown
2014-04-04 12:14 ` Harini Katakam
2014-04-04 12:24 ` Peter Crosthwaite
2014-04-04 12:39 ` Harini Katakam
2014-04-04 12:46 ` Mark Brown
2014-04-04 14:08 ` Harini Katakam
2014-04-04 14:30 ` Harini Katakam
2014-04-04 23:14 ` Peter Crosthwaite
2014-04-05 6:05 ` Harini Katakam
2014-04-05 23:43 ` Peter Crosthwaite
2014-04-07 7:46 ` Harini Katakam
2014-04-04 14:42 ` Mark Brown
2014-04-04 14:49 ` Harini Katakam
2014-04-03 21:43 ` [PATCH v2 1/2] SPI: Add driver for Cadence SPI controller Mark Brown
2014-04-04 3:49 ` Harini Katakam
2014-04-04 9:04 ` sourav
2014-04-04 9:24 ` sourav
2014-04-04 10:02 ` Michal Simek [this message]
2014-04-04 22:58 ` Peter Crosthwaite
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=533E8325.5000503@monstr.eu \
--to=monstr@monstr.eu \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=harinik@xilinx.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sourav.poddar@ti.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
Powered by JetHome