From: Bjorn Andersson <andersson@kernel.org>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
konrad.dybcio@linaro.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: Remove "iommus" property from PCIe nodes
Date: Fri, 7 Apr 2023 10:41:13 -0700 [thread overview]
Message-ID: <168088927577.2561591.5257509522357724563.b4-ty@kernel.org> (raw)
In-Reply-To: <20230308075648.134119-1-manivannan.sadhasivam@linaro.org>
On Wed, 8 Mar 2023 13:26:48 +0530, Manivannan Sadhasivam wrote:
> Currently, most of the Qualcomm SoCs specify both "iommus" and "iommu-map"
> properties for the PCIe nodes. First one passes the SMR mask to the iommu
> driver and the latter specifies the SID for each PCIe device.
>
> But with "iommus" property, the PCIe controller will be added to the
> iommu group along with the devices. This makes no sense because the
> controller will not initiate any DMA transaction on its own. And moreover,
> it is not strictly required to pass the SMR mask to the iommu driver. If
> the "iommus" property is not present, then the default mask of "0" would be
> used which should work for all PCIe devices.
>
> [...]
Applied, thanks!
[1/1] arm64: dts: qcom: Remove "iommus" property from PCIe nodes
commit: 6340b391e15094575911ab0d96bfff09deadafba
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-04-07 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 7:56 Manivannan Sadhasivam
2023-03-16 2:31 ` Bjorn Andersson
2023-03-16 5:52 ` Manivannan Sadhasivam
2023-03-22 3:26 ` Bjorn Andersson
2023-04-07 17:41 ` Bjorn Andersson [this message]
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=168088927577.2561591.5257509522357724563.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=devicetree@vger.kernel.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=robh@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
all inboxes | Powered by JetHome®