From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Boris Brezillon <boris.brezillon@bootlin.com>,
Radu Pirea <radu.pirea@microchip.com>
Cc: <cyrille.pitchen@wedev4u.fr>, <marek.vasut@gmail.com>,
<dwmw2@infradead.org>, <computersforpeace@gmail.com>,
<richard@nod.at>, <linux-mtd@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Tudor Ambarus - M18064 <Tudor.Ambarus@microchip.com>
Subject: Re: [PATCH] spi-nor: Add support for Atmel Dataflash memories
Date: Mon, 7 May 2018 10:23:56 +0200 [thread overview]
Message-ID: <d9b3fffd-dded-b210-e058-13a326b4fb8f@microchip.com> (raw)
In-Reply-To: <20180504203844.0c09bf6d@bbrezillon>
On 04/05/2018 at 20:38, Boris Brezillon wrote:
> Hi Radu,
>
> Sorry for the late reply.
>
> On Wed, 28 Feb 2018 13:55:01 +0200
> Radu Pirea <radu.pirea@microchip.com> wrote:
>
>> This patch add support in spi-nor for allmost all dataflash memories
>> supported by old mtd_dataflash driver.
>
> Those devices clearly use a different instruction set, so I don't think
> they fit in this framework. Can you tell us why you want to move
> dataflash support to the SPI NOR framework. I think I know why, but I'd
> like to get your version. My guess is that some people want to connect
> dataflash chips to the Atmel QSPI controller, and it's not supported
> right now because the Atmel QSPI controller implements the SPI-NOR
> interface and not the generic SPI one, thus preventing anything that
> is not a SPI NOR from being connected to this controller.
>
> If I'm right, then the solution is to convert the QSPI driver to the
> spi-mem interface [1] and move it to drivers/spi/.
No, I we didn't think about this. Dataflash is not so popular those days
and we don't want to revive it anyway. Our QSPI driver has already a lot
of things to handle in QSPI-related topics to not mix it with oldies ;-)
The rationale behind this work is to get rid of the very old dataflash
standalone driver and benefit from the whole spi-nor infrastructure like
cache coherency management and DMA handling (which were broken in the
old dataflash driver in recent kernels).
Best regards,
Nicolas
> [1]http://patchwork.ozlabs.org/project/linux-mtd/list/?series=41174
>
--
Nicolas Ferre
next prev parent reply other threads:[~2018-05-07 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 11:55 [PATCH] spi-nor: Add support for Atmel Dataflash memories Radu Pirea
2018-05-04 18:38 ` Boris Brezillon
2018-05-07 8:23 ` Nicolas Ferre [this message]
2018-05-07 8:34 ` Boris Brezillon
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=d9b3fffd-dded-b210-e058-13a326b4fb8f@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=radu.pirea@microchip.com \
--cc=richard@nod.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.