summaryrefslogtreecommitdiff
path: root/drivers/i2c/Kconfig
diff options
context:
space:
mode:
authorDavid Brownell <david-b@pacbell.net>2007-05-02 01:26:31 +0400
committerJean Delvare <khali@hyperion.delvare>2007-05-02 01:26:31 +0400
commit9c1600eda42e52796f49b36cf15b9debcfd09bea (patch)
treefe93f5924c7777cd5c3cc1ef6033dd2dfae542b5 /drivers/i2c/Kconfig
parent4298cfc3eb6110df989f784be516c6340c597a66 (diff)
downloadlinux-9c1600eda42e52796f49b36cf15b9debcfd09bea.tar.xz
i2c: Add i2c_board_info and i2c_new_device()
This provides partial support for new-style I2C driver binding. It builds on "struct i2c_board_info" declarations that identify I2C devices on a given board. This is needed on systems with I2C devices that can't be fully probed and/or autoconfigured, such as many embedded Linux configurations where the way a given I2C device is wired may affect how it must be used. There are two models for declaring such devices: * LATE -- using a public function i2c_new_device(). This lets modules declare I2C devices found *AFTER* a given I2C adapter becomes available. For example, a PCI card could create adapters giving access to utility chips on that card, and this would be used to associate those chips with those adapters. * EARLY -- from arch_initcall() level code, using a non-exported function i2c_register_board_info(). This copies the declarations *BEFORE* such an i2c_adapter becomes available, arranging that i2c_new_device() will be called later when i2c-core registers the relevant i2c_adapter. For example, arch/.../.../board-*.c files would declare the I2C devices along with their platform data, and I2C devices would behave much like PNPACPI devices. (That is, both enumerate from board-specific tables.) To match the exported i2c_new_device(), the previously-private function i2c_unregister_device() is now exported. Pending later patches using these new APIs, this is effectively a NOP. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Jean Delvare <khali@linux-fr.org>
Diffstat (limited to 'drivers/i2c/Kconfig')
-rw-r--r--drivers/i2c/Kconfig5
1 files changed, 5 insertions, 0 deletions
diff --git a/drivers/i2c/Kconfig b/drivers/i2c/Kconfig
index 11935f66fcd8..74c8518b69e7 100644
--- a/drivers/i2c/Kconfig
+++ b/drivers/i2c/Kconfig
@@ -22,6 +22,11 @@ config I2C
This I2C support can also be built as a module. If so, the module
will be called i2c-core.
+config I2C_BOARDINFO
+ boolean
+ depends on I2C
+ default y
+
config I2C_CHARDEV
tristate "I2C device interface"
depends on I2C