From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: dts: ls1021a: add nodes for on-chip ram
Date: Tue, 23 Jan 2018 15:11:50 +0800 [thread overview]
Message-ID: <20180123071149.GC27764@dragon> (raw)
In-Reply-To: <1514994345-2471-1-git-send-email-rasmus.villemoes@prevas.dk>
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.
prev parent reply other threads:[~2018-01-23 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 15:38 [PATCH] ARM: dts: ls1021a: add nodes for on-chip ram Rasmus Villemoes
2017-12-26 8:56 ` Shawn Guo
2018-01-03 15:45 ` [PATCH v2] " Rasmus Villemoes
2018-01-19 10:53 ` Rasmus Villemoes
2018-01-23 7:11 ` Shawn Guo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180123071149.GC27764@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).