[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <154818353130.20280.17905705223316470797@swboyd.mtv.corp.google.com>
Date: Tue, 22 Jan 2019 10:58:51 -0800
From: Stephen Boyd <swboyd@...omium.org>
To: Andy Gross <andy.gross@...aro.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
David Brown <david.brown@...aro.org>,
Sibi Sankar <sibis@...eaurora.org>
Cc: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 01/10] arm64: dts: qcom: sdm845: Update PIL region memory map
Quoting Bjorn Andersson (2019-01-21 21:51:03)
> @@ -103,10 +138,30 @@
> no-map;
> };
>
> + venus_mem: memory@...00000 {
> + reg = <0 0x95800000 0 0x500000>;
> + no-map;
> + };
> +
> + cdsp_mem: memory@...00000 {
> + reg = <0 0x95d00000 0 0x800000>;
> + no-map;
> + };
> +
> mba_region: memory@...00000 {
> reg = <0 0x96500000 0 0x200000>;
> no-map;
> };
> +
> + slpi_mem: memory@...00000 {
> + reg = <0 0x96700000 0 0x1400000>;
> + no-map;
> + };
> +
> + spss_mem: memory@...00000 {
> + reg = <0 0x97b00000 0 0x100000>;
> + no-map;
> + };
> };
>
What's the plan if certain configurations don't use all these carveouts?
Can we mark the reservation nodes as status = "disabled", or the reverse
and mark them as status = "ok" in all boards, and then reclaim the
memory for peripherals we don't care to use?
Powered by blists - more mailing lists