Commit | Line | Data |
---|---|---|
0c86edc0 | 1 | \# |
c58411e9 AZ |
2 | # RTC class/drivers configuration |
3 | # | |
4 | ||
0c86edc0 AZ |
5 | menu "Real Time Clock" |
6 | ||
c58411e9 | 7 | config RTC_LIB |
0c86edc0 AZ |
8 | tristate |
9 | ||
10 | config RTC_CLASS | |
11 | tristate "RTC class" | |
12 | depends on EXPERIMENTAL | |
13 | default n | |
14 | select RTC_LIB | |
15 | help | |
16 | Generic RTC class support. If you say yes here, you will | |
17 | be allowed to plug one or more RTCs to your system. You will | |
18 | probably want to enable one of more of the interfaces below. | |
19 | ||
20 | This driver can also be built as a module. If so, the module | |
21 | will be called rtc-class. | |
22 | ||
23 | config RTC_HCTOSYS | |
24 | bool "Set system time from RTC on startup" | |
25 | depends on RTC_CLASS = y | |
26 | default y | |
27 | help | |
28 | If you say yes here, the system time will be set using | |
29 | the value read from the specified RTC device. This is useful | |
30 | in order to avoid unnecessary fschk runs. | |
31 | ||
32 | config RTC_HCTOSYS_DEVICE | |
33 | string "The RTC to read the time from" | |
34 | depends on RTC_HCTOSYS = y | |
35 | default "rtc0" | |
36 | help | |
37 | The RTC device that will be used as the source for | |
38 | the system time, usually rtc0. | |
39 | ||
40 | comment "RTC interfaces" | |
41 | depends on RTC_CLASS | |
42 | ||
c5c3e192 AZ |
43 | config RTC_INTF_SYSFS |
44 | tristate "sysfs" | |
45 | depends on RTC_CLASS && SYSFS | |
46 | default RTC_CLASS | |
47 | help | |
48 | Say yes here if you want to use your RTC using the sysfs | |
49 | interface, /sys/class/rtc/rtcX . | |
50 | ||
51 | This driver can also be built as a module. If so, the module | |
52 | will be called rtc-sysfs. | |
53 | ||
728a2947 AZ |
54 | config RTC_INTF_PROC |
55 | tristate "proc" | |
56 | depends on RTC_CLASS && PROC_FS | |
57 | default RTC_CLASS | |
58 | help | |
59 | Say yes here if you want to use your RTC using the proc | |
60 | interface, /proc/driver/rtc . | |
61 | ||
62 | This driver can also be built as a module. If so, the module | |
63 | will be called rtc-proc. | |
64 | ||
e824290e AZ |
65 | config RTC_INTF_DEV |
66 | tristate "dev" | |
67 | depends on RTC_CLASS | |
68 | default RTC_CLASS | |
69 | help | |
70 | Say yes here if you want to use your RTC using the dev | |
71 | interface, /dev/rtc . | |
72 | ||
73 | This driver can also be built as a module. If so, the module | |
74 | will be called rtc-dev. | |
75 | ||
0c86edc0 AZ |
76 | comment "RTC drivers" |
77 | depends on RTC_CLASS | |
78 | ||
1fec7c66 AZ |
79 | config RTC_DRV_X1205 |
80 | tristate "Xicor/Intersil X1205" | |
81 | depends on RTC_CLASS && I2C | |
82 | help | |
83 | If you say yes here you get support for the | |
84 | Xicor/Intersil X1205 RTC chip. | |
85 | ||
86 | This driver can also be built as a module. If so, the module | |
87 | will be called rtc-x1205. | |
88 | ||
edf1aaa3 AZ |
89 | config RTC_DRV_DS1672 |
90 | tristate "Dallas/Maxim DS1672" | |
91 | depends on RTC_CLASS && I2C | |
92 | help | |
93 | If you say yes here you get support for the | |
94 | Dallas/Maxim DS1672 timekeeping chip. | |
95 | ||
96 | This driver can also be built as a module. If so, the module | |
97 | will be called rtc-ds1672. | |
98 | ||
b5a82d62 AZ |
99 | config RTC_DRV_PCF8563 |
100 | tristate "Philips PCF8563/Epson RTC8564" | |
101 | depends on RTC_CLASS && I2C | |
102 | help | |
103 | If you say yes here you get support for the | |
104 | Philips PCF8563 RTC chip. The Epson RTC8564 | |
105 | should work as well. | |
106 | ||
107 | This driver can also be built as a module. If so, the module | |
108 | will be called rtc-pcf8563. | |
109 | ||
7520b94d AZ |
110 | config RTC_DRV_RS5C372 |
111 | tristate "Ricoh RS5C372A/B" | |
112 | depends on RTC_CLASS && I2C | |
113 | help | |
114 | If you say yes here you get support for the | |
115 | Ricoh RS5C372A and RS5C372B RTC chips. | |
116 | ||
117 | This driver can also be built as a module. If so, the module | |
118 | will be called rtc-rs5c372. | |
119 | ||
1d98af87 AZ |
120 | config RTC_DRV_M48T86 |
121 | tristate "ST M48T86/Dallas DS12887" | |
122 | depends on RTC_CLASS | |
123 | help | |
124 | If you say Y here you will get support for the | |
125 | ST M48T86 and Dallas DS12887 RTC chips. | |
126 | ||
127 | This driver can also be built as a module. If so, the module | |
128 | will be called rtc-m48t86. | |
129 | ||
fd507e2f AZ |
130 | config RTC_DRV_EP93XX |
131 | tristate "Cirrus Logic EP93XX" | |
132 | depends on RTC_CLASS && ARCH_EP93XX | |
133 | help | |
134 | If you say yes here you get support for the | |
135 | RTC embedded in the Cirrus Logic EP93XX processors. | |
136 | ||
137 | This driver can also be built as a module. If so, the module | |
138 | will be called rtc-ep93xx. | |
139 | ||
e842f1c8 RP |
140 | config RTC_DRV_SA1100 |
141 | tristate "SA11x0/PXA2xx" | |
142 | depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA) | |
143 | help | |
144 | If you say Y here you will get access to the real time clock | |
145 | built into your SA11x0 or PXA2xx CPU. | |
146 | ||
147 | To compile this driver as a module, choose M here: the | |
148 | module will be called rtc-sa1100. | |
fd507e2f | 149 | |
8417eb7a | 150 | config RTC_DRV_VR41XX |
3e16f6af | 151 | tristate "NEC VR41XX" |
8417eb7a | 152 | depends on RTC_CLASS && CPU_VR41XX |
3e16f6af AZ |
153 | help |
154 | If you say Y here you will get access to the real time clock | |
155 | built into your NEC VR41XX CPU. | |
156 | ||
157 | To compile this driver as a module, choose M here: the | |
158 | module will be called rtc-vr41xx. | |
8417eb7a | 159 | |
a95579cd AZ |
160 | config RTC_DRV_TEST |
161 | tristate "Test driver/device" | |
162 | depends on RTC_CLASS | |
163 | help | |
164 | If you say yes here you get support for the | |
165 | RTC test driver. It's a software RTC which can be | |
166 | used to test the RTC subsystem APIs. It gets | |
167 | the time from the system clock. | |
168 | You want this driver only if you are doing development | |
169 | on the RTC subsystem. Please read the source code | |
170 | for further details. | |
171 | ||
172 | This driver can also be built as a module. If so, the module | |
173 | will be called rtc-test. | |
174 | ||
0c86edc0 | 175 | endmenu |