From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.179]) by ozlabs.org (Postfix) with ESMTP id 94A69DDE48 for ; Thu, 5 Apr 2007 03:03:58 +1000 (EST) From: Arnd Bergmann To: linuxppc-dev@ozlabs.org Subject: Re: SPI devices and OF Date: Wed, 4 Apr 2007 19:03:46 +0200 References: <20070404110916.GA9910@localhost.localdomain> <4850DC60-A560-4A38-8416-ADA776B69509@kernel.crashing.org> In-Reply-To: <4850DC60-A560-4A38-8416-ADA776B69509@kernel.crashing.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-Id: <200704041903.46629.arnd@arndb.de> List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wednesday 04 April 2007, Kumar Gala wrote: > I don't think this is a good idea for SPI devices. =A0The effort vs =A0 > reward isn't worth it. =A0The simple fact that the 'chip select' =A0 > mechanism ends up being board specific is too much of a pain to =A0 > figure out how to deal with in the device tree. =A0I think its ok if we = =A0 > put information about the controller in the tree, but trying to do =A0 > the devices as well at this point doesn't seem like its much of a win. >=20 I'm not following your argumentation. If the chip select is board specific, isn't the device tree for that board _exactly_ the place where that information should be? Where else would you get it from? Arnd <><