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.
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Rasmus Villemoes
<rasmus.villemoes-rjjw5hvvQKZaa/9Udqfwiw@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [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-rjjw5hvvQKZaa/9Udqfwiw@public.gmane.org>
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-rjjw5hvvQKZaa/9Udqfwiw@public.gmane.org>
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [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.
next prev parent reply other threads:[~2018-01-23 7:11 UTC|newest]
Thread overview: 15+ 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-21 15:38 ` Rasmus Villemoes
2017-12-21 15:38 ` Rasmus Villemoes
2017-12-26 8:56 ` Shawn Guo
2017-12-26 8:56 ` Shawn Guo
2017-12-26 8:56 ` Shawn Guo
2018-01-03 15:45 ` [PATCH v2] " Rasmus Villemoes
2018-01-03 15:45 ` Rasmus Villemoes
2018-01-03 15:45 ` Rasmus Villemoes
2018-01-19 10:53 ` Rasmus Villemoes
2018-01-19 10:53 ` Rasmus Villemoes
2018-01-19 10:53 ` Rasmus Villemoes
2018-01-23 7:11 ` Shawn Guo [this message]
2018-01-23 7:11 ` Shawn Guo
2018-01-23 7:11 ` Shawn Guo
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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.