Message ID | 20221114170635.1406534-1-dmitry.baryshkov@linaro.org (mailing list archive) |
---|---|
Headers | show |
Series | iommu/arm-smmu-qcom: Rework Qualcomm SMMU bindings and implementation | expand |
On Mon, 14 Nov 2022 20:06:25 +0300, Dmitry Baryshkov wrote: > The main goal of this patchset is to define a generic qcom,smmu-500 > binding to be used by newer Qualcomm platforms instead of defining each > and every SoC line with no actual differences between the compats. > > While preparing this change it was required to cleanup the existing > bindings and to rework the way the arm-smmu-qcom implementation handles > binding to IOMMU devices. > > [...] Applied to arm64 (for-joerg/arm-smmu/bindings), thanks! Note that I removed the 'qcom_smmu_data' structure completely as it was no longer referenced after patch 9. [01/10] dt-bindings: arm-smmu: Add missing Qualcomm SMMU compatibles https://git.kernel.org/arm64/c/dbf88f743583 [02/10] dt-bindings: arm-smmu: fix clocks/clock-names schema https://git.kernel.org/arm64/c/982295bfe369 [03/10] dt-bindings: arm-smmu: add special case for Google Cheza platform https://git.kernel.org/arm64/c/3a12e8c06536 [04/10] dt-bindings: arm-smmu: Add generic qcom,smmu-500 bindings https://git.kernel.org/arm64/c/6c84bbd103d8 [05/10] iommu/arm-smmu-qcom: Move implementation data into match data https://git.kernel.org/arm64/c/4c1d0ad153f8 [06/10] iommu/arm-smmu-qcom: Move the qcom,adreno-smmu check into qcom_smmu_create https://git.kernel.org/arm64/c/30b912a03d91 [07/10] iommu/arm-smmu-qcom: provide separate implementation for SDM845-smmu-500 https://git.kernel.org/arm64/c/417b76adcf1d [08/10] iommu/arm-smmu-qcom: Merge table from arm-smmu-qcom-debug into match data https://git.kernel.org/arm64/c/4172dda2b30a [09/10] iommu/arm-smmu-qcom: Stop using mmu500 reset for v2 MMUs https://git.kernel.org/arm64/c/b4c6ee515c42 [10/10] iommu/arm-smmu-qcom: Add generic qcom,smmu-500 match entry https://git.kernel.org/arm64/c/80b71080720e Cheers,
On 14/11/2022 18:06, Dmitry Baryshkov wrote: > The main goal of this patchset is to define a generic qcom,smmu-500 > binding to be used by newer Qualcomm platforms instead of defining each > and every SoC line with no actual differences between the compats. > > While preparing this change it was required to cleanup the existing > bindings and to rework the way the arm-smmu-qcom implementation handles > binding to IOMMU devices. > > Changes since RFC v2: > - Dropped the dts patch, picked up by Bjorn > - Fixed minor nits in commit messages and in-file comments (noted by > Krzysztof and Richard Acayan) > > Changes since RFC v1: > - Added the dts patch fixing order of clocks in msm8996.dtsi > - Fixed the DT bot errors > - Added separate clause for Google Cheza devices Please continue the version numbering. RFC is also a patch and also a version. This is v3. Your next will be v4. Best regards, Krzysztof
On Fri, Nov 18, 2022 at 01:41:24PM +0100, Krzysztof Kozlowski wrote: > On 14/11/2022 18:06, Dmitry Baryshkov wrote: > > The main goal of this patchset is to define a generic qcom,smmu-500 > > binding to be used by newer Qualcomm platforms instead of defining each > > and every SoC line with no actual differences between the compats. > > > > While preparing this change it was required to cleanup the existing > > bindings and to rework the way the arm-smmu-qcom implementation handles > > binding to IOMMU devices. > > > > Changes since RFC v2: > > - Dropped the dts patch, picked up by Bjorn > > - Fixed minor nits in commit messages and in-file comments (noted by > > Krzysztof and Richard Acayan) > > > > Changes since RFC v1: > > - Added the dts patch fixing order of clocks in msm8996.dtsi > > - Fixed the DT bot errors > > - Added separate clause for Google Cheza devices > > Please continue the version numbering. RFC is also a patch and also a > version. This is v3. Your next will be v4. I queued this already, so hopefully there won't be a next version! Will