Message ID | 1629344185-27368-7-git-send-email-sibis@codeaurora.org (mailing list archive) |
---|---|
State | Superseded |
Headers | show |
Series | Add Modem support on SC7280 SoCs | expand |
Hi Sibi, On 19-08-21, 09:06, Sibi Sankar wrote: > diff --git a/arch/arm64/boot/dts/qcom/sc7280.dtsi b/arch/arm64/boot/dts/qcom/sc7280.dtsi > index 5e4f4f3b738a..894106efadfe 100644 > --- a/arch/arm64/boot/dts/qcom/sc7280.dtsi > +++ b/arch/arm64/boot/dts/qcom/sc7280.dtsi > @@ -48,6 +48,16 @@ > #size-cells = <2>; > ranges; > > + hyp_mem: memory@80000000 { > + reg = <0x0 0x80000000 0x0 0x600000>; > + no-map; This should conflict with the memory defined in this file: memory@80000000 { device_type = "memory"; /* We expect the bootloader to fill in the size */ reg = <0 0x80000000 0 0>; }; I think this should be updated?
On 2021-08-19 10:07, Vinod Koul wrote: > Hi Sibi, > > On 19-08-21, 09:06, Sibi Sankar wrote: > >> diff --git a/arch/arm64/boot/dts/qcom/sc7280.dtsi >> b/arch/arm64/boot/dts/qcom/sc7280.dtsi >> index 5e4f4f3b738a..894106efadfe 100644 >> --- a/arch/arm64/boot/dts/qcom/sc7280.dtsi >> +++ b/arch/arm64/boot/dts/qcom/sc7280.dtsi >> @@ -48,6 +48,16 @@ >> #size-cells = <2>; >> ranges; >> >> + hyp_mem: memory@80000000 { >> + reg = <0x0 0x80000000 0x0 0x600000>; >> + no-map; > > This should conflict with the memory defined in this file: > > memory@80000000 { > device_type = "memory"; > /* We expect the bootloader to fill in the size */ > reg = <0 0x80000000 0 0>; > }; > > I think this should be updated? Vinod, I prefer we leave ^^ node untouched. For platforms using hyp_mem, the regions defined in the memory map are valid and for the other platforms not using hyp_mem we would just delete them in the board files anyway.
On Fri 20 Aug 07:09 PDT 2021, Sibi Sankar wrote: > On 2021-08-19 10:07, Vinod Koul wrote: > > Hi Sibi, > > > > On 19-08-21, 09:06, Sibi Sankar wrote: > > > > > diff --git a/arch/arm64/boot/dts/qcom/sc7280.dtsi > > > b/arch/arm64/boot/dts/qcom/sc7280.dtsi > > > index 5e4f4f3b738a..894106efadfe 100644 > > > --- a/arch/arm64/boot/dts/qcom/sc7280.dtsi > > > +++ b/arch/arm64/boot/dts/qcom/sc7280.dtsi > > > @@ -48,6 +48,16 @@ > > > #size-cells = <2>; > > > ranges; > > > > > > + hyp_mem: memory@80000000 { > > > + reg = <0x0 0x80000000 0x0 0x600000>; > > > + no-map; > > > > This should conflict with the memory defined in this file: > > > > memory@80000000 { > > device_type = "memory"; > > /* We expect the bootloader to fill in the size */ > > reg = <0 0x80000000 0 0>; > > }; > > > > I think this should be updated? > > Vinod, > > I prefer we leave ^^ node untouched. For platforms using hyp_mem, the > regions defined in the memory map are valid and for the other > platforms not using hyp_mem we would just delete them in the board > files anyway. Logically this node describes where there is RAM, the reserved-memory then subtracts blocks of memory out of that. So I think it's perfectly legal for a region at the base to be marked as no-map. That said, isn't the address in the memory node just a placeholder? Regards, Bjorn
diff --git a/arch/arm64/boot/dts/qcom/sc7280.dtsi b/arch/arm64/boot/dts/qcom/sc7280.dtsi index 5e4f4f3b738a..894106efadfe 100644 --- a/arch/arm64/boot/dts/qcom/sc7280.dtsi +++ b/arch/arm64/boot/dts/qcom/sc7280.dtsi @@ -48,6 +48,16 @@ #size-cells = <2>; ranges; + hyp_mem: memory@80000000 { + reg = <0x0 0x80000000 0x0 0x600000>; + no-map; + }; + + xbl_mem: memory@80600000 { + reg = <0x0 0x80600000 0x0 0x200000>; + no-map; + }; + aop_mem: memory@80800000 { reg = <0x0 0x80800000 0x0 0x60000>; no-map; @@ -59,6 +69,16 @@ no-map; }; + reserved_xbl_uefi_log: memory@80880000 { + reg = <0x0 0x80884000 0x0 0x10000>; + no-map; + }; + + sec_apps_mem: memory@808ff000 { + reg = <0x0 0x808ff000 0x0 0x1000>; + no-map; + }; + smem_mem: memory@80900000 { reg = <0x0 0x80900000 0x0 0x200000>; no-map; @@ -69,10 +89,24 @@ reg = <0x0 0x80b00000 0x0 0x100000>; }; + wlan_fw_mem: memory@80c00000 { + reg = <0x0 0x80c00000 0x0 0xc00000>; + no-map; + }; + ipa_fw_mem: memory@8b700000 { reg = <0 0x8b700000 0 0x10000>; no-map; }; + + rmtfs_mem: memory@9c900000 { + compatible = "qcom,rmtfs-mem"; + reg = <0x0 0x9c900000 0x0 0x280000>; + no-map; + + qcom,client-id = <1>; + qcom,vmid = <15>; + }; }; cpus {