From: Richard Acayan <mailingradian@gmail.com>
To: iommu@lists.linux.dev
Cc: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Sai Prakash Ranjan <quic_saipraka@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Richard Acayan <mailingradian@gmail.com>,
Emma Anholt <emma@anholt.net>,
Sibi Sankar <quic_sibis@quicinc.com>,
Rob Clark <robdclark@chromium.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: [PATCH v2 0/2] iommu: SMMU for SDM670
Date: Tue, 4 Oct 2022 18:46:17 -0400 [thread overview]
Message-ID: <20221004224619.16406-1-mailingradian@gmail.com> (raw)
Changes since v1 (no emails related to this series since last week):
- accumulate tags (both were added because it seems like the discussion
ended in agreement to keep adding compatible strings to the driver)
This adds the compatible string for the Qualcomm Snapdragon 670's SMMU. The
SMMU is necessary for GENI I2C, included in initial bringup because it
doesn't need non-trivial patches except for patches conventionally added
before the initial device tree (global clock controller and pinctrl).
Richard Acayan (2):
dt-bindings: iommu: arm-smmu: add sdm670 compatible
iommu: arm-smmu-qcom: add sdm670 compatible
Documentation/devicetree/bindings/iommu/arm,smmu.yaml | 1 +
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 1 +
2 files changed, 2 insertions(+)
--
2.38.0
next reply other threads:[~2022-10-04 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 22:46 Richard Acayan [this message]
2022-10-04 22:46 ` [PATCH v2 1/2] dt-bindings: iommu: arm-smmu: add sdm670 compatible Richard Acayan
2022-10-04 22:46 ` [PATCH v2 2/2] iommu: arm-smmu-qcom: " Richard Acayan
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=20221004224619.16406-1-mailingradian@gmail.com \
--to=mailingradian@gmail.com \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emma@anholt.net \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=quic_saipraka@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=robdclark@chromium.org \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--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).