From: scottwood@freescale.com (Scott Wood) Date: Tue, 9 Aug 2011 16:52:27 -0500 Subject: How to handle named resources with DT? In-Reply-To: <4E41AA43.1000506@ti.com> References: <4E40FC88.5090403@ti.com> <20110809162907.GA630@manju-WNB7PBC4801-0006> <4E4166F0.9050401@ti.com> <4E4172A8.3030101@ti.com> <4E417BD5.8080409@freescale.com> <20110809205723.GE11568@ponder.secretlab.ca> <4E41A1B9.1060400@ti.com> <20110809211747.GJ11568@ponder.secretlab.ca> <4E41AA43.1000506@ti.com> Message-ID: <4E41AC1B.5040002@freescale.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 08/09/2011 04:44 PM, Cousson, Benoit wrote: > OK, so what about extending the reg attribute to be a reg node? > > dev { > reg { > name = "foo_wrapper"; > start = <0x10000>; > end = <0x200>; > } > reg { > name = "foo"; > start = <0x20000>; > end = <0x200>; > } > } > > A little bit more verbose, but at least we can add any attribute we want. A more standard way to do that would be something like: dev { #address-cells = <1>; #size-cells = <1>; ranges; foo { reg = <0x10000 0x200>; }; bar { reg = <0x20000 0x200>; }; }; ...which is OK if you need the expressiveness of a full hierarchy (and don't have some other meaning for child nodes of "dev"), but it seems like it would be overkill for some places where named resources would be useful. -Scott