From: Marek Vasut <marek.vasut@gmail.com>
To: Naga Sureshkumar Relli <naga.sureshkumar.relli@xilinx.com>,
cyrille.pitchen@wedev4u.fr, dwmw2@infradead.org,
computersforpeace@gmail.com, boris.brezillon@free-electrons.com
Cc: linux-mtd@lists.infradead.org,
Naga Sureshkumar Relli <nagasure@xilinx.com>
Subject: Re: [RFC PATCH 0/5] RFC for Zynq QSPI
Date: Fri, 23 Mar 2018 13:52:18 +0100 [thread overview]
Message-ID: <c06c5256-119d-ef90-0bf8-cdbc1720a7b9@gmail.com> (raw)
In-Reply-To: <1521807722-21626-1-git-send-email-nagasure@xilinx.com>
On 03/23/2018 01:21 PM, Naga Sureshkumar Relli wrote:
> Xilinx Zynq uses a QSPI controller that is based on the Cadence SPI IP.
Don't we have a CQSPI driver already ? Why is this adding a new one ?
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-03-23 12:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 12:21 [RFC PATCH 0/5] RFC for Zynq QSPI Naga Sureshkumar Relli
2018-03-23 12:21 ` [RFC PATCH 1/5] spi: Add support for Zynq qspi controller Naga Sureshkumar Relli
2018-03-23 12:21 ` [RFC PATCH 2/5] mtd: spi-nor: Add support for Zynq QSPI controller Naga Sureshkumar Relli
2018-03-23 12:22 ` [RFC PATCH 3/5] mtd: spi-nor: Add Dual Parallel and Stacked support for Zynq QSPI Naga Sureshkumar Relli
2018-03-23 12:22 ` [RFC PATCH 4/5] spi: Add PM Support for Zynq QSPI controller Naga Sureshkumar Relli
2018-03-23 12:22 ` [RFC PATCH 5/5] devicetree: Add devicetree bindings documentation for Naga Sureshkumar Relli
2018-03-23 14:47 ` Miquel Raynal
2018-03-23 12:52 ` Marek Vasut [this message]
2018-03-23 13:39 ` [RFC PATCH 0/5] RFC for Zynq QSPI Naga Sureshkumar Relli
2018-04-16 7:25 ` Naga Sureshkumar Relli
[not found] ` <CALgLF9K=rZxVx_QXvV_LH3OhidTcguZ=K=p=Lf9AfFbk4H+8Zw@mail.gmail.com>
2018-09-17 15:05 ` Boris Brezillon
2018-09-17 15:07 ` Boris Brezillon
[not found] ` <CALgLF9JVweEcEm6L33HaHp4HtXhmsZL7J5FDe8+O11i0Q1nukg@mail.gmail.com>
2018-09-18 7:17 ` Boris Brezillon
2018-09-18 8:58 ` Naga Sureshkumar Relli
2019-06-26 9:53 ` naga suresh kumar
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=c06c5256-119d-ef90-0bf8-cdbc1720a7b9@gmail.com \
--to=marek.vasut@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=naga.sureshkumar.relli@xilinx.com \
--cc=nagasure@xilinx.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).