From: Richard Acayan <mailingradian@gmail.com>
To: linux-arm-msm@vger.kernel.org
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>,
Bjorn Andersson <andersson@kernel.org>,
Sai Prakash Ranjan <quic_saipraka@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Clark <robdclark@chromium.org>,
Sibi Sankar <sibis@codeaurora.org>,
Loic Poulain <loic.poulain@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
iommu@lists.linux.dev, devicetree@vger.kernel.org,
Richard Acayan <mailingradian@gmail.com>
Subject: [PATCH 0/2] iommu: SMMU for SDM670
Date: Tue, 20 Sep 2022 18:39:54 -0400 [thread overview]
Message-ID: <20220920223955.151507-1-mailingradian@gmail.com> (raw)
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).
Documentation/devicetree/bindings/iommu/arm,smmu.yaml | 1 +
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 1 +
2 files changed, 2 insertions(+)
next reply other threads:[~2022-09-20 22:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 22:39 Richard Acayan [this message]
2022-09-20 22:39 ` [PATCH 1/2] dt-bindings: iommu: arm-smmu: add sdm670 compatible Richard Acayan
2022-09-21 7:31 ` Krzysztof Kozlowski
2022-09-20 22:39 ` [PATCH 2/2] iommu: arm-smmu-qcom: " Richard Acayan
2022-09-20 23:45 ` Konrad Dybcio
2022-09-21 7:31 ` Krzysztof Kozlowski
2022-09-21 18:47 ` Konrad Dybcio
2022-09-21 18:48 ` Konrad Dybcio
2022-09-21 19:05 ` Krzysztof Kozlowski
2022-09-21 21:14 ` Konrad Dybcio
2022-09-22 2:38 ` Richard Acayan
2022-09-22 6:41 ` Krzysztof Kozlowski
2022-09-22 10:48 ` Konrad Dybcio
2022-09-22 12:18 ` Krzysztof Kozlowski
2022-09-23 22:24 ` Richard Acayan
2022-09-22 6:39 ` Krzysztof Kozlowski
2022-10-18 10:21 ` Dmitry Baryshkov
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=20220920223955.151507-1-mailingradian@gmail.com \
--to=mailingradian@gmail.com \
--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@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=quic_saipraka@quicinc.com \
--cc=robdclark@chromium.org \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sibis@codeaurora.org \
--cc=vkoul@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