devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	andersson@kernel.org, will@kernel.org, joro@8bytes.org,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org
Cc: konrad.dybcio@linaro.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	iommu@lists.linux.dev, dmitry.baryshkov@linaro.org
Subject: Re: [PATCH 1/3] dt-bindings: arm-smmu: Fix binding for SDX55 and SDX65
Date: Mon, 23 Jan 2023 16:49:21 +0100	[thread overview]
Message-ID: <ee531a81-8ba8-b436-ddee-44a512c7be17@linaro.org> (raw)
In-Reply-To: <20230123131931.263024-2-manivannan.sadhasivam@linaro.org>

On 23/01/2023 14:19, Manivannan Sadhasivam wrote:
> Both SDX55 and SDX66 SoCs are using the Qualcomm version of the SMMU-500
> IP. But the binding lists them under the non-qcom implementation which is
> not correct.
> 
> So fix the binding by moving these two SoCs under "qcom,smmu-500"
> implementation.
> 


Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Best regards,
Krzysztof


  reply	other threads:[~2023-01-23 15:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 13:19 [PATCH 0/3] Fix SMMU on SDX55 and SDX65 Manivannan Sadhasivam
2023-01-23 13:19 ` [PATCH 1/3] dt-bindings: arm-smmu: Fix binding for " Manivannan Sadhasivam
2023-01-23 15:49   ` Krzysztof Kozlowski [this message]
2023-01-23 13:19 ` [PATCH 2/3] ARM: dts: qcom: sdx55: Add Qcom SMMU-500 as the fallback for IOMMU node Manivannan Sadhasivam
2023-01-23 13:21   ` Konrad Dybcio
2023-01-23 13:19 ` [PATCH 3/3] ARM: dts: qcom: sdx65: " Manivannan Sadhasivam
2023-01-23 13:21   ` Konrad Dybcio
2023-01-24 12:10 ` [PATCH 0/3] Fix SMMU on SDX55 and SDX65 Will Deacon
2023-02-09  4:23 ` (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=ee531a81-8ba8-b436-ddee-44a512c7be17@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=will@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;
as well as URLs for NNTP newsgroup(s).