linux-kernel - Re: (subset) [PATCH 0/3] Fix SMMU on SDX55 and SDX65

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <167591660366.1230100.12722515257767815828.b4-ty@kernel.org>
Date:   Wed,  8 Feb 2023 20:23:20 -0800
From:   Bjorn Andersson <andersson@...nel.org>
To:     Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
        robh+dt@...nel.org, joro@...tes.org,
        krzysztof.kozlowski+dt@...aro.org, will@...nel.org
Cc:     konrad.dybcio@...aro.org, devicetree@...r.kernel.org,
        dmitry.baryshkov@...aro.org, iommu@...ts.linux.dev,
        linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: (subset) [PATCH 0/3] Fix SMMU on SDX55 and SDX65

On Mon, 23 Jan 2023 18:49:28 +0530, Manivannan Sadhasivam wrote:
> Both SDX55 and SDX65 SoCs are using the Qcom version of the ARM SMMU-500
> IP. Even though the SoC specfic compatibles were being used in devicetree,
> the compatibles were not added to the arm-smmu-qcom driver. So they end up
> using the generic ARM SMMU-500 driver instead.
> 
> Spotting this discrepancy, the recent arm,smmu bindings change moved these
> SoCs under the non-qcom implementation of the SMMU.
> 
> [...]

Applied, thanks!

[2/3] ARM: dts: qcom: sdx55: Add Qcom SMMU-500 as the fallback for IOMMU node
      commit: af4ab377543853b690cc85b4c46cf976ab560dc2
[3/3] ARM: dts: qcom: sdx65: Add Qcom SMMU-500 as the fallback for IOMMU node
      commit: 157178a7912e00a0aa0371dc9041952c1a21d112

Best regards,
-- 
Bjorn Andersson <andersson@...nel.org>