From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: "David Woodhouse" <dwmw2@infradead.org>,
"Brian Norris" <computersforpeace@gmail.com>,
"Boris Brezillon" <boris.brezillon@free-electrons.com>,
"Marek Vasut" <marek.vasut@gmail.com>,
"Richard Weinberger" <richard@nod.at>,
"Cyrille Pitchen" <cyrille.pitchen@wedev4u.fr>,
linux-mtd@lists.infradead.org, linux-spi@vger.kernel.org,
"Peter Pan" <peterpansjtu@gmail.com>,
"Frieder Schrempf" <frieder.schrempf@exceet.de>,
"Vignesh R" <vigneshr@ti.com>,
"Yogesh Gaur" <yogeshnarayan.gaur@nxp.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Kamal Dasu" <kdasu.kdev@gmail.com>,
"Sourav Poddar" <sourav.poddar@ti.com>
Subject: Re: [RFC PATCH 0/6] spi: Extend the framework to generically support memory devices
Date: Mon, 19 Feb 2018 17:51:40 +0100 [thread overview]
Message-ID: <20180219175140.7ec6f0e1@bbrezillon> (raw)
In-Reply-To: <20180219162510.GG32761@sirena.org.uk>
On Mon, 19 Feb 2018 16:25:10 +0000
Mark Brown <broonie@kernel.org> wrote:
> On Tue, Feb 06, 2018 at 12:21:14AM +0100, Boris Brezillon wrote:
>
> > SPI NAND layer): you can register a SPI NOR device directly from the
> > dedicated SPI memory controller, or it can be registered through the
> > SPI layer if the SPI controller is a generic SPI controller. While
> > the generic SPI controller path works fine, the dedicated SPI NOR
> > controller path brings its own set of issues:
>
> > * the SPI bus is not represented in sysfs
>
> I'm not sure if this is a big deal or not - at some point it's just an
> implementation detail of the hardware rather than something we're aware
> of or interested in.
>
> > * because there's no bus, there's no uevent, which means you'll have to
> > select both the SPI NAND and SPI NOR logic as soon as one driver
> > supports both interfaces if you don't want to run into loading
> > dependency issues
>
> This is sounding like we want a class (well, virtual bus in the new
> world) for these devices with a SPI based driver sitting on top of that
> for use with genuine SPI controllers. If the intention is as the
> comments in the code suggested that controllers implementing the memory
> mapping stuff don't use SPI at all then we could have the legacy SPI bus
> support be just another driver for this class. However when I look at
> what the drivers are actually doing it seems like that's not the case
> and the new API is intended to sit alongside normal SPI support, perhaps
> only implementing certain operations and using regular SPI for others.
> In that case it makes a lot more sense to have this be bolted on the
> side of SPI.
This is a case: most controllers support both regular SPI transfers and
memory-like operations (with some optimizations for memory oriented
operations).
--
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-19 16:52 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 23:21 [RFC PATCH 0/6] spi: Extend the framework to generically support memory devices Boris Brezillon
2018-02-05 23:21 ` Boris Brezillon
2018-02-05 23:21 ` [RFC PATCH 1/6] spi: Extend the core to ease integration of SPI memory controllers Boris Brezillon
2018-02-05 23:21 ` Boris Brezillon
2018-02-06 9:43 ` Maxime Chevallier
2018-02-06 9:43 ` Maxime Chevallier
2018-02-06 10:25 ` Boris Brezillon
2018-02-06 10:25 ` Boris Brezillon
2018-02-06 12:06 ` Mark Brown
2018-02-06 12:06 ` Mark Brown
2018-02-09 12:52 ` Miquel Raynal
2018-02-09 12:52 ` Miquel Raynal
2018-02-11 16:00 ` Boris Brezillon
2018-02-11 16:00 ` Boris Brezillon
2018-02-12 11:50 ` Vignesh R
2018-02-12 11:50 ` Vignesh R
2018-02-12 12:28 ` Boris Brezillon
2018-02-12 12:28 ` Boris Brezillon
2018-02-19 13:53 ` Mark Brown
2018-02-19 14:20 ` Boris Brezillon
2018-02-19 14:00 ` Mark Brown
2018-02-19 14:32 ` Boris Brezillon
2018-02-28 7:51 ` Peter Pan
2018-02-28 7:51 ` Peter Pan
2018-02-28 12:25 ` Boris Brezillon
2018-02-28 12:25 ` Boris Brezillon
2018-03-04 21:15 ` Cyrille Pitchen
2018-03-04 21:15 ` Cyrille Pitchen
2018-03-05 9:00 ` Boris Brezillon
2018-03-05 9:00 ` Boris Brezillon
2018-03-05 13:01 ` Cyrille Pitchen
2018-03-05 13:01 ` Cyrille Pitchen
2018-03-05 13:47 ` Boris Brezillon
2018-03-05 13:47 ` Boris Brezillon
2018-03-08 14:07 ` Boris Brezillon
2018-03-08 14:07 ` Boris Brezillon
2018-02-05 23:21 ` [RFC PATCH 2/6] spi: bcm-qspi: Implement the spi_mem interface Boris Brezillon
2018-02-05 23:21 ` Boris Brezillon
2018-02-05 23:21 ` [RFC PATCH 3/6] spi: bcm53xx: " Boris Brezillon
2018-02-05 23:21 ` Boris Brezillon
2018-02-05 23:21 ` [RFC PATCH 4/6] spi: ti-qspi: " Boris Brezillon
2018-02-05 23:21 ` Boris Brezillon
2018-02-11 15:17 ` Miquel Raynal
2018-02-11 15:17 ` Miquel Raynal
2018-02-11 17:18 ` Boris Brezillon
2018-02-11 17:18 ` Boris Brezillon
2018-02-12 7:54 ` Miquel Raynal
2018-02-12 7:54 ` Miquel Raynal
2018-02-12 11:43 ` Vignesh R
2018-02-12 11:43 ` Vignesh R
2018-02-12 12:31 ` Boris Brezillon
2018-02-12 12:31 ` Boris Brezillon
2018-02-12 16:00 ` Vignesh R
2018-02-12 16:00 ` Vignesh R
2018-02-12 16:08 ` Boris Brezillon
2018-02-12 16:08 ` Boris Brezillon
2018-02-14 16:25 ` Vignesh R
2018-02-14 16:25 ` Vignesh R
2018-02-14 19:09 ` Boris Brezillon
2018-02-14 19:09 ` Boris Brezillon
2018-02-14 20:44 ` Schrempf Frieder
2018-02-14 20:44 ` Schrempf Frieder
2018-02-14 21:00 ` Boris Brezillon
2018-02-14 21:00 ` Boris Brezillon
2018-02-15 16:38 ` Schrempf Frieder
2018-02-15 16:38 ` Schrempf Frieder
2018-02-17 11:01 ` Vignesh R
2018-02-17 11:01 ` Vignesh R
2018-02-17 21:52 ` Boris Brezillon
2018-02-17 21:52 ` Boris Brezillon
2018-02-16 10:25 ` Boris Brezillon
2018-02-16 10:25 ` Boris Brezillon
2018-02-05 23:21 ` [RFC PATCH 5/6] mtd: spi-nor: Use the spi_mem_xx() API Boris Brezillon
2018-02-05 23:21 ` Boris Brezillon
2018-02-12 11:44 ` Vignesh R
2018-02-12 11:44 ` Vignesh R
2018-02-12 12:32 ` Boris Brezillon
2018-02-12 12:32 ` Boris Brezillon
2018-06-11 6:25 ` Yogesh Narayan Gaur
2018-06-11 6:25 ` Yogesh Narayan Gaur
2018-06-11 7:35 ` Boris Brezillon
2018-06-11 7:35 ` Boris Brezillon
2018-02-05 23:21 ` [RFC PATCH 6/6] spi: Get rid of the spi_flash_read() API Boris Brezillon
2018-02-05 23:21 ` Boris Brezillon
2018-02-16 10:21 ` Vignesh R
2018-02-16 10:21 ` Vignesh R
2018-02-16 10:24 ` Boris Brezillon
2018-02-16 10:24 ` Boris Brezillon
2018-02-19 16:25 ` [RFC PATCH 0/6] spi: Extend the framework to generically support memory devices Mark Brown
2018-02-19 16:51 ` Boris Brezillon [this message]
2018-03-04 21:40 ` Cyrille Pitchen
2018-03-04 21:40 ` Cyrille Pitchen
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=20180219175140.7ec6f0e1@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=boris.brezillon@free-electrons.com \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=frieder.schrempf@exceet.de \
--cc=kdasu.kdev@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=peterpansjtu@gmail.com \
--cc=rafal@milecki.pl \
--cc=richard@nod.at \
--cc=sourav.poddar@ti.com \
--cc=vigneshr@ti.com \
--cc=yogeshnarayan.gaur@nxp.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 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.