linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vivek Gautam <vivek.gautam@codeaurora.org>
To: joro@8bytes.org, robh+dt@kernel.org, andy.gross@linaro.org,
	iommu@lists.linux-foundation.org, devicetree@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Cc: mark.rutland@arm.com, david.brown@linaro.org,
	linux-kernel@vger.kernel.org, robin.murphy@arm.com,
	will.deacon@arm.com, dianders@chromium.org,
	Vivek Gautam <vivek.gautam@codeaurora.org>
Subject: [PATCH v4 1/2] dt-bindings: arm-smmu: Add binding doc for Qcom smmu-500
Date: Thu, 11 Oct 2018 15:19:29 +0530	[thread overview]
Message-ID: <20181011094930.17010-2-vivek.gautam@codeaurora.org> (raw)
In-Reply-To: <20181011094930.17010-1-vivek.gautam@codeaurora.org>

Qcom's implementation of arm,mmu-500 works well with current
arm-smmu driver implementation. Adding a soc specific compatible
along with arm,mmu-500 makes the bindings future safe.

Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org>
---

Changes since v3:
 - Refined language more to state things directly for the bindings
   description.

 Documentation/devicetree/bindings/iommu/arm,smmu.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu.txt b/Documentation/devicetree/bindings/iommu/arm,smmu.txt
index a6504b37cc21..3133f3ba7567 100644
--- a/Documentation/devicetree/bindings/iommu/arm,smmu.txt
+++ b/Documentation/devicetree/bindings/iommu/arm,smmu.txt
@@ -27,6 +27,10 @@ conditions.
                   "qcom,msm8996-smmu-v2", "qcom,smmu-v2",
                   "qcom,sdm845-smmu-v2", "qcom,smmu-v2".
 
+                  Qcom SoCs implementing "arm,mmu-500" must also include,
+                  as below, SoC-specific compatibles:
+                  "qcom,sdm845-smmu-500", "arm,mmu-500"
+
 - reg           : Base address and size of the SMMU.
 
 - #global-interrupts : The number of global interrupts exposed by the
-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation


  reply	other threads:[~2018-10-11  9:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11  9:49 [PATCH v4 0/2] Enable smmu support on sdm845 Vivek Gautam
2018-10-11  9:49 ` Vivek Gautam [this message]
2018-10-11 22:16   ` [PATCH v4 1/2] dt-bindings: arm-smmu: Add binding doc for Qcom smmu-500 Rob Herring
2018-10-12  6:07     ` Vivek Gautam
2018-12-12  9:48       ` Vivek Gautam
2018-12-12 14:11         ` Will Deacon
2018-10-11  9:49 ` [PATCH v4 2/2] dts: arm64/sdm845: Add node for arm,mmu-500 Vivek Gautam
2019-01-08  6:59   ` Bjorn Andersson
     [not found]     ` <9675f7d8-a726-07d3-34b7-99b7464a6303@codeaurora.org>
2019-01-11  3:15       ` Bjorn Andersson
2018-11-21 15:52 ` [PATCH v4 0/2] Enable smmu support on sdm845 Will Deacon
2018-11-21 16:06   ` Vivek Gautam

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=20181011094930.17010-2-vivek.gautam@codeaurora.org \
    --to=vivek.gautam@codeaurora.org \
    --cc=andy.gross@linaro.org \
    --cc=david.brown@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=will.deacon@arm.com \
    /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).