From: Vignesh R <vigneshr@ti.com>
To: Brian Norris <computersforpeace@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: Russell King <linux@arm.linux.org.uk>, <hramrach@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-mtd@lists.infradead.org>, <linux-spi@vger.kernel.org>,
Vignesh R <vigneshr@ti.com>
Subject: [RESEND][PATCH v5 0/3] Add memory mapped read support for ti-qspi
Date: Mon, 1 Feb 2016 12:14:22 +0530 [thread overview]
Message-ID: <1454309065-11493-1-git-send-email-vigneshr@ti.com> (raw)
Resend v5:
Rebased on top of v4.5-rc1
Changes since v4:
Use syscon to access system control module register in ti-qspi driver.
Changes since v3:
Rework to introduce spi_flash_read_message struct.
Support different opcode/addr/data formats as per Brian's suggestion
here: https://lkml.org/lkml/2015/11/11/454
Changes since v2:
Remove mmap_lock_mutex.
Optimize enable/disable of mmap mode.
Changes since v1:
Introduce API in SPI core that MTD flash driver can call for mmap read
instead of directly calling spi-master driver callback. This API makes
sure that SPI core msg queue is locked during mmap transfers.
v1: https://lkml.org/lkml/2015/9/4/103
Cover letter:
This patch series adds support for memory mapped read port of ti-qspi.
ti-qspi has a special memory mapped port through which SPI flash
memories can be accessed directly via SoC specific memory region.
First patch adds a method to pass flash specific information like read
opcode, dummy bytes etc and to request mmap read. Second patch
implements mmap read method in ti-qspi driver. Patch 3 adapts m25p80 to
use mmap read method before trying normal SPI transfer. Patch 4 and 5
add memory map region DT entries for DRA7xx and AM43xx SoCs.
This patch series is based on the discussions here:
http://www.spinics.net/lists/linux-spi/msg04796.html
Tested on DRA74 EVM and AM437x-SK.
Read performance increases from ~100kB/s to ~2.5MB/s.
Vignesh R (3):
spi: introduce accelerated read support for spi flash devices
spi: spi-ti-qspi: add mmap mode read support
mtd: devices: m25p80: add support for mmap read request
drivers/mtd/devices/m25p80.c | 20 +++++++
drivers/spi/spi-ti-qspi.c | 139 ++++++++++++++++++++++++++++++++++---------
drivers/spi/spi.c | 45 ++++++++++++++
include/linux/spi/spi.h | 41 +++++++++++++
4 files changed, 216 insertions(+), 29 deletions(-)
--
2.7.0
next reply other threads:[~2016-02-01 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 6:44 Vignesh R [this message]
2016-02-01 6:44 ` [RESEND][PATCH v5 1/3] spi: introduce accelerated read support for spi flash devices Vignesh R
2016-02-01 6:44 ` [RESEND][PATCH v5 2/3] spi: spi-ti-qspi: add mmap mode read support Vignesh R
[not found] ` <1454309065-11493-1-git-send-email-vigneshr-l0cyMroinI0@public.gmane.org>
2016-02-01 6:44 ` [RESEND][PATCH v5 3/3] mtd: devices: m25p80: add support for mmap read request 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=1454309065-11493-1-git-send-email-vigneshr@ti.com \
--to=vigneshr@ti.com \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=hramrach@gmail.com \
--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 \
/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).