From: Bhupesh Sharma <bhupesh.sharma@linaro.org>
To: linux-arm-msm@vger.kernel.org
Cc: agross@kernel.org, linux-kernel@vger.kernel.org,
devicetree@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
Subject: [PATCH 0/5] arm64: dts: qcom: Enable Crypto Engine for a few Qualcomm SoCs
Date: Wed, 22 Mar 2023 00:31:13 +0530 [thread overview]
Message-ID: <20230321190118.3327360-1-bhupesh.sharma@linaro.org> (raw)
This patchset enables Crypto Engine support for Qualcomm SoCs like
SM6115, SM8150, SM8250 and SM8350.
While at it, also fix the compatible string for BAM DMA engine
used in sdm845.dtsi
Note that:
- SM8250 crypto engine patch utilizes the work already done by myself and
Vladimir.
- SM8350 crypto engine patch utilizes the work already done by Robert.
This patchset depends on the dt-bindings patch which added support for
SM6115 and QCS2290 SoCs:
https://lore.kernel.org/linux-arm-msm/20230321184811.3325725-1-bhupesh.sharma@linaro.org/
Also this patchset is rebased on linux-next/master.
Bhupesh Sharma (5):
arm64: dts: qcom: sdm845: Fix the BAM DMA engine compatible string
arm64: dts: qcom: sm6115: Add Crypto Engine support
arm64: dts: qcom: sm8150: Add Crypto Engine support
arm64: dts: qcom: sm8250: Add Crypto Engine support
arm64: dts: qcom: sm8350: Add Crypto Engine support
arch/arm64/boot/dts/qcom/sdm845.dtsi | 2 +-
arch/arm64/boot/dts/qcom/sm6115.dtsi | 26 ++++++++++++++++++++++++++
arch/arm64/boot/dts/qcom/sm8150.dtsi | 26 ++++++++++++++++++++++++++
arch/arm64/boot/dts/qcom/sm8250.dtsi | 26 ++++++++++++++++++++++++++
arch/arm64/boot/dts/qcom/sm8350.dtsi | 26 ++++++++++++++++++++++++++
5 files changed, 105 insertions(+), 1 deletion(-)
--
2.38.1
next reply other threads:[~2023-03-21 19:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 19:01 Bhupesh Sharma [this message]
2023-03-21 19:01 ` [PATCH 1/5] arm64: dts: qcom: sdm845: Fix the BAM DMA engine compatible string Bhupesh Sharma
2023-03-21 19:29 ` Konrad Dybcio
2023-03-21 19:01 ` [PATCH 2/5] arm64: dts: qcom: sm6115: Add Crypto Engine support Bhupesh Sharma
2023-03-21 20:38 ` Stephan Gerhold
2023-03-22 10:41 ` Bhupesh Sharma
2023-03-21 19:01 ` [PATCH 3/5] arm64: dts: qcom: sm8150: " Bhupesh Sharma
2023-03-21 19:01 ` [PATCH 4/5] arm64: dts: qcom: sm8250: " Bhupesh Sharma
2023-03-21 19:01 ` [PATCH 5/5] arm64: dts: qcom: sm8350: " Bhupesh Sharma
2023-03-21 19:27 ` [PATCH 0/5] arm64: dts: qcom: Enable Crypto Engine for a few Qualcomm SoCs Konrad Dybcio
2023-03-22 8:33 ` Bhupesh Sharma
2023-03-22 8:34 ` Konrad Dybcio
2023-03-22 8:35 ` Krzysztof Kozlowski
2023-03-22 14:45 ` (subset) " 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=20230321190118.3327360-1-bhupesh.sharma@linaro.org \
--to=bhupesh.sharma@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhupesh.linux@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rfoss@kernel.org \
--cc=robh+dt@kernel.org \
--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).