public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: naga suresh kumar <nagasureshkumarrelli@gmail.com>
Cc: nagasure@xilinx.com, cyrille.pitchen@wedev4u.fr,
	marek.vasut@gmail.com, dwmw2@infradead.org,
	computersforpeace@gmail.com, boris.brezillon@free-electrons.com,
	linux-mtd@lists.infradead.org
Subject: Re: [RFC PATCH 0/5] RFC for Zynq QSPI
Date: Mon, 17 Sep 2018 17:07:31 +0200	[thread overview]
Message-ID: <20180917170731.078e3d4f@bbrezillon> (raw)
In-Reply-To: <20180917170522.0312ae8c@bbrezillon>

On Mon, 17 Sep 2018 17:05:22 +0200
Boris Brezillon <boris.brezillon@bootlin.com> wrote:

> Hi Naga,
> 
> On Mon, 17 Sep 2018 16:08:26 +0530
> naga suresh kumar <nagasureshkumarrelli@gmail.com> wrote:
> 
> > Hi all,
> > 
> > Can i write the Zynq QSPI driver under the new spi/mem framework?  
> 
> Yes, you should.
> 
> > As i said, it needs tweaking the mtd->size and spi read/write addresses.  
> 
> Can you elaborate a bit on why you think this is needed? Did you look
> at [1]? Maybe it will prevent us from exposing the flash size at the
> spi-mem level.
> 
> > Can somebody share your thoughts on this(Adding Zynq QSPI Dual parallel and
> > stacked)?  
> 
> I always have a hard time with this naming. I guess stacked is when you
> have 2 chips sharing the same I/O bus, and parallel is when you have 2
> chips with one taking all of the I/O and the other taking the other

			^half of the I/O bus and the other one

> half. Is that correct?
> 
> If it is, then stacked mode should be easy to support (it's just a
> matter of patching the spi layer to allow passing several CS lines to a
> single device (in case of DT parsing, it means reg = <0 1> implies CS 0
> and 1 are assigned to the same device. For the parallel, I don't have a
> solution yet.
> 
> Anyway, I'd suggest that you start with something simple (a spi-mem
> driver supporting ->exec_op() in Single/Dual/Quad mode), and build on
> top of that for the advanced features you're mentioning here.
> 
> Regards,
> 
> Boris
> 
> [1]http://lists.infradead.org/pipermail/linux-mtd/2018-June/081460.html

  reply	other threads:[~2018-09-17 15:07 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 ` [RFC PATCH 0/5] RFC for Zynq QSPI Marek Vasut
2018-03-23 13:39   ` 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 [this message]
     [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=20180917170731.078e3d4f@bbrezillon \
    --to=boris.brezillon@bootlin.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=marek.vasut@gmail.com \
    --cc=nagasure@xilinx.com \
    --cc=nagasureshkumarrelli@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