All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bhupesh Sharma <bhupesh.sharma@linaro.org>
To: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Cc: agross@kernel.org, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org, andersson@kernel.org,
	bhupesh.sharma@linaro.org, bhupesh.linux@gmail.com,
	krzysztof.kozlowski@linaro.org, robh+dt@kernel.org,
	konrad.dybcio@linaro.org, vladimir.zapolskiy@linaro.org,
	rfoss@kernel.org, neil.armstrong@linaro.org, djakov@kernel.org,
	stephan@gerhold.net, Anders Roxell <anders.roxell@linaro.org>,
	Linux Kernel Functional Testing <lkft@linaro.org>
Subject: [PATCH v8 04/11] arm64: dts: qcom: sdm845: Fix the slimbam DMA engine compatible string
Date: Sat, 27 May 2023 00:52:03 +0530	[thread overview]
Message-ID: <20230526192210.3146896-5-bhupesh.sharma@linaro.org> (raw)
In-Reply-To: <20230526192210.3146896-1-bhupesh.sharma@linaro.org>

As per documentation, Qualcomm SDM845 SoC supports SLIMBAM DMA
engine v1.7.4, so use the correct compatible strings.

Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Tested-by: Anders Roxell <anders.roxell@linaro.org>
Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
---
 arch/arm64/boot/dts/qcom/sdm845.dtsi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi b/arch/arm64/boot/dts/qcom/sdm845.dtsi
index cdeb05e95674..0d1d7328cd62 100644
--- a/arch/arm64/boot/dts/qcom/sdm845.dtsi
+++ b/arch/arm64/boot/dts/qcom/sdm845.dtsi
@@ -5221,7 +5221,7 @@ msi-controller@17a40000 {
 		};
 
 		slimbam: dma-controller@17184000 {
-			compatible = "qcom,bam-v1.7.0";
+			compatible = "qcom,bam-v1.7.4", "qcom,bam-v1.7.0";
 			qcom,controlled-remotely;
 			reg = <0 0x17184000 0 0x2a000>;
 			num-channels = <31>;
-- 
2.38.1


  parent reply	other threads:[~2023-05-26 19:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26 19:21 [PATCH v8 00/11] arm64: qcom: Enable Crypto Engine for a few Qualcomm SoCs Bhupesh Sharma
2023-05-26 19:22 ` [PATCH v8 01/11] dt-bindings: dma: Add support for SM6115 and QCM2290 SoCs Bhupesh Sharma
2023-05-29  6:13   ` Bhupesh Sharma
2023-06-06  8:14     ` Bhupesh Sharma
2023-06-08 12:32     ` Vinod Koul
2023-06-30  8:30       ` Bhupesh Sharma
2023-05-26 19:22 ` [PATCH v8 02/11] dt-bindings: dma: Increase iommu maxItems for BAM DMA Bhupesh Sharma
2023-06-18  8:36   ` Krzysztof Kozlowski
2023-06-18  8:39   ` Krzysztof Kozlowski
2023-06-30  8:35     ` Bhupesh Sharma
2023-05-26 19:22 ` [PATCH v8 03/11] arm64: dts: qcom: sdm8550: Fix the BAM DMA engine compatible string Bhupesh Sharma
2023-05-26 19:22 ` Bhupesh Sharma [this message]
2023-05-26 19:22 ` [PATCH v8 05/11] dt-bindings: qcom-qce: Fix compatible combinations for SM8150 and IPQ4019 SoCs Bhupesh Sharma
2023-05-29  6:15   ` Bhupesh Sharma
2023-06-02 10:26     ` Herbert Xu
2023-05-26 19:22 ` [PATCH v8 06/11] dt-bindings: qcom-qce: Add compatibles for SM6115 and QCM2290 Bhupesh Sharma
2023-05-26 19:22 ` [PATCH v8 07/11] arm64: dts: qcom: sm6115: Add Crypto Engine support Bhupesh Sharma
2023-05-26 20:49   ` Konrad Dybcio
2023-05-26 19:22 ` [PATCH v8 08/11] arm64: dts: qcom: sm8150: " Bhupesh Sharma
2023-05-26 19:22 ` [PATCH v8 09/11] arm64: dts: qcom: sm8250: " Bhupesh Sharma
2023-05-26 19:22 ` [PATCH v8 10/11] arm64: dts: qcom: sm8350: " Bhupesh Sharma
2023-06-16 17:36   ` Krzysztof Kozlowski
2023-06-16 23:33     ` Konrad Dybcio
2023-06-17  7:28       ` Krzysztof Kozlowski
2023-06-18  6:49         ` Bhupesh Sharma
2023-06-26 10:51     ` Linux regression tracking #update (Thorsten Leemhuis)
2023-05-26 19:22 ` [PATCH v8 11/11] arm64: dts: qcom: sm8450: add crypto nodes Bhupesh Sharma
2023-05-26 20:50   ` Konrad Dybcio
2023-05-27  1:07 ` (subset) [PATCH v8 00/11] arm64: qcom: Enable Crypto Engine for a few Qualcomm SoCs Bjorn Andersson

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=20230526192210.3146896-5-bhupesh.sharma@linaro.org \
    --to=bhupesh.sharma@linaro.org \
    --cc=agross@kernel.org \
    --cc=anders.roxell@linaro.org \
    --cc=andersson@kernel.org \
    --cc=bhupesh.linux@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=djakov@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft@linaro.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=stephan@gerhold.net \
    --cc=vladimir.zapolskiy@linaro.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 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.