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:48:50 -0600 Message-ID: <20101016034850.GC21170@angua.secretlab.ca> References: <4CB79D93.6090500@caviumnetworks.com> <20101014.191309.515504596.imp@bsdimp.com> <7A9214B0DEB2074FBCA688B30B04400D01B50901@XMB-RCD-208.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <7A9214B0DEB2074FBCA688B30B04400D01B50901-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, ddaney-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org List-Id: devicetree@vger.kernel.org On Fri, Oct 15, 2010 at 12:30:48PM -0500, 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. Yes. In fact, John Bonesio is working right now of polishing the last details of this to allow for example a board-level .dts file to include an SoC level .dts and add/remove/modify nodes as needed. Should be sorted out in a week or two. Once that is done then we'll update the copy of dtc in the kernel (probably looking at the 2.6.38 timeframe realistically). g. > = > > -----Original Message----- > > From: linux-mips-bounce-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org [mailto:linux-mips-bounce@linux- > > mips.org] On Behalf Of Grant Likely > > Sent: Thursday, October 14, 2010 6:29 PM > > To: Warner Losh > > Cc: ddaney-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org; prasun.kapoor-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org; linux- > > mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org; devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org > > Subject: Re: Device Tree questions WRT MIPS/Octeon SOCs. > > = > > On Thu, Oct 14, 2010 at 7:13 PM, Warner Losh wrote: > > > In message: > cNh8xACS_KPf_dCst5cgmh5VR-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> > > > =A0 =A0 =A0 =A0 =A0 =A0Grant Likely write= s: > > > : Overall the plan makes sense, however I would suggest the > > following. > > > : instead of 'live' modifying the tree, another option is to carry a > > set > > > : of 'stock' device trees in the kernel; one per board. =A0Of course > > this > > > : assumes that your current ad-hoc code is keying on the specific > > board. > > > : =A0If it is interpreting data provided by the firmware, then your > > > : suggestion of modifying a single stock tree probably makes more > > sense, > > > : or possibly a combination of the too. =A0In general you should avoid > > > : live modification as much as possible. > > > > > > The one draw back on this is that there's lots of different "stock" > > > boards that the Cavium Octeon SDK supports. =A0These will be difficult > > > to drag along for every kernel. =A0And they'd be mostly the same to, > > > which is why I think that David is suggesting the live modification > > > thing... > > = > > Okay. Do what makes the most sense for your platform. > > = > > g. > =