Message ID | 1514994345-2471-1-git-send-email-rasmus.villemoes@prevas.dk (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On 2018-01-03 16:45, Rasmus Villemoes wrote: > Although the two nodes constitute one contiguous 128K region, still > describe them separately: > > - That's how they are described in the reference manual: "Each OCRAM > occupies a 64 KB of address region...", and the names ocram1 and > ocram2 are also as used in the manual. > > - The two areas are treated differently by the boot ROM code: OCRAM2 is > zero-initialized, while, again quoting the RM, "software must perform > the zero initialization of OCRAM1." ping
On Wed, Jan 03, 2018 at 04:45:45PM +0100, Rasmus Villemoes wrote: > Although the two nodes constitute one contiguous 128K region, still > describe them separately: > > - That's how they are described in the reference manual: "Each OCRAM > occupies a 64 KB of address region...", and the names ocram1 and > ocram2 are also as used in the manual. > > - The two areas are treated differently by the boot ROM code: OCRAM2 is > zero-initialized, while, again quoting the RM, "software must perform > the zero initialization of OCRAM1." > > Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk> Applied, thanks.
diff --git a/arch/arm/boot/dts/ls1021a.dtsi b/arch/arm/boot/dts/ls1021a.dtsi index 96aa7752dd0d..7bb5896b3726 100644 --- a/arch/arm/boot/dts/ls1021a.dtsi +++ b/arch/arm/boot/dts/ls1021a.dtsi @@ -748,5 +748,21 @@ <0000 0 0 3 &gic GIC_SPI 191 IRQ_TYPE_LEVEL_HIGH>, <0000 0 0 4 &gic GIC_SPI 193 IRQ_TYPE_LEVEL_HIGH>; }; + + ocram1: sram@10000000 { + compatible = "mmio-sram"; + reg = <0x0 0x10000000 0x0 0x10000>; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0x0 0x0 0x10000000 0x10000>; + }; + + ocram2: sram@10010000 { + compatible = "mmio-sram"; + reg = <0x0 0x10010000 0x0 0x10000>; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0x0 0x0 0x10010000 0x10000>; + }; }; };
Although the two nodes constitute one contiguous 128K region, still describe them separately: - That's how they are described in the reference manual: "Each OCRAM occupies a 64 KB of address region...", and the names ocram1 and ocram2 are also as used in the manual. - The two areas are treated differently by the boot ROM code: OCRAM2 is zero-initialized, while, again quoting the RM, "software must perform the zero initialization of OCRAM1." Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk> --- v2: add changelog explaining the split in two nodes. arch/arm/boot/dts/ls1021a.dtsi | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)