[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170512235501.ziplwgevcjqyjims@rob-hp-laptop>
Date: Fri, 12 May 2017 18:55:01 -0500
From: Rob Herring <robh@...nel.org>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
mark.rutland@....com, david@...son.dropbear.id.au,
devicetree-spec@...r.kernel.org, glikely@...retlab.ca,
stewart@...ux.vnet.ibm.com
Subject: Re: [PATCH] dt-bindings: Document optional "reserved-names" property
On Tue, May 09, 2017 at 10:18:47AM -0700, Florian Fainelli wrote:
> Define an optional string property: "reserved-names" which can be used
> by the client program to tag/identify reserved memory regions.
>
> Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
> ---
> Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt b/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
> index 3da0ebdba8d9..bd3c9485f637 100644
> --- a/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
> +++ b/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
> @@ -64,6 +64,10 @@ reusable (optional) - empty property
> system can use that region to store volatile or cached data that
> can be otherwise regenerated or migrated elsewhere.
>
> +reserved-names (optional)
> + - Provides a named tag to the client program to help pretty print/identify
> + the reserved memory region.
*-names is normally on the client side. I'd like to keep that
consistent.
Second, I don't see the need for this. The compatible is not enough?
Rob
Powered by blists - more mailing lists