From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Likely Subject: Re: Device Tree questions WRT MIPS/Octeon SOCs. Date: Fri, 15 Oct 2010 21:45:48 -0600 Message-ID: <20101016034548.GB21170@angua.secretlab.ca> References: <4CB79D93.6090500@caviumnetworks.com> <20101014.191309.515504596.imp@bsdimp.com> <7A9214B0DEB2074FBCA688B30B04400D01B50901@XMB-RCD-208.cisco.com> <4CB89275.8020502@caviumnetworks.com> <7A9214B0DEB2074FBCA688B30B04400D01B50924@XMB-RCD-208.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <7A9214B0DEB2074FBCA688B30B04400D01B50924-2KNrN6/GZtCQwNoRDPPJJaBKnGwkPULj@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: "David VomLehn (dvomlehn)" Cc: prasun.kapoor-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org, linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org, devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org, David Daney List-Id: devicetree@vger.kernel.org [reorganized quoting] On Fri, Oct 15, 2010 at 12:48:55PM -0500, David VomLehn (dvomlehn) wrote: > > David Daney wrote: > > On 10/15/2010 10:30 AM, David VomLehn (dvomlehn) wrote: > > > > > If this is really a question of needing to dynamically generate the > > > device tree, then you have no choice. It's worth mentioning, though, > > > that the device tree compiler (dtc) does have the ability to include > > > files, making it easier to create and maintain device trees that are > > > static but which share devices. > > > > Some experimentation will be necessary. We will have to patch in some > > properties like the Ethernet MAC address as that is stored in a > > separate eeprom. Also some boards have pluggable I/O modules, so we > > may not know at dtb generation time what is there. If it touches firmware, then you'll need to be careful about getting painted into a corner with an over-complex boot firmware design, but yet this sounds like an appropriate approach. > We're in much the same situation. Almost all of the device tree is > static, but we add on/overwrite little bits. I'm not the device tree > expert, but if I understand correctly, you can even have dtc emit labels > that you can reference to make the fix-up simpler. The labels are not available at runtime, but properties in the 'aliases' node can (and should) be used to avoid having to depend on the full path to a device node. It has been on my to-do list for a while to add automatic parsing of aliases when finding a node by full path. g.