From: Mike Looijmans <mike.looijmans@topic.nl>
To: "R, Vignesh" <vigneshr@ti.com>,
Brian Norris <computersforpeace@gmail.com>
Cc: devicetree@vger.kernel.org, Michal Suchanek <hramrach@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Tony Lindgren <tony@atomide.com>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/5] spi: introduce mmap read support for spi flash devices
Date: Fri, 13 Nov 2015 15:06:55 +0100 [thread overview]
Message-ID: <5645EE7F.5040101@topic.nl> (raw)
In-Reply-To: <5642E546.3040806@ti.com>
On 11-11-15 07:50, R, Vignesh wrote:
> Hi Brain,
>
> On 11/11/2015 4:53 AM, Brian Norris wrote:
>> Hi Vignesh,
...
>> Also, this API doesn't actually have anything to do with memory mapping.
>> It has to do with the de facto standard flash protocol. So I don't think
>> mmap belongs in the name; it should be something about flash. (I know of
>> at least one other controller that could probably use this API, excpet
>> it doesn't use memory mapping to accomplish the accelerated flash read.)
The Zynq has a similar way of accessing QSPI flash through a memory map. The
memory window is only 16MB, so some form of paging would be needed.
It's why I have been following this thread with great interest, since the QSPI
performance on the Zynq is way below what it could potentially be.
> As far as TI QSPI controller is concerned, the accelerated read happens
> via mmap port whereby a predefined memory address space of SoC is
> exposed as QSPI mmap region. This region can be accessed like normal
> RAM(via memcpy()) and the QSPI controller interface takes care of
> fetching data from flash on SPI bus automatically hence, I named it as
> above. But, I have no hard feelings if it needs to be generalized to
> spi_mtd_read() or something else.
I know that on the Zynq, you can even let the DMA controller access the QSPI
flash via this memory mapping. The QSPI controller itself doesn't support any
DMA at all.
If something similar applies to the TI platform (most of the TI procs have
nice DMA controllers) one could go one step further and implement a generic
DMA-through-mmap access to QSPI flash.
Mike.
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
Visit us at : Aerospace Electrical Systems Expo Europe which will be held from 17.11.2015 till 19.11.2015, Findorffstrasse 101 Bremen, Germany, Hall 5, stand number C65
http://www.aesexpo.eu
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2015-11-13 14:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 5:29 [PATCH v3 0/5] Add memory mapped read support for ti-qspi Vignesh R
2015-11-10 5:29 ` [PATCH v3 1/5] spi: introduce mmap read support for spi flash devices Vignesh R
[not found] ` <1447133399-25658-2-git-send-email-vigneshr-l0cyMroinI0@public.gmane.org>
2015-11-10 23:23 ` Brian Norris
2015-11-11 6:50 ` R, Vignesh
[not found] ` <5642E546.3040806-l0cyMroinI0@public.gmane.org>
2015-11-11 7:20 ` Brian Norris
2015-11-13 16:05 ` Cyrille Pitchen
[not found] ` <56460A4D.30303-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-11-17 6:32 ` Vignesh R
2015-11-17 17:48 ` Brian Norris
2015-11-13 14:06 ` Mike Looijmans [this message]
2015-11-11 19:24 ` Brian Norris
2015-11-12 4:32 ` Vignesh R
2015-11-10 5:29 ` [PATCH v3 2/5] spi: spi-ti-qspi: add mmap mode read support Vignesh R
2015-11-10 5:29 ` [PATCH v3 3/5] mtd: devices: m25p80: add support for mmap read request Vignesh R
2015-11-10 5:29 ` [PATCH v3 4/5] ARM: dts: DRA7: add entry for qspi mmap region Vignesh R
2015-11-10 5:29 ` [PATCH v3 5/5] ARM: dts: AM4372: " Vignesh R
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=5645EE7F.5040101@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hramrach@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.com \
--cc=vigneshr@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;
as well as URLs for NNTP newsgroup(s).