linux-kernel - Re: [PATCH v4 02/10] arm64: dts: qcom: sdm845: Define rmtfs memory

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: <20190130064740.GB2387@tuxbook-pro>
Date:   Tue, 29 Jan 2019 22:47:40 -0800
From:   Bjorn Andersson <bjorn.andersson@...aro.org>
To:     Andy Gross <andy.gross@...aro.org>,
        David Brown <david.brown@...aro.org>
Cc:     Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Ohad Ben-Cohen <ohad@...ery.com>,
        Arun Kumar Neelakantam <aneela@...eaurora.org>,
        Sibi Sankar <sibis@...eaurora.org>,
        linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-remoteproc@...r.kernel.org
Subject: Re: [PATCH v4 02/10] arm64: dts: qcom: sdm845: Define rmtfs memory

On Tue 29 Jan 15:20 PST 2019, Bjorn Andersson wrote:

> Define the rmtfs memory node, as described in version 10 of the memory
> map.
> 
> Signed-off-by: Bjorn Andersson <bjorn.andersson@...aro.org>
> ---
> 
> Changes since v3:
> - Labeled the node
> 
>  arch/arm64/boot/dts/qcom/sdm845.dtsi | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi b/arch/arm64/boot/dts/qcom/sdm845.dtsi
> index c363848e9001..afaffcc1e835 100644
> --- a/arch/arm64/boot/dts/qcom/sdm845.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sdm845.dtsi
> @@ -78,6 +78,15 @@
>  			no-map;
>  		};
>  
> +		mpss_efs: memory@...00000 {
> +			compatible = "qcom,rmtfs-mem";
> +			reg = <0 0x85d00000 0 0x200000>;

It would be nice if this is how math works, but unfortunately I missed
that this overlaps with the xbl_mem below.

Will fix and resend the series.

Regards,
Bjorn

> +			no-map;
> +
> +			qcom,client-id = <1>;
> +			qcom,vmid = <15>;
> +		};
> +
>  		xbl_mem: memory@...00000 {
>  			reg = <0x0 0x85e00000 0 0x100000>;
>  			no-map;
> -- 
> 2.18.0
>