From mboxrd@z Thu Jan 1 00:00:00 1970 From: Uli Luckas Subject: Re: Grouping i2c bus drivers Date: Wed, 2 Jul 2008 20:09:23 +0200 Message-ID: <200807022009.23340.u.luckas@road.de> References: <20080627145236.2a20aaad@hyperion.delvare> <4868ADCD.3080305@compulab.co.il> <20080702164207.76304a01@hyperion.delvare> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080702164207.76304a01-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: i2c-bounces-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org Errors-To: i2c-bounces-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org To: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org List-Id: linux-i2c@vger.kernel.org On Wednesday, 2. July 2008, Jean Delvare wrote: > Hi Mike, > > On Mon, 30 Jun 2008 12:56:29 +0300, Mike Rapoport wrote: > > Jean Delvare wrote: > > > Hi all, > > > > > > As was mentioned previously, I have decided to group the i2c bus > > > drivers to make it easier for the users to know what they need (and > > > also for me to know what drivers might be affected by a given problem.) > > > Here is the list I have at the moment. There are still many drivers in > > > the "Other" category. I suspect that many of these should move to the > > > "Embedded" category, but I don't know for sure. So I would welcome > > > comments and suggestions for improvements. > > > > [ snip ] > > > > > obj-$(CONFIG_SCx200_ACB) += scx200_acb.o > > > obj-$(CONFIG_SCx200_I2C) += scx200_i2c.o > > > > SCx200 are Geode GX/LX devices, so I think it also can be moved to > > embedded. > > As far as I know, the Geode uses I2C as a peripheral bus, much like PCs > do, not a system bus as most embedded systems do. So, in the light of > other discussions in this thread, it's probably better to not put these > drivers in the "embedded" category (which might in turn be renamed to > "System I2C host controller drivers (mostly embedded)" or similar.) > I fully agree. Using the embedded classification already lead to confusion in the subthread started by Riku Voipio (See my comment in that subthread) > But honestly I'm not too sure what to do. Grouping by functionality > makes sense for the user, but grouping by bus usage makes more sense if > we end up splitting the bus drivers depending on the time at which they > need to come up. We are talking about source code layout. I am not an expert for Kconfig but I guess we can present the drivers to the user in a completely source tree layout independent fashion. regards, Uli -- ------- ROAD ...the handyPC Company - - - ) ) ) Uli Luckas Software Development ROAD GmbH Bennigsenstr. 14 | 12159 Berlin | Germany fon: +49 (30) 230069 - 64 | fax: +49 (30) 230069 - 69 url: www.road.de Amtsgericht Charlottenburg: HRB 96688 B Managing directors: Hans-Peter Constien, Hubertus von Streit _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c