From: Xing Zheng <zhengxing@rock-chips.com>
To: Shawn Lin <shawn.lin@rock-chips.com>, Vinod Koul <vinod.koul@intel.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Huibin Hong <huibin.hong@rock-chips.com>,
devicetree@vger.kernel.org, dianders@chromium.org,
briannorris@chromium.org, Caesar Wang <wxt@rock-chips.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 2/3] dmaengine: pl330: enable burst mode by parsing dt
Date: Sun, 7 Aug 2016 17:20:33 +0800 [thread overview]
Message-ID: <57A6FD61.6080003@rock-chips.com> (raw)
In-Reply-To: <1470365602-32586-3-git-send-email-shawn.lin@rock-chips.com>
Hi Shawn,
On 2016年08月05日 10:53, Shawn Lin wrote:
> Currently pl330 use single mode defaultly. But burst
> mode can improve efficiency of memory accessing. We
> couldn't enable it by defalut in case of breaking any
> Socs which don't support it.
>
> With burst mode supported, we could see the improvement
> significantly when tesing SPI transfer etc.
>
> default single mode
> [ 88.292550] spi write 65536*1 cost 32402us speed:2022KB/S
>
> After applied with burst mode(len 16)
> [ 17.625296] spi write 65536*1 cost 17830us speed:3675KB/S
>
> Cc: Huibin Hong <huibin.hong@rock-chips.com>
> Cc: Xing Zheng <zhengxing@rock-chips.com>
> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
> ---
>
Tested-by: Xing Zheng <zhengxing@rock-chips.com>
Thanks
--
- Xing Zheng
next prev parent reply other threads:[~2016-08-07 9:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 2:53 [PATCH 0/3] Support burst request by peripherals Shawn Lin
[not found] ` <1470365602-32586-1-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-08-05 2:53 ` [PATCH 1/3] dt/bindings: arm-pl330: add description of arm,pl330-periph-burst Shawn Lin
2016-08-05 3:34 ` Vinod Koul
2016-08-05 7:25 ` Shawn Lin
[not found] ` <ea3572fa-4bff-87db-d5ad-f406809f8296-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-08-09 8:39 ` Lars-Peter Clausen
2016-08-09 9:12 ` Shawn Lin
[not found] ` <1d42542f-c43c-5c4b-01b7-ba0ca085004a-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-08-17 8:11 ` Shawn Lin
2016-08-19 2:45 ` Vinod Koul
2016-08-21 1:00 ` Shawn Lin
[not found] ` <d4574737-f7b7-2726-373c-31cc81274a32-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-08-22 6:04 ` Vinod Koul
2016-08-05 2:53 ` [PATCH 2/3] dmaengine: pl330: enable burst mode by parsing dt Shawn Lin
2016-08-07 9:20 ` Xing Zheng [this message]
2016-08-05 2:53 ` [PATCH 3/3] dmaengine: pl330: support transfer unaligned with (burst len * burst size) Shawn Lin
[not found] ` <1470365602-32586-4-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-08-07 9:21 ` Xing Zheng
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=57A6FD61.6080003@rock-chips.com \
--to=zhengxing@rock-chips.com \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmaengine@vger.kernel.org \
--cc=huibin.hong@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=vinod.koul@intel.com \
--cc=wxt@rock-chips.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).