linux-kernel - Re: [RESEND PATCH v4 1/1] dt-bindings: arm-smmu: Add binding doc for Qcom smmu-500

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20181213104524.GA31177@edgewater-inn.cambridge.arm.com>
Date:   Thu, 13 Dec 2018 10:45:24 +0000
From:   Will Deacon <will.deacon@....com>
To:     Vivek Gautam <vivek.gautam@...eaurora.org>
Cc:     joro@...tes.org, iommu@...ts.linux-foundation.org,
        devicetree@...r.kernel.org, robh+dt@...nel.org,
        mark.rutland@....com, linux-arm-msm@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH v4 1/1] dt-bindings: arm-smmu: Add binding doc for
 Qcom smmu-500

On Thu, Dec 13, 2018 at 02:35:07PM +0530, Vivek Gautam wrote:
> Qcom's implementation of arm,mmu-500 works well with current
> arm-smmu driver implementation. Adding a soc specific compatible
> along with arm,mmu-500 makes the bindings future safe.
> 
> Signed-off-by: Vivek Gautam <vivek.gautam@...eaurora.org>
> Reviewed-by: Rob Herring <robh@...nel.org>
> Cc: Will Deacon <will.deacon@....com>
> ---
> 
> Hi Joerg,
> I am picking this out separately from the sdm845 smmu support
> series [1], so that this can go through iommu tree.
> The dt patch from the series [1] can be taken through arm-soc tree.
> 
> Hi Will,
> As asked [2], here's the resend version of dt binding patch for sdm845.
> Kindly ack this so that Joerg can pull this in.

Acked-by: Will Deacon <will.deacon@....com>

Joerg -- please can you take this on top of the pull request I sent already?
Vivek included it as part of a separate series which I thought was going
via arm-soc, but actually it needs to go with the other arm-smmu patches
in order to avoid conflicts.

Cheers,

Will

>  Documentation/devicetree/bindings/iommu/arm,smmu.txt | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu.txt b/Documentation/devicetree/bindings/iommu/arm,smmu.txt
> index a6504b37cc21..3133f3ba7567 100644
> --- a/Documentation/devicetree/bindings/iommu/arm,smmu.txt
> +++ b/Documentation/devicetree/bindings/iommu/arm,smmu.txt
> @@ -27,6 +27,10 @@ conditions.
>                    "qcom,msm8996-smmu-v2", "qcom,smmu-v2",
>                    "qcom,sdm845-smmu-v2", "qcom,smmu-v2".
>  
> +                  Qcom SoCs implementing "arm,mmu-500" must also include,
> +                  as below, SoC-specific compatibles:
> +                  "qcom,sdm845-smmu-500", "arm,mmu-500"
> +
>  - reg           : Base address and size of the SMMU.
>  
>  - #global-interrupts : The number of global interrupts exposed by the
> -- 
> QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
> of Code Aurora Forum, hosted by The Linux Foundation
>