David Brownell 1d0b19c9a0 i2c: Guard against oopses from bad init sequences ... Guard I2C against oopsing because of init sequence problems, by verifying that i2c_init() has been called before calling any routines that rely on that initialization. This specific test just requires that bus_register(&i2c_bus_type) was called. Examples of this kind of oopsing come from subystems and drivers which register I2C drivers in their subsys_initcall code but which are statically linked before I2C by drivers/Makefile. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Jean Delvare <khali@linux-fr.org>		2008-10-14 17:30:05 +02:00
..
algos	i2c: Let users select algorithm drivers manually again	2008-08-10 22:56:15 +02:00
busses	i2c-parport-light: Don't register a platform device resource	2008-10-14 17:30:04 +02:00
chips	i2c/tps65010: Vibrator hookup to gpiolib	2008-10-14 17:30:04 +02:00
i2c-boardinfo.c
i2c-core.c	i2c: Guard against oopses from bad init sequences	2008-10-14 17:30:05 +02:00
i2c-core.h
i2c-dev.c	i2c-dev: Return correct error code on class_create() failure	2008-09-24 13:39:21 +02:00
Kconfig	i2c: Let users select algorithm drivers manually again	2008-08-10 22:56:15 +02:00
Makefile