From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from e23smtp01.au.ibm.com (E23SMTP01.au.ibm.com [202.81.18.162]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "e23smtp01.au.ibm.com", Issuer "Equifax" (verified OK)) by ozlabs.org (Postfix) with ESMTP id 14FCADDF78 for ; Thu, 11 Oct 2007 14:25:17 +1000 (EST) Received: from d23relay03.au.ibm.com (d23relay03.au.ibm.com [202.81.18.234]) by e23smtp01.au.ibm.com (8.13.1/8.13.1) with ESMTP id l9B4PQPm017479 for ; Thu, 11 Oct 2007 14:25:26 +1000 Received: from d23av01.au.ibm.com (d23av01.au.ibm.com [9.190.234.96]) by d23relay03.au.ibm.com (8.13.8/8.13.8/NCO v8.5) with ESMTP id l9B4PGgP4817064 for ; Thu, 11 Oct 2007 14:25:16 +1000 Received: from d23av01.au.ibm.com (loopback [127.0.0.1]) by d23av01.au.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l9B4MN5A005760 for ; Thu, 11 Oct 2007 14:22:23 +1000 Date: Thu, 11 Oct 2007 14:24:41 +1000 From: David Gibson To: Grant Likely Subject: Re: [PATCH] Device tree bindings for Xilinx devices Message-ID: <20071011042441.GG14873@localhost.localdomain> References: <20071008075127.9887.38702.stgit@trillian.cg.shawcable.net> <1192048682.5534.92.camel@localhost.localdomain> <20071011013817.GB14873@localhost.localdomain> <20071011040622.GE14873@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Oct 10, 2007 at 10:18:50PM -0600, Grant Likely wrote: > On 10/10/07, David Gibson wrote: > > On Wed, Oct 10, 2007 at 08:25:36PM -0600, Grant Likely wrote: > > > On 10/10/07, David Gibson wrote: > > > > We've used 'cell-index' for similar purposes on other 4xx. > > > > > > Unfortunately, 'cell' has been used in the sense of a logic cell in an > > > SoC. In the case of the SystemACE, it is an external chip. > > > > > > What about "device-number"? > > > > Ok, I misunderstood. If it's not on chip, what significance does this > > serial number have? Where would a driver need it? > > If there were 2 systemace devices on board; one attached to a CF slot > labeled "1" and the other to one labeled "2". :-) Same problem as > lining up serial device files to physical port numbers. > > The driver doesn't technically need it, but the information does need > to flow through to the creation of logically numbered device files. Ah. Then, I'm afraid it doesn't belong in the core binding. Preferably, you should just figure out something without help of this property - plenty of other things have to figure out device names without assistance like this. If you really must you could do this in analogy with the "linux,network-index" property - but this would be, as that is, an ugly hack, and should be recognized as such. Segher's suggestion of using OF-style aliases for this is a fairly good one, actually. I just need to get to implementing it... -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson