On 05/12/2017 04:55 PM, Rob Herring wrote: > 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@xxxxxxxxx> >> --- >> 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? Sounds like you are right, compatible is good enough, thanks -- Florian -- To unsubscribe from this list: send the line "unsubscribe devicetree-spec" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
