From: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>,
dmaengine@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org
Cc: agross@kernel.org, linux-kernel@vger.kernel.org,
andersson@kernel.org, bhupesh.linux@gmail.com, vkoul@kernel.org,
krzysztof.kozlowski@linaro.org, robh+dt@kernel.org,
konrad.dybcio@linaro.org
Subject: Re: [PATCH 1/2] dt-bindings: dma: Add support for SM6115 and QCS2290 SoCs
Date: Fri, 24 Mar 2023 14:08:35 +0200 [thread overview]
Message-ID: <7b26e32d-6f3e-4e1f-33a7-0a994ae8526d@linaro.org> (raw)
In-Reply-To: <20230320071211.3005769-1-bhupesh.sharma@linaro.org>
Hi Bhupesh,
On 3/20/23 09:12, Bhupesh Sharma wrote:
> Add new compatible for BAM DMA engine version v1.7.4 which is
> found on Qualcomm SM6115 and QCS2290 SoCs.
>
> 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>
> ---
> Documentation/devicetree/bindings/dma/qcom,bam-dma.yaml | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/dma/qcom,bam-dma.yaml b/Documentation/devicetree/bindings/dma/qcom,bam-dma.yaml
> index f1ddcf672261..4c8536df98fe 100644
> --- a/Documentation/devicetree/bindings/dma/qcom,bam-dma.yaml
> +++ b/Documentation/devicetree/bindings/dma/qcom,bam-dma.yaml
> @@ -20,8 +20,10 @@ properties:
> - qcom,bam-v1.3.0
> # MSM8974, APQ8074 and APQ8084
> - qcom,bam-v1.4.0
> - # MSM8916 and SDM845
> + # MSM8916, SDM845, SM8150 and SM8250
> - qcom,bam-v1.7.0
> + # SM6115 and QRB2290
> + - qcom,bam-v1.7.4
>
> clocks:
> maxItems: 1
apparently it's a good time to implement a switch in compatible values
similar to the one done for QCE:
https://lore.kernel.org/linux-arm-msm/20230222172240.3235972-6-vladimir.zapolskiy@linaro.org/
If this is done in the nearest time, then new platfrom QCE changes
can be seamlessly added after the next merge window, also the change
in the compatible values model shall resolve multiple technical
concerns including the one above about 1/1 change in the series.
--
Best wishes,
Vladimir
next prev parent reply other threads:[~2023-03-24 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 7:12 [PATCH 1/2] dt-bindings: dma: Add support for SM6115 and QCS2290 SoCs Bhupesh Sharma
2023-03-20 7:12 ` [PATCH 2/2] dmaengine: qcom: bam_dma: Add support for BAM engine v1.7.4 Bhupesh Sharma
2023-03-20 10:42 ` Konrad Dybcio
2023-03-21 6:34 ` Bhupesh Sharma
2023-03-24 12:08 ` Vladimir Zapolskiy [this message]
2023-03-28 5:53 ` [PATCH 1/2] dt-bindings: dma: Add support for SM6115 and QCS2290 SoCs 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=7b26e32d-6f3e-4e1f-33a7-0a994ae8526d@linaro.org \
--to=vladimir.zapolskiy@linaro.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=dmaengine@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=robh+dt@kernel.org \
--cc=vkoul@kernel.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