From: Madalin Bucur <madalin.bucur@oss.nxp.com>
To: shawnguo@kernel.org
Cc: devicetree@vger.kernel.org, leoyang.li@nxp.com,
robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
netdev@vger.kernel.org, camelia.groza@oss.nxp.com,
Madalin Bucur <madalin.bucur@oss.nxp.com>
Subject: [PATCH] arm64: dts: fsl: DPAA FMan DMA operations are coherent
Date: Mon, 5 Oct 2020 15:46:39 +0300 [thread overview]
Message-ID: <1601901999-28280-1-git-send-email-madalin.bucur@oss.nxp.com> (raw)
Although the DPAA 1 FMan operations are coherent, the device tree
node for the FMan does not indicate that, resulting in a needless
loss of performance. Adding the missing dma-coherent property.
Fixes: 1ffbecdd8321 ("arm64: dts: add DPAA FMan nodes")
Signed-off-by: Madalin Bucur <madalin.bucur@oss.nxp.com>
Tested-by: Camelia Groza <camelia.groza@oss.nxp.com>
---
arch/arm64/boot/dts/freescale/qoriq-fman3-0.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/freescale/qoriq-fman3-0.dtsi b/arch/arm64/boot/dts/freescale/qoriq-fman3-0.dtsi
index 8bc6caa9167d..4338db14c5da 100644
--- a/arch/arm64/boot/dts/freescale/qoriq-fman3-0.dtsi
+++ b/arch/arm64/boot/dts/freescale/qoriq-fman3-0.dtsi
@@ -19,6 +19,7 @@ fman0: fman@1a00000 {
clock-names = "fmanclk";
fsl,qman-channel-range = <0x800 0x10>;
ptimer-handle = <&ptp_timer0>;
+ dma-coherent;
muram@0 {
compatible = "fsl,fman-muram";
--
2.1.0
next reply other threads:[~2020-10-05 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 12:46 Madalin Bucur [this message]
2020-10-05 15:07 ` [PATCH] arm64: dts: fsl: DPAA FMan DMA operations are coherent Li Yang
2020-10-30 7:39 ` Shawn Guo
2020-11-11 15:33 ` Madalin Bucur
2020-11-16 7:06 ` Shawn 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=1601901999-28280-1-git-send-email-madalin.bucur@oss.nxp.com \
--to=madalin.bucur@oss.nxp.com \
--cc=camelia.groza@oss.nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.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;
as well as URLs for NNTP newsgroup(s).