]> bbs.cooldavid.org Git - net-next-2.6.git/blame - drivers/i2c/Kconfig
i2c: Separate Kconfig option for i2c-smbus
[net-next-2.6.git] / drivers / i2c / Kconfig
CommitLineData
1da177e4 1#
be53f9b2 2# I2C subsystem configuration
1da177e4
LT
3#
4
16538e6b 5menuconfig I2C
1da177e4 6 tristate "I2C support"
e25df120 7 depends on HAS_IOMEM
194684e5 8 select RT_MUTEXES
1da177e4
LT
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
16538e6b
JE
25if I2C
26
9c1600ed
DB
27config I2C_BOARDINFO
28 boolean
9c1600ed
DB
29 default y
30
2bb5095a
JD
31config I2C_COMPAT
32 boolean "Enable compatibility bits for old user-space"
33 default y
34 help
35 Say Y here if you intend to run lm-sensors 3.1.1 or older, or any
36 other user-space package which expects i2c adapters to be class
37 devices. If you don't know, say Y.
38
1da177e4
LT
39config I2C_CHARDEV
40 tristate "I2C device interface"
1da177e4
LT
41 help
42 Say Y here to use i2c-* device files, usually found in the /dev
43 directory on your system. They make it possible to have user-space
44 programs use the I2C bus. Information on how to do this is
45 contained in the file <file:Documentation/i2c/dev-interface>.
46
47 This support is also available as a module. If so, the module
48 will be called i2c-dev.
49
8d24f8dc
JD
50config I2C_HELPER_AUTO
51 bool "Autoselect pertinent helper modules"
52 default y
53 help
54 Some I2C bus drivers require so-called "I2C algorithm" modules
55 to work. These are basically software-only abstractions of generic
56 I2C interfaces. This option will autoselect them so that you don't
57 have to care.
58
59 Unselect this only if you need to enable additional helper
60 modules, for example for use with external I2C bus drivers.
61
62 In doubt, say Y.
63
e2ca3074
JD
64config I2C_SMBUS
65 tristate "SMBus-specific protocols" if !I2C_HELPER_AUTO
66 help
67 Say Y here if you want support for SMBus extensions to the I2C
68 specification. At the moment, the only supported extension is
69 the SMBus alert protocol.
70
71 This support is also available as a module. If so, the module
72 will be called i2c-smbus.
73
1da177e4
LT
74source drivers/i2c/algos/Kconfig
75source drivers/i2c/busses/Kconfig
76source drivers/i2c/chips/Kconfig
77
78config I2C_DEBUG_CORE
79 bool "I2C Core debugging messages"
1da177e4
LT
80 help
81 Say Y here if you want the I2C core to produce a bunch of debug
82 messages to the system log. Select this if you are having a
83 problem with I2C support and want to see more of what is going on.
84
85config I2C_DEBUG_ALGO
86 bool "I2C Algorithm debugging messages"
1da177e4
LT
87 help
88 Say Y here if you want the I2C algorithm drivers to produce a bunch
89 of debug messages to the system log. Select this if you are having
90 a problem with I2C support and want to see more of what is going
91 on.
92
93config I2C_DEBUG_BUS
94 bool "I2C Bus debugging messages"
1da177e4
LT
95 help
96 Say Y here if you want the I2C bus drivers to produce a bunch of
97 debug messages to the system log. Select this if you are having
98 a problem with I2C support and want to see more of what is going
99 on.
100
101config I2C_DEBUG_CHIP
102 bool "I2C Chip debugging messages"
1da177e4
LT
103 help
104 Say Y here if you want the I2C chip drivers to produce a bunch of
105 debug messages to the system log. Select this if you are having
106 a problem with I2C support and want to see more of what is going
107 on.
108
16538e6b 109endif # I2C