From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.ebshome.net (gate.ebshome.net [208.106.21.240]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "gate.ebshome.net", Issuer "gate.ebshome.net" (not verified)) by ozlabs.org (Postfix) with ESMTP id 3E32FDDFED for ; Tue, 16 Oct 2007 05:11:24 +1000 (EST) Date: Mon, 15 Oct 2007 12:11:18 -0700 From: Eugene Surovegin To: Scott Wood Subject: Re: [PATCH 2/2] i2c: Add devtree-aware iic support for PPC4xx Message-ID: <20071015191118.GA9733@gate.ebshome.net> References: <200710151529.11485.sr@denx.de> <20071015163216.GA8127@gate.ebshome.net> <20071015185340.GB4474@loki.buserror.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20071015185340.GB4474@loki.buserror.net> Cc: Jean Delvare , Stefan Roese , i2c@lm-sensors.org, linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, Oct 15, 2007 at 01:53:40PM -0500, Scott Wood wrote: > Though, I don't see what the problem with the original approach is, as long > as the numbers are chosen in the same way when registering i2c clients based > on the children of the adapter node. There's no concept in the hardware > itself of a bus number. Huh? As far as I can tell, there is. Also, I want messages from the kernel mention something I can map to the real hw, e.g. fixed IIC device index, not some random number. This already works with the current OCP code, so if you want change it to a "superior" technology, please, make sure it provides the same functionality as trivial OCP one. I find it rather puzzling that instead people are trying to make this a non-issue as soon as it cannot be implemented easily with their new and shiny infrastructure. -- Eugene