Thread (1 message) 1 message, 1 author, 2011-10-19

[RFC] [PATCH] ARM: tegra: emc: device tree bindings

From: Rob Herring <hidden>
Date: 2011-10-19 14:36:42
Also in: linux-devicetree, linux-tegra

Possibly related (same subject, not in this thread)

On 10/18/2011 10:28 PM, Olof Johansson wrote:
On Tue, Oct 18, 2011 at 7:37 PM, Rob Herring [off-list ref] wrote:
quoted
On 10/18/2011 04:01 PM, Stephen Warren wrote:
quoted
I only suggested the well-known-named sub-nodes in order to eliminate
the need for a compatible property.

My inclination is that if we use compatible to distinguish the tables
from anything else, there's little point having the extra level of nodes;
we may as well lay it out as in your original patch, just with an explicit
nvidia,ram-code property in each table (or omitted/ignored when not using
it) instead of reg?
Node names should be generic like serial or ethernet. Compatible is used
to specify the specific model.
In cases where unit addresses can be used to separate out identical
entries, yes. For something like this, there's no logical addressing
of the tables so something else must be used to distinguish them.
Using the frequency as was previously proposed would work assuming that
is unique.

Rob
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help