[i2c] Grouping i2c bus drivers

[Jean Delvare]

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.)

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.

-- 
Jean Delvare