From: "Andreas Färber" <afaerber@suse.de>
To: Neil Armstrong <narmstrong@baylibre.com>,
khilman@baylibre.com, carlo@caione.org
Cc: xypron.glpk@gmx.de, linux-amlogic@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4] ARM64: dts: meson-gx: Add reserved memory zone and usable memory range
Date: Wed, 18 Jan 2017 01:09:02 +0100 [thread overview]
Message-ID: <635fece7-4edf-13b4-3de1-e093abae655f@suse.de> (raw)
In-Reply-To: <1484129414-23325-1-git-send-email-narmstrong@baylibre.com>
Am 11.01.2017 um 11:10 schrieb Neil Armstrong:
> diff --git a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
> index eada0b5..66677b5 100644
> --- a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
> +++ b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
> @@ -55,6 +55,18 @@
> #address-cells = <2>;
> #size-cells = <2>;
>
> + reserved-memory {
Should this get a label for future gx*-level additions?
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + /* 2MiB reserved for ARM Trusted Firmware (BL31) */
"2 MiB" please. Ditto for the to-be-refactored 16 MiB node.
> + secmon: secmon {
> + reg = <0x0 0x10000000 0x0 0x200000>;
> + no-map;
> + };
> + };
> +
> cpus {
> #address-cells = <0x2>;
> #size-cells = <0x0>;
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
prev parent reply other threads:[~2017-01-18 0:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 10:10 [PATCH v4] ARM64: dts: meson-gx: Add reserved memory zone and usable memory range Neil Armstrong
2017-01-13 20:03 ` Kevin Hilman
2017-01-15 14:43 ` Andreas Färber
2017-01-16 10:39 ` Neil Armstrong
2017-01-16 15:06 ` Andreas Färber
2017-01-17 6:07 ` Olof Johansson
2017-01-17 8:21 ` Neil Armstrong
2017-01-18 0:00 ` Andreas Färber
2017-01-18 0:27 ` Andreas Färber
2017-01-18 10:58 ` Neil Armstrong
2017-01-18 10:57 ` Neil Armstrong
2017-01-18 19:54 ` Kevin Hilman
2017-01-18 0:09 ` Andreas Färber [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=635fece7-4edf-13b4-3de1-e093abae655f@suse.de \
--to=afaerber@suse.de \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=xypron.glpk@gmx.de \
/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).