blob: f9fae28f5612d8406820f38179e0bcfdf631d399 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
Jean Delvaread2f9312005-07-02 18:15:49 +02002# Miscellaneous I2C chip drivers configuration
Linus Torvalds1da177e2005-04-16 15:20:36 -07003#
4
Jean Delvaread2f9312005-07-02 18:15:49 +02005menu "Miscellaneous I2C Chip support"
Linus Torvalds1da177e2005-04-16 15:20:36 -07006 depends on I2C
7
8config SENSORS_DS1337
Ladislav Michl912b9c02005-05-10 14:08:04 +02009 tristate "Dallas Semiconductor DS1337 and DS1339 Real Time Clock"
Linus Torvalds1da177e2005-04-16 15:20:36 -070010 depends on I2C && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -070011 help
12 If you say yes here you get support for Dallas Semiconductor
Ladislav Michl912b9c02005-05-10 14:08:04 +020013 DS1337 and DS1339 real-time clock chips.
Linus Torvalds1da177e2005-04-16 15:20:36 -070014
15 This driver can also be built as a module. If so, the module
16 will be called ds1337.
17
Randy Vinsonc124a782005-06-03 14:36:06 -070018config SENSORS_DS1374
19 tristate "Maxim/Dallas Semiconductor DS1374 Real Time Clock"
20 depends on I2C && EXPERIMENTAL
Randy Vinsonc124a782005-06-03 14:36:06 -070021 help
22 If you say yes here you get support for Dallas Semiconductor
23 DS1374 real-time clock chips.
24
25 This driver can also be built as a module. If so, the module
26 will be called ds1374.
27
Linus Torvalds1da177e2005-04-16 15:20:36 -070028config SENSORS_EEPROM
29 tristate "EEPROM reader"
30 depends on I2C && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -070031 help
32 If you say yes here you get read-only access to the EEPROM data
33 available on modern memory DIMMs and Sony Vaio laptops. Such
34 EEPROMs could theoretically be available on other devices as well.
35
36 This driver can also be built as a module. If so, the module
37 will be called eeprom.
38
39config SENSORS_PCF8574
40 tristate "Philips PCF8574 and PCF8574A"
41 depends on I2C && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -070042 help
43 If you say yes here you get support for Philips PCF8574 and
44 PCF8574A chips.
45
46 This driver can also be built as a module. If so, the module
47 will be called pcf8574.
48
bgardner@wabtec.com69dd2042005-06-07 08:55:38 -050049config SENSORS_PCA9539
50 tristate "Philips PCA9539 16-bit I/O port"
51 depends on I2C && EXPERIMENTAL
52 help
53 If you say yes here you get support for the Philips PCA9539
54 16-bit I/O port.
55
56 This driver can also be built as a module. If so, the module
57 will be called pca9539.
58
Linus Torvalds1da177e2005-04-16 15:20:36 -070059config SENSORS_PCF8591
60 tristate "Philips PCF8591"
61 depends on I2C && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -070062 help
63 If you say yes here you get support for Philips PCF8591 chips.
64
65 This driver can also be built as a module. If so, the module
66 will be called pcf8591.
67
68config SENSORS_RTC8564
69 tristate "Epson 8564 RTC chip"
70 depends on I2C && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -070071 help
72 If you say yes here you get support for the Epson 8564 RTC chip.
73
74 This driver can also be built as a module. If so, the module
75 will be called i2c-rtc8564.
76
77config ISP1301_OMAP
78 tristate "Philips ISP1301 with OMAP OTG"
79 depends on I2C && ARCH_OMAP_OTG
80 help
81 If you say yes here you get support for the Philips ISP1301
82 USB-On-The-Go transceiver working with the OMAP OTG controller.
83 The ISP1301 is used in products including H2 and H3 development
84 boards for Texas Instruments OMAP processors.
85
86 This driver can also be built as a module. If so, the module
87 will be called isp1301_omap.
88
David Brownell72cd7992005-05-24 17:34:51 -070089# NOTE: This isn't really OMAP-specific, except for the current
90# interface location in <include/asm-arm/arch-omap/tps65010.h>
91# and having mostly OMAP-specific board support
92config TPS65010
93 tristate "TPS6501x Power Management chips"
94 depends on I2C && ARCH_OMAP
95 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
96 help
97 If you say yes here you get support for the TPS6501x series of
98 Power Management chips. These include voltage regulators,
99 lithium ion/polymer battery charging, and other features that
100 are often used in portable devices like cell phones and cameras.
101
102 This driver can also be built as a module. If so, the module
103 will be called tps65010.
104
Linus Torvalds1da177e2005-04-16 15:20:36 -0700105config SENSORS_M41T00
106 tristate "ST M41T00 RTC chip"
107 depends on I2C && PPC32
108 help
109 If you say yes here you get support for the ST M41T00 RTC chip.
110
111 This driver can also be built as a module. If so, the module
112 will be called m41t00.
113
BGardner@Wabtec.comc3bc4ca2005-06-03 13:03:27 -0400114config SENSORS_MAX6875
Jean Delvare2146fec2005-06-23 23:41:39 +0200115 tristate "Maxim MAX6875 Power supply supervisor"
BGardner@Wabtec.comc3bc4ca2005-06-03 13:03:27 -0400116 depends on I2C && EXPERIMENTAL
117 help
Jean Delvare2146fec2005-06-23 23:41:39 +0200118 If you say yes here you get support for the Maxim MAX6875
119 EEPROM-programmable, quad power-supply sequencer/supervisor.
BGardner@Wabtec.comc3bc4ca2005-06-03 13:03:27 -0400120
Jean Delvare2146fec2005-06-23 23:41:39 +0200121 This provides an interface to program the EEPROM and reset the chip.
122
123 This driver also supports the Maxim MAX6874 hex power-supply
124 sequencer/supervisor if found at a compatible address.
BGardner@Wabtec.comc3bc4ca2005-06-03 13:03:27 -0400125
126 This driver can also be built as a module. If so, the module
127 will be called max6875.
128
Alessandro Zummo4d4e5ce2005-10-17 23:04:42 +0200129config RTC_X1205_I2C
130 tristate "Xicor X1205 RTC chip"
131 depends on I2C && EXPERIMENTAL
132 help
133 If you say yes here you get support for the Xicor X1205 RTC chip.
134
135 This driver can also be built as a module. If so, the module
136 will be called x1205.
137
Linus Torvalds1da177e2005-04-16 15:20:36 -0700138endmenu