From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 21DDDDDEF9 for ; Thu, 23 Oct 2008 15:48:16 +1100 (EST) Subject: Re: [PATCH 4/7] gpiolib: implement dev_gpiochip_{add,remove} calls From: Benjamin Herrenschmidt To: David Brownell In-Reply-To: <200810221404.52798.david-b@pacbell.net> References: <20081016171222.GA24812@oksana.dev.rtsoft.ru> <20081022104606.GA510@oksana.dev.rtsoft.ru> <20081022183218.GA19025@oksana.dev.rtsoft.ru> <200810221404.52798.david-b@pacbell.net> Content-Type: text/plain Date: Thu, 23 Oct 2008 15:45:45 +1100 Message-Id: <1224737145.7654.387.camel@pasglop> Mime-Version: 1.0 Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, i2c@lm-sensors.org, Jean Delvare , David Miller Reply-To: benh@kernel.crashing.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 2008-10-22 at 14:04 -0700, David Brownell wrote: > > So if we register the board infos after > > the controller registered, then nobody will probe the board infos. > > See above. If you're doing it right, there's no problem. > That is, scan the OF tables early. Just like PNP tables > get scanned early, for example. It's still pretty yucky in that case to scan the device-tree to convert it into some kind of fugly board info ... I'd rather have the end drivers that actually use those GPIOs scan the device-tree directly. But then, I'm not a believer in generic drivers for things like GPIOs, i2c devices, etc.. :-) Ben.