| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # |
| Arthur Othieno | be53f9b | 2006-08-13 23:39:11 +0200 | [diff] [blame] | 2 | # I2C subsystem configuration |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 3 | # |
| 4 | |
| 5 | menu "I2C support" |
| 6 | |
| 7 | config I2C |
| 8 | tristate "I2C support" |
| 9 | ---help--- |
| 10 | I2C (pronounce: I-square-C) is a slow serial bus protocol used in |
| 11 | many micro controller applications and developed by Philips. SMBus, |
| 12 | or System Management Bus is a subset of the I2C protocol. More |
| 13 | information is contained in the directory <file:Documentation/i2c/>, |
| 14 | especially in the file called "summary" there. |
| 15 | |
| 16 | Both I2C and SMBus are supported here. You will need this for |
| 17 | hardware sensors support, and also for Video For Linux support. |
| 18 | |
| 19 | If you want I2C support, you should say Y here and also to the |
| 20 | specific driver for your bus adapter(s) below. |
| 21 | |
| 22 | This I2C support can also be built as a module. If so, the module |
| 23 | will be called i2c-core. |
| 24 | |
| David Brownell | 9c1600e | 2007-05-01 23:26:31 +0200 | [diff] [blame^] | 25 | config I2C_BOARDINFO |
| 26 | boolean |
| 27 | depends on I2C |
| 28 | default y |
| 29 | |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 30 | config I2C_CHARDEV |
| 31 | tristate "I2C device interface" |
| 32 | depends on I2C |
| 33 | help |
| 34 | Say Y here to use i2c-* device files, usually found in the /dev |
| 35 | directory on your system. They make it possible to have user-space |
| 36 | programs use the I2C bus. Information on how to do this is |
| 37 | contained in the file <file:Documentation/i2c/dev-interface>. |
| 38 | |
| 39 | This support is also available as a module. If so, the module |
| 40 | will be called i2c-dev. |
| 41 | |
| 42 | source drivers/i2c/algos/Kconfig |
| 43 | source drivers/i2c/busses/Kconfig |
| 44 | source drivers/i2c/chips/Kconfig |
| 45 | |
| 46 | config I2C_DEBUG_CORE |
| 47 | bool "I2C Core debugging messages" |
| 48 | depends on I2C |
| 49 | help |
| 50 | Say Y here if you want the I2C core to produce a bunch of debug |
| 51 | messages to the system log. Select this if you are having a |
| 52 | problem with I2C support and want to see more of what is going on. |
| 53 | |
| 54 | config I2C_DEBUG_ALGO |
| 55 | bool "I2C Algorithm debugging messages" |
| 56 | depends on I2C |
| 57 | help |
| 58 | Say Y here if you want the I2C algorithm drivers to produce a bunch |
| 59 | of debug messages to the system log. Select this if you are having |
| 60 | a problem with I2C support and want to see more of what is going |
| 61 | on. |
| 62 | |
| 63 | config I2C_DEBUG_BUS |
| 64 | bool "I2C Bus debugging messages" |
| 65 | depends on I2C |
| 66 | help |
| 67 | Say Y here if you want the I2C bus drivers to produce a bunch of |
| 68 | debug messages to the system log. Select this if you are having |
| 69 | a problem with I2C support and want to see more of what is going |
| 70 | on. |
| 71 | |
| 72 | config I2C_DEBUG_CHIP |
| 73 | bool "I2C Chip debugging messages" |
| 74 | depends on I2C |
| 75 | help |
| 76 | Say Y here if you want the I2C chip drivers to produce a bunch of |
| 77 | debug messages to the system log. Select this if you are having |
| 78 | a problem with I2C support and want to see more of what is going |
| 79 | on. |
| 80 | |
| 81 | endmenu |
| 82 | |