From: Yingjoe Chen <yingjoe.chen@mediatek.com>
To: Chuanhong Guo <gch981213@gmail.com>
Cc: <linux-mtd@lists.infradead.org>,
Mark Rutland <mark.rutland@arm.com>, <devicetree@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
"Tudor Ambarus" <tudor.ambarus@microchip.com>,
Richard Weinberger <richard@nod.at>,
<linux-kernel@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
<linux-mediatek@lists.infradead.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] mtd: mtk-quadspi: add support for memory-mapped flash reading
Date: Thu, 7 Nov 2019 21:23:16 +0800 [thread overview]
Message-ID: <1573132996.8833.3.camel@mtksdaap41> (raw)
In-Reply-To: <20191106140748.13100-2-gch981213@gmail.com>
On Wed, 2019-11-06 at 22:07 +0800, Chuanhong Guo wrote:
> PIO reading mode on this controller is ridiculously inefficient
> (one cmd+addr+dummy sequence reads only one byte)
> This patch adds support for reading from memory-mapped flash area
> which increases reading speed from 1MB/s to 5.6MB/s
This may not be true for all MTK SoC. Which one are you testing?
Joe.C
next prev parent reply other threads:[~2019-11-07 13:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 14:07 [PATCH 0/2] mtd: mtk-quadspi: add support for memory-mapped flash reading Chuanhong Guo
2019-11-06 14:07 ` [PATCH 1/2] " Chuanhong Guo
2019-11-07 6:06 ` Vignesh Raghavendra
2019-11-07 9:31 ` Chuanhong Guo
2019-11-07 12:25 ` Vignesh Raghavendra
2019-11-07 13:23 ` Yingjoe Chen [this message]
2019-11-07 15:34 ` Chuanhong Guo
2019-11-08 3:52 ` Chuanhong Guo
2019-11-06 14:07 ` [PATCH 2/2] dt-bindings: mtd: mtk-quadspi: update bindings for mmap flash read Chuanhong Guo
2019-11-07 1:09 ` Rob Herring
2019-11-07 9:25 ` Chuanhong Guo
2019-11-08 3:51 ` Chuanhong Guo
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=1573132996.8833.3.camel@mtksdaap41 \
--to=yingjoe.chen@mediatek.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=gch981213@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=tudor.ambarus@microchip.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).