From: Sugar Zhang <sugar.zhang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
To: heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org,
vkoul-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Sugar Zhang <sugar.zhang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Subject: [PATCH v2 11/13] arm64: dts: rk3328: Add 'arm,pl330-periph-burst' for dmac
Date: Tue, 9 Jun 2020 09:22:21 +0800 [thread overview]
Message-ID: <1591665743-38416-2-git-send-email-sugar.zhang@rock-chips.com> (raw)
In-Reply-To: <1591665267-37713-1-git-send-email-sugar.zhang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
This patch Add the quirk to specify to use burst transfer
for better compatible and higher performance.
Signed-off-by: Sugar Zhang <sugar.zhang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
---
Changes in v2:
- fix FATAL ERROR: Unable to parse input tree
arch/arm64/boot/dts/rockchip/rk3328.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
index a4d591d..8a9ce1e 100644
--- a/arch/arm64/boot/dts/rockchip/rk3328.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
@@ -156,6 +156,7 @@
clocks = <&cru ACLK_DMAC>;
clock-names = "apb_pclk";
#dma-cells = <1>;
+ arm,pl330-periph-burst;
};
};
--
2.7.4
next prev parent reply other threads:[~2020-06-09 1:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 1:14 [PATCH v2 0/13] Patches to improve transfer efficiency for Rockchip SoCs Sugar Zhang
2020-06-09 1:14 ` [PATCH v2 01/13] dmaengine: pl330: Remove the burst limit for quirk 'NO-FLUSHP' Sugar Zhang
2020-06-24 7:54 ` Vinod Koul
2020-06-29 1:38 ` sugar zhang
2020-06-09 1:14 ` [PATCH v2 02/13] dmaengine: pl330: Add quirk 'arm,pl330-periph-burst' Sugar Zhang
2020-06-24 8:19 ` Vinod Koul
[not found] ` <1591665267-37713-1-git-send-email-sugar.zhang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2020-06-09 1:14 ` [PATCH v2 03/13] dt-bindings: dma: pl330: Document the " Sugar Zhang
[not found] ` <1591665267-37713-4-git-send-email-sugar.zhang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2020-06-17 20:58 ` Rob Herring
2020-06-09 1:14 ` [PATCH v2 04/13] ARM: dts: rk3036: Add 'arm,pl330-periph-burst' for dmac Sugar Zhang
2020-06-09 1:20 ` [PATCH v2 05/13] ARM: dts: rk322x: " Sugar Zhang
2020-06-09 1:20 ` [PATCH v2 06/13] ARM: dts: rk3288: " Sugar Zhang
2020-06-09 1:20 ` [PATCH v2 07/13] ARM: dts: rk3xxx: " Sugar Zhang
2020-06-09 1:20 ` [PATCH v2 08/13] ARM: dts: rv1108: " Sugar Zhang
2020-06-09 1:20 ` [PATCH v2 09/13] arm64: dts: px30: " Sugar Zhang
2020-06-09 1:22 ` [PATCH v2 10/13] arm64: dts: rk3308: " Sugar Zhang
2020-06-09 1:22 ` Sugar Zhang [this message]
2020-06-09 1:22 ` [PATCH v2 12/13] arm64: dts: rk3368: " Sugar Zhang
2020-06-09 1:22 ` [PATCH v2 13/13] arm64: dts: rk3399: " Sugar Zhang
2020-06-12 1:06 ` [PATCH v2 0/13] Patches to improve transfer efficiency for Rockchip SoCs Peter Geis
[not found] ` <CAMdYzYr+NF7L3KKzcGano=j9V844Gy8gH03hD++CoPe8Ao1QxQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-06-12 1:15 ` Peter Geis
2020-06-12 8:58 ` sugar zhang
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=1591665743-38416-2-git-send-email-sugar.zhang@rock-chips.com \
--to=sugar.zhang-tnx95d0mmh7dzftrwevzcw@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=vkoul-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
/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