diff options
Diffstat (limited to 'drivers/i2c/Kconfig')
| -rw-r--r-- | drivers/i2c/Kconfig | 77 |
1 files changed, 77 insertions, 0 deletions
diff --git a/drivers/i2c/Kconfig b/drivers/i2c/Kconfig new file mode 100644 index 000000000000..24383afdda76 --- /dev/null +++ b/drivers/i2c/Kconfig | |||
| @@ -0,0 +1,77 @@ | |||
| 1 | # | ||
| 2 | # Character device configuration | ||
| 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 | |||
| 25 | config I2C_CHARDEV | ||
| 26 | tristate "I2C device interface" | ||
| 27 | depends on I2C | ||
| 28 | help | ||
| 29 | Say Y here to use i2c-* device files, usually found in the /dev | ||
| 30 | directory on your system. They make it possible to have user-space | ||
| 31 | programs use the I2C bus. Information on how to do this is | ||
| 32 | contained in the file <file:Documentation/i2c/dev-interface>. | ||
| 33 | |||
| 34 | This support is also available as a module. If so, the module | ||
| 35 | will be called i2c-dev. | ||
| 36 | |||
| 37 | source drivers/i2c/algos/Kconfig | ||
| 38 | source drivers/i2c/busses/Kconfig | ||
| 39 | source drivers/i2c/chips/Kconfig | ||
| 40 | |||
| 41 | config I2C_DEBUG_CORE | ||
| 42 | bool "I2C Core debugging messages" | ||
| 43 | depends on I2C | ||
| 44 | help | ||
| 45 | Say Y here if you want the I2C core to produce a bunch of debug | ||
| 46 | messages to the system log. Select this if you are having a | ||
| 47 | problem with I2C support and want to see more of what is going on. | ||
| 48 | |||
| 49 | config I2C_DEBUG_ALGO | ||
| 50 | bool "I2C Algorithm debugging messages" | ||
| 51 | depends on I2C | ||
| 52 | help | ||
| 53 | Say Y here if you want the I2C algorithm drivers to produce a bunch | ||
| 54 | of debug messages to the system log. Select this if you are having | ||
| 55 | a problem with I2C support and want to see more of what is going | ||
| 56 | on. | ||
| 57 | |||
| 58 | config I2C_DEBUG_BUS | ||
| 59 | bool "I2C Bus debugging messages" | ||
| 60 | depends on I2C | ||
| 61 | help | ||
| 62 | Say Y here if you want the I2C bus drivers to produce a bunch of | ||
| 63 | debug messages to the system log. Select this if you are having | ||
| 64 | a problem with I2C support and want to see more of what is going | ||
| 65 | on. | ||
| 66 | |||
| 67 | config I2C_DEBUG_CHIP | ||
| 68 | bool "I2C Chip debugging messages" | ||
| 69 | depends on I2C | ||
| 70 | help | ||
| 71 | Say Y here if you want the I2C chip drivers to produce a bunch of | ||
| 72 | debug messages to the system log. Select this if you are having | ||
| 73 | a problem with I2C support and want to see more of what is going | ||
| 74 | on. | ||
| 75 | |||
| 76 | endmenu | ||
| 77 | |||