All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jayesh Choudhary <j-choudhary@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>
Cc: <kristo@kernel.org>, <robh+dt@kernel.org>, <afd@ti.com>,
	<j-keerthy@ti.com>, <krzysztof.kozlowski+dt@linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<j-choudhary@ti.com>
Subject: [PATCH 3/3] arm64: dts: ti: k3-j7200-mcu-wakeup: drop dma-coherent in crypto node
Date: Mon, 31 Oct 2022 20:55:20 +0530	[thread overview]
Message-ID: <20221031152520.355653-4-j-choudhary@ti.com> (raw)
In-Reply-To: <20221031152520.355653-1-j-choudhary@ti.com>

crypto driver itself is not dma-coherent. So drop it.

Fixes: d683a73980a6 ("arm64: dts: ti: k3-j7200-mcu-wakeup: Add SA2UL node")
Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
---
 arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 1 -
 1 file changed, 1 deletion(-)

diff --git a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
index 2006933f9b49..e85106f55bee 100644
--- a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
@@ -391,7 +391,6 @@ mcu_crypto: crypto@40900000 {
 		dmas = <&mcu_udmap 0xf501>, <&mcu_udmap 0x7502>,
 		       <&mcu_udmap 0x7503>;
 		dma-names = "tx", "rx1", "rx2";
-		dma-coherent;
 
 		rng: rng@40910000 {
 			compatible = "inside-secure,safexcel-eip76";
-- 
2.25.1


WARNING: multiple messages have this Message-ID (diff)
From: Jayesh Choudhary <j-choudhary@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>
Cc: <kristo@kernel.org>, <robh+dt@kernel.org>, <afd@ti.com>,
	<j-keerthy@ti.com>, <krzysztof.kozlowski+dt@linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<j-choudhary@ti.com>
Subject: [PATCH 3/3] arm64: dts: ti: k3-j7200-mcu-wakeup: drop dma-coherent in crypto node
Date: Mon, 31 Oct 2022 20:55:20 +0530	[thread overview]
Message-ID: <20221031152520.355653-4-j-choudhary@ti.com> (raw)
In-Reply-To: <20221031152520.355653-1-j-choudhary@ti.com>

crypto driver itself is not dma-coherent. So drop it.

Fixes: d683a73980a6 ("arm64: dts: ti: k3-j7200-mcu-wakeup: Add SA2UL node")
Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
---
 arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 1 -
 1 file changed, 1 deletion(-)

diff --git a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
index 2006933f9b49..e85106f55bee 100644
--- a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
@@ -391,7 +391,6 @@ mcu_crypto: crypto@40900000 {
 		dmas = <&mcu_udmap 0xf501>, <&mcu_udmap 0x7502>,
 		       <&mcu_udmap 0x7503>;
 		dma-names = "tx", "rx1", "rx2";
-		dma-coherent;
 
 		rng: rng@40910000 {
 			compatible = "inside-secure,safexcel-eip76";
-- 
2.25.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-10-31 15:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 15:25 [PATCH 0/3] Drop dma-coherent property from SA2UL Jayesh Choudhary
2022-10-31 15:25 ` Jayesh Choudhary
2022-10-31 15:25 ` [PATCH 1/3] arm64: dts: ti: k3-am65-main: drop dma-coherent in crypto node Jayesh Choudhary
2022-10-31 15:25   ` Jayesh Choudhary
2022-10-31 15:25 ` [PATCH 2/3] arm64: dts: ti: k3-j721e-main: " Jayesh Choudhary
2022-10-31 15:25   ` Jayesh Choudhary
2022-10-31 15:25 ` Jayesh Choudhary [this message]
2022-10-31 15:25   ` [PATCH 3/3] arm64: dts: ti: k3-j7200-mcu-wakeup: " Jayesh Choudhary
2022-11-15 20:22 ` [PATCH 0/3] Drop dma-coherent property from SA2UL Nishanth Menon
2022-11-15 20:22   ` Nishanth Menon

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=20221031152520.355653-4-j-choudhary@ti.com \
    --to=j-choudhary@ti.com \
    --cc=afd@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=j-keerthy@ti.com \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.