I noticed that some of the compatibles for either matching SMMU probe
or peripheral workarounds were lingering on my branch.
This series collects them in an effort to get them merged.
The bindings are all there.
I don't think it makes sense for me to look for the source series of
each patch.
Signed-off-by: Konrad Dybcio <[email protected]>
---
Konrad Dybcio (4):
iommu/arm-smmu-qcom: Sort the compatible list alphabetically
iommu/arm-smmu-qcom: Add SM6375 DPU compatible
iommu/arm-smmu-qcom: Add SM6350 DPU compatible
iommu/arm-smmu-qcom: Add SM6375 SMMUv2
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
---
base-commit: 21ef7b1e17d039053edaeaf41142423810572741
change-id: 20230810-topic-lost_smmu_compats-116f2e9f231a
Best regards,
--
Konrad Dybcio <[email protected]>
SM6375 uses a qcom,smmu-v2-style SMMU just for Adreno and friends.
Add a compatible for it.
Signed-off-by: Konrad Dybcio <[email protected]>
---
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
index bdeb587552c0..7f52ac67495f 100644
--- a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
+++ b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
@@ -530,6 +530,7 @@ static const struct of_device_id __maybe_unused qcom_smmu_impl_of_match[] = {
{ .compatible = "qcom,sm6125-smmu-500", .data = &qcom_smmu_500_impl0_data },
{ .compatible = "qcom,sm6350-smmu-v2", .data = &qcom_smmu_v2_data },
{ .compatible = "qcom,sm6350-smmu-500", .data = &qcom_smmu_500_impl0_data },
+ { .compatible = "qcom,sm6375-smmu-v2", .data = &qcom_smmu_v2_data },
{ .compatible = "qcom,sm6375-smmu-500", .data = &qcom_smmu_500_impl0_data },
{ .compatible = "qcom,sm8150-smmu-500", .data = &qcom_smmu_500_impl0_data },
{ .compatible = "qcom,sm8250-smmu-500", .data = &qcom_smmu_500_impl0_data },
--
2.41.0
Add the SM6375 DPU compatible to clients compatible list, as it also
needs the workarounds.
Acked-by: Dmitry Baryshkov <[email protected]>
Signed-off-by: Konrad Dybcio <[email protected]>
---
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
index 3800ab478216..cc574928c707 100644
--- a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
+++ b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
@@ -253,6 +253,7 @@ static const struct of_device_id qcom_smmu_client_of_match[] __maybe_unused = {
{ .compatible = "qcom,sc8280xp-mdss" },
{ .compatible = "qcom,sdm845-mdss" },
{ .compatible = "qcom,sdm845-mss-pil" },
+ { .compatible = "qcom,sm6375-mdss" },
{ .compatible = "qcom,sm8150-mdss" },
{ .compatible = "qcom,sm8250-mdss" },
{ }
--
2.41.0
On Thu, 10 Aug 2023 19:45:03 +0200, Konrad Dybcio wrote:
> I noticed that some of the compatibles for either matching SMMU probe
> or peripheral workarounds were lingering on my branch.
>
> This series collects them in an effort to get them merged.
>
> The bindings are all there.
>
> [...]
Applied to will (for-joerg/arm-smmu/updates), thanks!
[1/4] iommu/arm-smmu-qcom: Sort the compatible list alphabetically
https://git.kernel.org/will/c/ec2ff4d8160f
[2/4] iommu/arm-smmu-qcom: Add SM6375 DPU compatible
https://git.kernel.org/will/c/6ebaa77ce483
[3/4] iommu/arm-smmu-qcom: Add SM6350 DPU compatible
https://git.kernel.org/will/c/7e85676a4523
[4/4] iommu/arm-smmu-qcom: Add SM6375 SMMUv2
https://git.kernel.org/will/c/757d591d965f
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev