From: Rob Herring <robh@kernel.org>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: rfoss@kernel.org, andersson@kernel.org, agross@kernel.org,
linux-crypto@vger.kernel.org, konrad.dybcio@linaro.org,
vladimir.zapolskiy@linaro.org, bhupesh.linux@gmail.com,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
krzysztof.kozlowski@linaro.org, robh+dt@kernel.org,
neil.armstrong@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 01/11] dt-bindings: dma: Add support for SM6115 and QCM2290 SoCs
Date: Tue, 4 Apr 2023 08:41:22 -0500 [thread overview]
Message-ID: <168061568226.3782433.11290866098182220844.robh@kernel.org> (raw)
In-Reply-To: <20230402100509.1154220-2-bhupesh.sharma@linaro.org>
On Sun, 02 Apr 2023 15:34:59 +0530, Bhupesh Sharma wrote:
> Add new compatible for BAM DMA engine version v1.7.4 which is
> found on Qualcomm SM6115 and QCM2290 SoCs. Since its very similar
> to v1.7.0 used on SM8150 like SoCs, mark the comptible scheme
> accordingly.
>
> While at it, also update qcom,bam-dma bindings to add comments
> which describe the BAM DMA versions used in SM8150 and SM8250 SoCs.
> This provides an easy reference for identifying the actual BAM DMA
> version available on Qualcomm SoCs.
>
> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
> ---
> .../devicetree/bindings/dma/qcom,bam-dma.yaml | 20 ++++++++++++-------
> 1 file changed, 13 insertions(+), 7 deletions(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2023-04-04 13:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 10:04 [PATCH v5 00/11] arm64: qcom: Enable Crypto Engine for a few Qualcomm SoCs Bhupesh Sharma
2023-04-02 10:04 ` [PATCH v5 01/11] dt-bindings: dma: Add support for SM6115 and QCM2290 SoCs Bhupesh Sharma
2023-04-04 13:41 ` Rob Herring [this message]
2023-04-02 10:05 ` [PATCH v5 02/11] dt-bindings: dma: Increase iommu maxItems for BAM DMA Bhupesh Sharma
2023-04-02 10:05 ` [PATCH v5 03/11] arm64: dts: qcom: sdm8550: Fix the BAM DMA engine compatible string Bhupesh Sharma
2023-04-02 10:05 ` [PATCH v5 04/11] arm64: dts: qcom: sdm845: Fix the slimbam " Bhupesh Sharma
2023-04-02 10:05 ` [PATCH v5 05/11] dt-bindings: qcom-qce: Fix compatible combinations for SM8150 and IPQ4019 SoCs Bhupesh Sharma
2023-04-03 5:36 ` Vladimir Zapolskiy
2023-04-03 6:15 ` Bhupesh Sharma
2023-04-03 10:48 ` Konrad Dybcio
2023-04-03 11:07 ` Bhupesh Sharma
2023-04-02 10:05 ` [PATCH v5 06/11] dt-bindings: qcom-qce: Add compatibles for SM6115 and QCM2290 Bhupesh Sharma
2023-04-02 10:05 ` [PATCH v5 07/11] arm64: dts: qcom: sm6115: Add Crypto Engine support Bhupesh Sharma
2023-04-02 10:05 ` [PATCH v5 08/11] arm64: dts: qcom: sm8150: " Bhupesh Sharma
2023-04-02 10:05 ` [PATCH v5 09/11] arm64: dts: qcom: sm8250: " Bhupesh Sharma
2023-04-02 10:05 ` [PATCH v5 10/11] arm64: dts: qcom: sm8350: " Bhupesh Sharma
2023-04-03 12:15 ` Georgi Djakov
2023-04-04 6:51 ` Bhupesh Sharma
2023-04-02 10:05 ` [PATCH v5 11/11] arm64: dts: qcom: sm8450: add crypto nodes Bhupesh Sharma
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=168061568226.3782433.11290866098182220844.robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhupesh.linux@gmail.com \
--cc=bhupesh.sharma@linaro.org \
--cc=devicetree@vger.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=neil.armstrong@linaro.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).