From: Grant Likely <grant.likely@arm.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Ard Biesheuvel <ardb@kernel.org>, nd <nd@arm.com>
Subject: Re: [PATCH 1/1] of: properties of reserved-memory nodes
Date: Thu, 10 Sep 2020 17:49:35 +0100 [thread overview]
Message-ID: <c163b528-cf26-7733-c4c6-471bfd84cc43@arm.com> (raw)
In-Reply-To: <20200910162020.3927-1-xypron.glpk@gmx.de>
On 10/09/2020 17:20, Heinrich Schuchardt wrote:
> The reusable and the no-map property are mutually exclusive.
> Clarify this in the documentation.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Acked-by: Grant Likely <grant.likely@arm.com>
> ---
> .../devicetree/bindings/reserved-memory/reserved-memory.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt b/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
> index bac4afa3b197..eb987203548f 100644
> --- a/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
> +++ b/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
> @@ -64,6 +64,9 @@ reusable (optional) - empty property
> system can use that region to store volatile or cached data that
> can be otherwise regenerated or migrated elsewhere.
>
> +A node must not carry both the no-map and the reusable property as these are
> +logically contradictory.
> +
> Linux implementation note:
> - If a "linux,cma-default" property is present, then Linux will use the
> region for the default pool of the contiguous memory allocator.
> --
> 2.28.0
>
next prev parent reply other threads:[~2020-09-10 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 16:20 [PATCH 1/1] of: properties of reserved-memory nodes Heinrich Schuchardt
2020-09-10 16:49 ` Grant Likely [this message]
2020-09-15 20:26 ` Rob Herring
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=c163b528-cf26-7733-c4c6-471bfd84cc43@arm.com \
--to=grant.likely@arm.com \
--cc=ardb@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nd@arm.com \
--cc=robh+dt@kernel.org \
--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).