From: Bhupesh Sharma <bhupesh.sharma@linaro.org>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Thara Gopinath <thara.gopinath@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Andy Gross <agross@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v9 11/14] arm64: dts: qcom: sm8250: add description of Qualcomm Crypto Engine IP
Date: Thu, 9 Feb 2023 17:51:19 +0530 [thread overview]
Message-ID: <7b38331c-3b29-03c1-fbed-f5799d11ca1f@linaro.org> (raw)
In-Reply-To: <20230208183755.2907771-12-vladimir.zapolskiy@linaro.org>
Hi Vladimir,
On 2/9/23 12:07 AM, Vladimir Zapolskiy wrote:
> Add description of QCE and its corresponding BAM DMA IPs on SM8250 SoC.
>
> Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
> ---
> arch/arm64/boot/dts/qcom/sm8250.dtsi | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm8250.dtsi b/arch/arm64/boot/dts/qcom/sm8250.dtsi
> index e59c16f74d17..d8698d18223e 100644
> --- a/arch/arm64/boot/dts/qcom/sm8250.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8250.dtsi
> @@ -2215,6 +2215,30 @@ ufs_mem_phy_lanes: phy@1d87400 {
> };
> };
>
> + cryptobam: dma-controller@1dc4000 {
> + compatible = "qcom,bam-v1.7.0";
> + reg = <0x0 0x01dc4000 0x0 0x24000>;
> + interrupts = <GIC_SPI 272 IRQ_TYPE_LEVEL_HIGH>;
> + #dma-cells = <1>;
> + qcom,ee = <0>;
> + qcom,controlled-remotely;
> + num-channels = <8>;
> + qcom,num-ees = <2>;
> + iommus = <&apps_smmu 0x586 0x11>,
> + <&apps_smmu 0x596 0x11>;
> + };
> +
> + crypto: crypto@1dfa000 {
> + compatible = "qcom,sm8250-qce", "qcom,sm8150-qce";
> + reg = <0x0 0x01dfa000 0x0 0x6000>;
> + dmas = <&cryptobam 6>, <&cryptobam 7>;
> + dma-names = "rx", "tx";
> + interconnects = <&aggre2_noc MASTER_CRYPTO_CORE_0 &mc_virt SLAVE_EBI_CH0>;
> + interconnect-names = "memory";
> + iommus = <&apps_smmu 0x586 0x11>,
> + <&apps_smmu 0x596 0x11>;
> + };
> +
> tcsr_mutex: hwlock@1f40000 {
> compatible = "qcom,tcsr-mutex";
> reg = <0x0 0x01f40000 0x0 0x40000>;
This patch was part of the v7 arm64 dts fixes I sent out - see [1].
Probably you can use it as a base and make the changes (interconnect
property for the BAM DMA node and qce-compatible names) directly there
and include it in your patch series.
[1].
https://lore.kernel.org/linux-arm-msm/20220921045602.1462007-3-bhupesh.sharma@linaro.org/
Thanks,
Bhupesh
next prev parent reply other threads:[~2023-02-09 12:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 18:37 [PATCH v9 00/14] crypto: qcom-qce: Add YAML bindings & support for newer SoCs Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 01/14] dt-bindings: qcom-qce: Convert bindings to yaml Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 02/14] MAINTAINERS: Add qcom-qce dt-binding file to QUALCOMM CRYPTO DRIVERS section Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 03/14] dt-bindings: qcom-qce: Add 'interconnects' and 'interconnect-names' Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 04/14] dt-bindings: qcom-qce: Add 'iommus' to optional properties Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 05/14] dt-bindings: qcom-qce: Add new SoC compatible strings for qcom-qce Vladimir Zapolskiy
2023-02-09 9:18 ` Krzysztof Kozlowski
2023-02-09 9:19 ` Krzysztof Kozlowski
2023-02-08 18:37 ` [PATCH v9 06/14] dt-bindings: qcom-qce: document optional clocks and clock-names properties Vladimir Zapolskiy
2023-02-09 9:20 ` Krzysztof Kozlowski
2023-02-10 11:17 ` Vladimir Zapolskiy
2023-02-10 11:30 ` Krzysztof Kozlowski
2023-02-08 18:37 ` [PATCH v9 07/14] arm: dts: qcom: ipq4019: update a compatible for QCE IP on IPQ4019 SoC Vladimir Zapolskiy
2023-02-09 9:22 ` Krzysztof Kozlowski
2023-02-08 18:37 ` [PATCH v9 08/14] arm64: dts: qcom: msm8996: update QCE compatible according to a new scheme Vladimir Zapolskiy
2023-02-09 9:23 ` Krzysztof Kozlowski
2023-02-08 18:37 ` [PATCH v9 09/14] arm64: dts: qcom: sdm845: " Vladimir Zapolskiy
2023-02-09 9:23 ` Krzysztof Kozlowski
2023-02-08 18:37 ` [PATCH v9 10/14] arm64: dts: qcom: sm8550: add a family compatible for QCE IP Vladimir Zapolskiy
2023-02-09 9:23 ` Krzysztof Kozlowski
2023-02-08 18:37 ` [PATCH v9 11/14] arm64: dts: qcom: sm8250: add description of Qualcomm Crypto Engine IP Vladimir Zapolskiy
2023-02-09 12:21 ` Bhupesh Sharma [this message]
2023-02-09 14:30 ` Vladimir Zapolskiy
2023-02-13 17:12 ` Bhupesh Sharma
2023-02-14 10:24 ` Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 12/14] crypto: qce: core: Add support to initialize interconnect path Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 13/14] crypto: qce: core: Make clocks optional Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 14/14] crypto: qce: core: Add a compatible based on a SoC name Vladimir Zapolskiy
2023-02-09 9:26 ` Krzysztof Kozlowski
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=7b38331c-3b29-03c1-fbed-f5799d11ca1f@linaro.org \
--to=bhupesh.sharma@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thara.gopinath@gmail.com \
--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 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).