Re: [PATCH v2] ARM: dts: ls1021a: add nodes for on-chip ram
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 VillemoesApplied, thanks.
Re: [PATCH v2] ARM: dts: ls1021a: add nodes for on-chip ram
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 Applied, thanks.
Re: [PATCH v2] ARM: dts: ls1021a: add nodes for on-chip ram
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
Re: [PATCH v2] ARM: dts: ls1021a: add nodes for on-chip ram
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