On Monday 09 June 2008, Ryan Mallon wrote: > > > > Talk to i2c and framebuffer people about changing the link order. > > > > i2c should really be initialised before framebuffer devices because > > framebuffer devices tend to want to read DDC from monitors, which is > > basically a I2C EEPROM in the monitor. > > > > ... but there's probably some reason why it's done the way it is today, > > and changing it could well cause stuff to break. > > We have made i2c the first driver subsystem to come up in our 2.6.20 > kernel since we use i2c io expanders for power domain control. All we > did was change drivers/Makefile so that obj-$(CONFIG_I2C) += i2c/ is at > the very top of the file. We didn't have any problems with doing this. > YMMV of course.
OMAP does much the same thing, for the same reason, and the I2C adapter gets initialized earlier too (so power management chips will be fully usable before driver_initcall code runs). Unless there's a downside on x86, I'd just suggest someone submit a patch moving I2C init "early" so it merges in 2.6.27 ... cc to LKML to scare out more potential problems, but I have a hard time imagining there'd really be any. - Dave _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
