From: Vignesh R <vigneshr@ti.com>
To: Tony Lindgren <tony@atomide.com>,
Brian Norris <computersforpeace@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Russell King <linux@arm.linux.org.uk>, <hramrach@gmail.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mtd@lists.infradead.org>, <linux-spi@vger.kernel.org>
Subject: Re: [PATCH v5 0/5] Add memory mapped read support for ti-qspi
Date: Tue, 5 Jan 2016 10:50:42 +0530 [thread overview]
Message-ID: <568B52AA.4070900@ti.com> (raw)
In-Reply-To: <1449807000-6457-1-git-send-email-vigneshr@ti.com>
Hi Brian,
On 12/11/2015 09:39 AM, Vignesh R wrote:
> Changes since v4:
> Use syscon to access system control module register in ti-qspi driver.
>
Gentle ping...
Are you ok with MTD side changes of this patch series?
> 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 (5):
> 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
> ARM: dts: DRA7: add entry for qspi mmap region
> ARM: dts: AM4372: add entry for qspi mmap region
>
> Documentation/devicetree/bindings/spi/ti_qspi.txt | 22 +++-
> arch/arm/boot/dts/am4372.dtsi | 4 +-
> arch/arm/boot/dts/dra7.dtsi | 6 +-
> drivers/mtd/devices/m25p80.c | 20 ++++
> drivers/spi/spi-ti-qspi.c | 139 +++++++++++++++++-----
> drivers/spi/spi.c | 45 +++++++
> include/linux/spi/spi.h | 41 +++++++
> 7 files changed, 243 insertions(+), 34 deletions(-)
>
--
Regards
Vignesh
next prev parent reply other threads:[~2016-01-05 5:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 4:09 [PATCH v5 0/5] Add memory mapped read support for ti-qspi Vignesh R
2015-12-11 4:09 ` [PATCH v5 1/5] spi: introduce accelerated read support for spi flash devices Vignesh R
2015-12-11 4:09 ` [PATCH v5 2/5] spi: spi-ti-qspi: add mmap mode read support Vignesh R
2015-12-11 4:09 ` [PATCH v5 3/5] mtd: devices: m25p80: add support for mmap read request Vignesh R
2016-02-09 19:36 ` Mark Brown
2016-02-11 5:33 ` Vignesh R
2016-02-12 22:37 ` Mark Brown
2016-02-16 8:00 ` Vignesh R
2016-02-16 12:38 ` Mark Brown
2016-02-17 16:11 ` R, Vignesh
2016-02-24 12:21 ` Vignesh R
2015-12-11 4:09 ` [PATCH v5 4/5] ARM: dts: DRA7: add entry for qspi mmap region Vignesh R
2015-12-11 15:09 ` Rob Herring
2015-12-17 18:45 ` Tony Lindgren
2015-12-18 5:50 ` Vignesh R
2015-12-18 16:42 ` Tony Lindgren
2015-12-11 4:10 ` [PATCH v5 5/5] ARM: dts: AM4372: " Vignesh R
2015-12-21 12:03 ` [PATCH v5 0/5] Add memory mapped read support for ti-qspi Vignesh R
2016-01-05 5:20 ` Vignesh R [this message]
2016-01-05 18:19 ` Mark Brown
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=568B52AA.4070900@ti.com \
--to=vigneshr@ti.com \
--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=robh+dt@kernel.org \
--cc=tony@atomide.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).