xref: /linux/drivers/rtc/Kconfig (revision a5766f11cfd3a0c03450d99c8fe548c2940be884)
1#
2# RTC class/drivers configuration
3#
4
5config RTC_LIB
6	tristate
7
8menuconfig RTC_CLASS
9	tristate "Real Time Clock"
10	default n
11	depends on !S390
12	select RTC_LIB
13	help
14	  Generic RTC class support. If you say yes here, you will
15 	  be allowed to plug one or more RTCs to your system. You will
16	  probably want to enable one or more of the interfaces below.
17
18	  This driver can also be built as a module. If so, the module
19	  will be called rtc-core.
20
21if RTC_CLASS
22
23config RTC_HCTOSYS
24	bool "Set system time from RTC on startup and resume"
25	depends on RTC_CLASS = y
26	default y
27	help
28	  If you say yes here, the system time (wall clock) will be set using
29	  the value read from a specified RTC device. This is useful to avoid
30	  unnecessary fsck runs at boot time, and to network better.
31
32config RTC_HCTOSYS_DEVICE
33	string "RTC used to set the system time"
34	depends on RTC_HCTOSYS = y
35	default "rtc0"
36	help
37	  The RTC device that will be used to (re)initialize the system
38	  clock, usually rtc0.  Initialization is done when the system
39	  starts up, and when it resumes from a low power state.  This
40	  device should record time in UTC, since the kernel won't do
41	  timezone correction.
42
43	  The driver for this RTC device must be loaded before late_initcall
44	  functions run, so it must usually be statically linked.
45
46	  This clock should be battery-backed, so that it reads the correct
47	  time when the system boots from a power-off state.  Otherwise, your
48	  system will need an external clock source (like an NTP server).
49
50	  If the clock you specify here is not battery backed, it may still
51	  be useful to reinitialize system time when resuming from system
52	  sleep states. Do not specify an RTC here unless it stays powered
53	  during all this system's supported sleep states.
54
55config RTC_DEBUG
56	bool "RTC debug support"
57	depends on RTC_CLASS = y
58	help
59	  Say yes here to enable debugging support in the RTC framework
60	  and individual RTC drivers.
61
62comment "RTC interfaces"
63
64config RTC_INTF_SYSFS
65	boolean "/sys/class/rtc/rtcN (sysfs)"
66	depends on SYSFS
67	default RTC_CLASS
68	help
69	  Say yes here if you want to use your RTCs using sysfs interfaces,
70	  /sys/class/rtc/rtc0 through /sys/.../rtcN.
71
72	  This driver can also be built as a module. If so, the module
73	  will be called rtc-sysfs.
74
75config RTC_INTF_PROC
76	boolean "/proc/driver/rtc (procfs for rtc0)"
77	depends on PROC_FS
78	default RTC_CLASS
79	help
80	  Say yes here if you want to use your first RTC through the proc
81	  interface, /proc/driver/rtc.  Other RTCs will not be available
82	  through that API.
83
84	  This driver can also be built as a module. If so, the module
85	  will be called rtc-proc.
86
87config RTC_INTF_DEV
88	boolean "/dev/rtcN (character devices)"
89	default RTC_CLASS
90	help
91	  Say yes here if you want to use your RTCs using the /dev
92	  interfaces, which "udev" sets up as /dev/rtc0 through
93	  /dev/rtcN.  You may want to set up a symbolic link so one
94	  of these can be accessed as /dev/rtc, which is a name
95	  expected by "hwclock" and some other programs.
96
97	  This driver can also be built as a module. If so, the module
98	  will be called rtc-dev.
99
100config RTC_INTF_DEV_UIE_EMUL
101	bool "RTC UIE emulation on dev interface"
102	depends on RTC_INTF_DEV
103	help
104	  Provides an emulation for RTC_UIE if the underlying rtc chip
105	  driver does not expose RTC_UIE ioctls.  Those requests generate
106	  once-per-second update interrupts, used for synchronization.
107
108config RTC_DRV_TEST
109	tristate "Test driver/device"
110	help
111	  If you say yes here you get support for the
112	  RTC test driver. It's a software RTC which can be
113	  used to test the RTC subsystem APIs. It gets
114	  the time from the system clock.
115	  You want this driver only if you are doing development
116	  on the RTC subsystem. Please read the source code
117	  for further details.
118
119	  This driver can also be built as a module. If so, the module
120	  will be called rtc-test.
121
122comment "I2C RTC drivers"
123	depends on I2C
124
125if I2C
126
127config RTC_DRV_DS1307
128	tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00"
129	help
130	  If you say yes here you get support for various compatible RTC
131	  chips (often with battery backup) connected with I2C.  This driver
132	  should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
133	  and probably other chips.  In some cases the RTC must already
134	  have been initialized (by manufacturing or a bootloader).
135
136	  The first seven registers on these chips hold an RTC, and other
137	  registers may add features such as NVRAM, a trickle charger for
138	  the RTC/NVRAM backup power, and alarms.  NVRAM is visible in
139	  sysfs, but other chip features may not be available.
140
141	  This driver can also be built as a module. If so, the module
142	  will be called rtc-ds1307.
143
144config RTC_DRV_DS1374
145	tristate "Dallas/Maxim DS1374"
146	depends on RTC_CLASS && I2C
147	help
148	  If you say yes here you get support for Dallas Semiconductor
149	  DS1374 real-time clock chips.  If an interrupt is associated
150	  with the device, the alarm functionality is supported.
151
152	  This driver can also be built as a module.  If so, the module
153	  will be called rtc-ds1374.
154
155config RTC_DRV_DS1672
156	tristate "Dallas/Maxim DS1672"
157	help
158	  If you say yes here you get support for the
159	  Dallas/Maxim DS1672 timekeeping chip.
160
161	  This driver can also be built as a module. If so, the module
162	  will be called rtc-ds1672.
163
164config RTC_DRV_MAX6900
165	tristate "Maxim MAX6900"
166	help
167	  If you say yes here you will get support for the
168	  Maxim MAX6900 I2C RTC chip.
169
170	  This driver can also be built as a module. If so, the module
171	  will be called rtc-max6900.
172
173config RTC_DRV_RS5C372
174	tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A"
175	help
176	  If you say yes here you get support for the
177	  Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
178
179	  This driver can also be built as a module. If so, the module
180	  will be called rtc-rs5c372.
181
182config RTC_DRV_ISL1208
183	tristate "Intersil ISL1208"
184	help
185	  If you say yes here you get support for the
186	  Intersil ISL1208 RTC chip.
187
188	  This driver can also be built as a module. If so, the module
189	  will be called rtc-isl1208.
190
191config RTC_DRV_X1205
192	tristate "Xicor/Intersil X1205"
193	help
194	  If you say yes here you get support for the
195	  Xicor/Intersil X1205 RTC chip.
196
197	  This driver can also be built as a module. If so, the module
198	  will be called rtc-x1205.
199
200config RTC_DRV_PCF8563
201	tristate "Philips PCF8563/Epson RTC8564"
202	help
203	  If you say yes here you get support for the
204	  Philips PCF8563 RTC chip. The Epson RTC8564
205	  should work as well.
206
207	  This driver can also be built as a module. If so, the module
208	  will be called rtc-pcf8563.
209
210config RTC_DRV_PCF8583
211	tristate "Philips PCF8583"
212	help
213	  If you say yes here you get support for the Philips PCF8583
214	  RTC chip found on Acorn RiscPCs. This driver supports the
215	  platform specific method of retrieving the current year from
216	  the RTC's SRAM. It will work on other platforms with the same
217	  chip, but the year will probably have to be tweaked.
218
219	  This driver can also be built as a module. If so, the module
220	  will be called rtc-pcf8583.
221
222config RTC_DRV_M41T80
223	tristate "ST M41T80/81/82/83/84/85/87"
224	help
225	  If you say Y here you will get support for the
226	  ST M41T80 RTC chips series. Currently following chips are
227	  supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85
228	  and M41ST87.
229
230	  This driver can also be built as a module. If so, the module
231	  will be called rtc-m41t80.
232
233config RTC_DRV_M41T80_WDT
234	bool "ST M41T80 series RTC watchdog timer"
235	depends on RTC_DRV_M41T80
236	help
237	  If you say Y here you will get support for the
238	  watchdog timer in ST M41T80 RTC chips series.
239
240config RTC_DRV_TWL92330
241	boolean "TI TWL92330/Menelaus"
242	depends on MENELAUS
243	help
244	  If you say yes here you get support for the RTC on the
245	  TWL92330 "Menelaus" power management chip, used with OMAP2
246	  platforms.  The support is integrated with the rest of
247	  the Menelaus driver; it's not separate module.
248
249config RTC_DRV_S35390A
250	tristate "Seiko Instruments S-35390A"
251	select BITREVERSE
252	help
253	  If you say yes here you will get support for the Seiko
254	  Instruments S-35390A.
255
256	  This driver can also be built as a module. If so the module
257	  will be called rtc-s35390a.
258
259config RTC_DRV_FM3130
260	tristate "Ramtron FM3130"
261	help
262	  If you say Y here you will get support for the
263	  Ramtron FM3130 RTC chips.
264	  Ramtron FM3130 is a chip with two separate devices inside,
265	  RTC clock and FRAM. This driver provides only RTC functionality.
266
267	  This driver can also be built as a module. If so the module
268	  will be called rtc-fm3130.
269
270endif # I2C
271
272comment "SPI RTC drivers"
273
274if SPI_MASTER
275
276config RTC_DRV_M41T94
277	tristate "ST M41T94"
278	help
279	  If you say yes here you will get support for the
280	  ST M41T94 SPI RTC chip.
281
282	  This driver can also be built as a module. If so, the module
283	  will be called rtc-m41t94.
284
285config RTC_DRV_DS1305
286	tristate "Dallas/Maxim DS1305/DS1306"
287	help
288	  Select this driver to get support for the Dallas/Maxim DS1305
289	  and DS1306 real time clock chips.  These support a trickle
290	  charger, alarms, and NVRAM in addition to the clock.
291
292	  This driver can also be built as a module. If so, the module
293	  will be called rtc-ds1305.
294
295config RTC_DRV_MAX6902
296	tristate "Maxim MAX6902"
297	help
298	  If you say yes here you will get support for the
299	  Maxim MAX6902 SPI RTC chip.
300
301	  This driver can also be built as a module. If so, the module
302	  will be called rtc-max6902.
303
304config RTC_DRV_R9701
305	tristate "Epson RTC-9701JE"
306	help
307	  If you say yes here you will get support for the
308	  Epson RTC-9701JE SPI RTC chip.
309
310	  This driver can also be built as a module. If so, the module
311	  will be called rtc-r9701.
312
313config RTC_DRV_RS5C348
314	tristate "Ricoh RS5C348A/B"
315	help
316	  If you say yes here you get support for the
317	  Ricoh RS5C348A and RS5C348B RTC chips.
318
319	  This driver can also be built as a module. If so, the module
320	  will be called rtc-rs5c348.
321
322endif # SPI_MASTER
323
324comment "Platform RTC drivers"
325
326# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
327# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
328# global rtc_lock ... it's not yet just another platform_device.
329
330config RTC_DRV_CMOS
331	tristate "PC-style 'CMOS'"
332	depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
333	default y if X86
334	help
335	  Say "yes" here to get direct support for the real time clock
336	  found in every PC or ACPI-based system, and some other boards.
337	  Specifically the original MC146818, compatibles like those in
338	  PC south bridges, the DS12887 or M48T86, some multifunction
339	  or LPC bus chips, and so on.
340
341	  Your system will need to define the platform device used by
342	  this driver, otherwise it won't be accessible.  This means
343	  you can safely enable this driver if you don't know whether
344	  or not your board has this kind of hardware.
345
346	  This driver can also be built as a module. If so, the module
347	  will be called rtc-cmos.
348
349config RTC_DRV_DS1216
350	tristate "Dallas DS1216"
351	depends on SNI_RM
352	help
353	  If you say yes here you get support for the Dallas DS1216 RTC chips.
354
355config RTC_DRV_DS1302
356	tristate "Dallas DS1302"
357	depends on SH_SECUREEDGE5410
358	help
359	  If you say yes here you get support for the Dallas DS1302 RTC chips.
360
361config RTC_DRV_DS1511
362	tristate "Dallas DS1511"
363	depends on RTC_CLASS
364	help
365	  If you say yes here you get support for the
366	  Dallas DS1511 timekeeping/watchdog chip.
367
368	  This driver can also be built as a module. If so, the module
369	  will be called rtc-ds1511.
370
371config RTC_DRV_DS1553
372	tristate "Maxim/Dallas DS1553"
373	help
374	  If you say yes here you get support for the
375	  Maxim/Dallas DS1553 timekeeping chip.
376
377	  This driver can also be built as a module. If so, the module
378	  will be called rtc-ds1553.
379
380config RTC_DRV_DS1742
381	tristate "Maxim/Dallas DS1742/1743"
382	help
383	  If you say yes here you get support for the
384	  Maxim/Dallas DS1742/1743 timekeeping chip.
385
386	  This driver can also be built as a module. If so, the module
387	  will be called rtc-ds1742.
388
389config RTC_DRV_STK17TA8
390	tristate "Simtek STK17TA8"
391	depends on RTC_CLASS
392	help
393	  If you say yes here you get support for the
394	  Simtek STK17TA8 timekeeping chip.
395
396	  This driver can also be built as a module. If so, the module
397	  will be called rtc-stk17ta8.
398
399config RTC_DRV_M48T86
400	tristate "ST M48T86/Dallas DS12887"
401	help
402	  If you say Y here you will get support for the
403	  ST M48T86 and Dallas DS12887 RTC chips.
404
405	  This driver can also be built as a module. If so, the module
406	  will be called rtc-m48t86.
407
408config RTC_DRV_M48T59
409	tristate "ST M48T59/M48T08/M48T02"
410	help
411	  If you say Y here you will get support for the
412	  ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
413
414	  These chips are usually found in Sun SPARC and UltraSPARC
415	  workstations.
416
417	  This driver can also be built as a module, if so, the module
418	  will be called "rtc-m48t59".
419
420config RTC_DRV_BQ4802
421	tristate "TI BQ4802"
422	help
423	  If you say Y here you will get support for the TI
424	  BQ4802 RTC chip.
425
426	  This driver can also be built as a module. If so, the module
427	  will be called rtc-bq4802.
428
429config RTC_DRV_V3020
430	tristate "EM Microelectronic V3020"
431	help
432	  If you say yes here you will get support for the
433	  EM Microelectronic v3020 RTC chip.
434
435	  This driver can also be built as a module. If so, the module
436	  will be called rtc-v3020.
437
438comment "on-CPU RTC drivers"
439
440config RTC_DRV_OMAP
441	tristate "TI OMAP1"
442	depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730
443	help
444	  Say "yes" here to support the real time clock on TI OMAP1 chips.
445	  This driver can also be built as a module called rtc-omap.
446
447config RTC_DRV_S3C
448	tristate "Samsung S3C series SoC RTC"
449	depends on ARCH_S3C2410
450	help
451	  RTC (Realtime Clock) driver for the clock inbuilt into the
452	  Samsung S3C24XX series of SoCs. This can provide periodic
453	  interrupt rates from 1Hz to 64Hz for user programs, and
454	  wakeup from Alarm.
455
456	  The driver currently supports the common features on all the
457	  S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
458	  and S3C2442.
459
460	  This driver can also be build as a module. If so, the module
461	  will be called rtc-s3c.
462
463config RTC_DRV_EP93XX
464	tristate "Cirrus Logic EP93XX"
465	depends on ARCH_EP93XX
466	help
467	  If you say yes here you get support for the
468	  RTC embedded in the Cirrus Logic EP93XX processors.
469
470	  This driver can also be built as a module. If so, the module
471	  will be called rtc-ep93xx.
472
473config RTC_DRV_SA1100
474	tristate "SA11x0/PXA2xx"
475	depends on ARCH_SA1100 || ARCH_PXA
476	help
477	  If you say Y here you will get access to the real time clock
478	  built into your SA11x0 or PXA2xx CPU.
479
480	  To compile this driver as a module, choose M here: the
481	  module will be called rtc-sa1100.
482
483config RTC_DRV_SH
484	tristate "SuperH On-Chip RTC"
485	depends on RTC_CLASS && SUPERH
486	help
487	  Say Y here to enable support for the on-chip RTC found in
488	  most SuperH processors.
489
490 	  To compile this driver as a module, choose M here: the
491	  module will be called rtc-sh.
492
493config RTC_DRV_VR41XX
494	tristate "NEC VR41XX"
495	depends on CPU_VR41XX
496	help
497	  If you say Y here you will get access to the real time clock
498	  built into your NEC VR41XX CPU.
499
500	  To compile this driver as a module, choose M here: the
501	  module will be called rtc-vr41xx.
502
503config RTC_DRV_PL030
504	tristate "ARM AMBA PL030 RTC"
505	depends on ARM_AMBA
506	help
507	  If you say Y here you will get access to ARM AMBA
508	  PrimeCell PL030 RTC found on certain ARM SOCs.
509
510	  To compile this driver as a module, choose M here: the
511	  module will be called rtc-pl030.
512
513config RTC_DRV_PL031
514	tristate "ARM AMBA PL031 RTC"
515	depends on ARM_AMBA
516	help
517	  If you say Y here you will get access to ARM AMBA
518	  PrimeCell PL031 RTC found on certain ARM SOCs.
519
520	  To compile this driver as a module, choose M here: the
521	  module will be called rtc-pl031.
522
523config RTC_DRV_AT32AP700X
524	tristate "AT32AP700X series RTC"
525	depends on PLATFORM_AT32AP
526	help
527	  Driver for the internal RTC (Realtime Clock) on Atmel AVR32
528	  AT32AP700x family processors.
529
530config RTC_DRV_AT91RM9200
531	tristate "AT91RM9200 or AT91SAM9RL"
532	depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
533	help
534	  Driver for the internal RTC (Realtime Clock) module found on
535	  Atmel AT91RM9200's and AT91SAM9RL chips.  On SAM9RL chips
536	  this is powered by the backup power supply.
537
538config RTC_DRV_AT91SAM9
539	tristate "AT91SAM9x/AT91CAP9"
540	depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
541	help
542	  RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
543	  (Real Time Timer). These timers are powered by the backup power
544	  supply (such as a small coin cell battery), but do not need to
545	  be used as RTCs.
546
547	  (On AT91SAM9rl chips you probably want to use the dedicated RTC
548	  module and leave the RTT available for other uses.)
549
550config RTC_DRV_AT91SAM9_RTT
551	int
552	range 0 1
553	default 0
554	prompt "RTT module Number" if ARCH_AT91SAM9263
555	depends on RTC_DRV_AT91SAM9
556	help
557	  More than one RTT module is available.  You can choose which
558	  one will be used as an RTC.  The default of zero is normally
559	  OK to use, though some systems use that for non-RTC purposes.
560
561config RTC_DRV_AT91SAM9_GPBR
562	int
563	range 0 3 if !ARCH_AT91SAM9263
564	range 0 15 if ARCH_AT91SAM9263
565	default 0
566	prompt "Backup Register Number"
567	depends on RTC_DRV_AT91SAM9
568	help
569	  The RTC driver needs to use one of the General Purpose Backup
570	  Registers (GPBRs) as well as the RTT.  You can choose which one
571	  will be used.  The default of zero is normally OK to use, but
572	  on some systems other software needs to use that register.
573
574config RTC_DRV_BFIN
575	tristate "Blackfin On-Chip RTC"
576	depends on BLACKFIN && !BF561
577	help
578	  If you say yes here you will get support for the
579	  Blackfin On-Chip Real Time Clock.
580
581	  This driver can also be built as a module. If so, the module
582	  will be called rtc-bfin.
583
584config RTC_DRV_RS5C313
585	tristate "Ricoh RS5C313"
586	depends on SH_LANDISK
587	help
588	  If you say yes here you get support for the Ricoh RS5C313 RTC chips.
589
590config RTC_DRV_PPC
591       tristate "PowerPC machine dependent RTC support"
592       depends on PPC_MERGE
593       help
594	 The PowerPC kernel has machine-specific functions for accessing
595	 the RTC. This exposes that functionality through the generic RTC
596	 class.
597
598config RTC_DRV_SUN4V
599	bool "SUN4V Hypervisor RTC"
600	depends on SPARC64
601	help
602	  If you say Y here you will get support for the Hypervisor
603	  based RTC on SUN4V systems.
604
605config RTC_DRV_STARFIRE
606	bool "Starfire RTC"
607	depends on SPARC64
608	help
609	  If you say Y here you will get support for the RTC found on
610	  Starfire systems.
611
612endif # RTC_CLASS
613