linux-kernel - Re: [PATCH] arm64: dts: qcom: Remove "iommus" property from PCIe nodes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <168088927577.2561591.5257509522357724563.b4-ty@kernel.org>
Date:   Fri,  7 Apr 2023 10:41:13 -0700
From:   Bjorn Andersson <andersson@...nel.org>
To:     robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
        Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc:     linux-kernel@...r.kernel.org, Rob Herring <robh@...nel.org>,
        konrad.dybcio@...aro.org, devicetree@...r.kernel.org,
        linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: Remove "iommus" property from PCIe nodes

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@...nel.org>