From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: In-Reply-To: <20070810010217.GA17370@localhost.localdomain> References: <20070808170728.GA21118@localhost.localdomain> <20070808170921.GA21487@localhost.localdomain> <20070809030752.GB8261@localhost.localdomain> <20070810010217.GA17370@localhost.localdomain> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <5cad6d634a7cb6c8c37adbb15db8dfc2@kernel.crashing.org> From: Segher Boessenkool Subject: Re: [PATCH v3 1/2] [POWERPC] MPC832x_RDB: update dts to use spi, register mmc_spi stub Date: Fri, 10 Aug 2007 22:42:51 +0200 To: David Gibson Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , >>> We should co-ordinate better on this, if it's to become a >>> convention... >> >> That means we shouldn't coordinate on this, right? > > Heh. Either one is kind of ugly, I'll grant you. > > But, many SoCs do have a notion of device "number", which is relevant > for programming other general control registers in places. We need to > encode it somehow, and it would be good to have a consistent way of > doing it. I'm not convinced there isn't a more direct way to represent the relevant relationships. Either way, we don't have enough experience with this stuff yet to know what works well and what doesn't (at least, I don't, and I haven't seen any evidence that others do); so I'd prefer to keep this in per-device bindings for now; it should be there anyhow, but once we do have experience with it we could do some recommendation. Segher