Messages in this thread |  | | Date | Mon, 16 Sep 2013 16:48:47 -0700 | | Subject | Re: "memory" binding issues | | From | Olof Johansson <> |
| |
On Mon, Sep 16, 2013 at 4:47 PM, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote: > On Mon, 2013-09-16 at 15:48 -0700, Olof Johansson wrote: >> > A node that has a "reg" property should have the corresponding unit >> > address. >> >> No, absolutely _NOT_ a requirement. Unit address is only required if >> needed to disambiguate two properties with the same name. >> >> If there are no ambiguities, then leaving off the unit address is much >> preferred. > > I disagree :-)
Well, good thing you've got your own arch to litter the device trees with unit specifiers in then. :)
> Also this would be only true of our find_node_by_path was capable of > handling it, which it isn't. Thus you end up with generic code looking > for /memory and finding nothing ...
Yes, this should be fixed.
-Olof
|  |