Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1640805 > unrolled thread
| Started by | Rob Herring <robh@kernel.org> |
|---|---|
| First post | 2017-05-13 02:00 +0200 |
| Last post | 2017-05-20 02:10 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH] dt-bindings: Document optional "reserved-names" property Rob Herring <robh@kernel.org> - 2017-05-13 02:00 +0200
Re: [PATCH] dt-bindings: Document optional "reserved-names" property Florian Fainelli <f.fainelli@gmail.com> - 2017-05-20 02:10 +0200
| From | Rob Herring <robh@kernel.org> |
|---|---|
| Date | 2017-05-13 02:00 +0200 |
| Subject | Re: [PATCH] dt-bindings: Document optional "reserved-names" property |
| Message-ID | <tGsDw-3R4-5@gated-at.bofh.it> |
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@gmail.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
[toc] | [next] | [standalone]
| From | Florian Fainelli <f.fainelli@gmail.com> |
|---|---|
| Date | 2017-05-20 02:10 +0200 |
| Message-ID | <tJ081-1wI-9@gated-at.bofh.it> |
| In reply to | #1640805 |
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@gmail.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? Sounds like you are right, compatible is good enough, thanks -- Florian
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web