aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/rtc
diff options
context:
space:
mode:
Diffstat (limited to 'drivers/rtc')
-rw-r--r--drivers/rtc/Kconfig52
1 files changed, 26 insertions, 26 deletions
diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
index fe1d7a2c27e4..92c2db64de9c 100644
--- a/drivers/rtc/Kconfig
+++ b/drivers/rtc/Kconfig
@@ -35,8 +35,8 @@ config RTC_HCTOSYS_DEVICE
35 default "rtc0" 35 default "rtc0"
36 help 36 help
37 The RTC device that will be used to (re)initialize the system 37 The RTC device that will be used to (re)initialize the system
38 clock, usually rtc0. Initialization is done when 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 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 40 device should record time in UTC, since the kernel won't do
41 timezone correction. 41 timezone correction.
42 42
@@ -44,7 +44,7 @@ config RTC_HCTOSYS_DEVICE
44 functions run, so it must usually be statically linked. 44 functions run, so it must usually be statically linked.
45 45
46 This clock should be battery-backed, so that it reads the correct 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 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). 48 system will need an external clock source (like an NTP server).
49 49
50 If the clock you specify here is not battery backed, it may still 50 If the clock you specify here is not battery backed, it may still
@@ -69,8 +69,7 @@ config RTC_INTF_SYSFS
69 Say yes here if you want to use your RTCs using sysfs interfaces, 69 Say yes here if you want to use your RTCs using sysfs interfaces,
70 /sys/class/rtc/rtc0 through /sys/.../rtcN. 70 /sys/class/rtc/rtc0 through /sys/.../rtcN.
71 71
72 This driver can also be built as a module. If so, the module 72 If unsure, say Y.
73 will be called rtc-sysfs.
74 73
75config RTC_INTF_PROC 74config RTC_INTF_PROC
76 boolean "/proc/driver/rtc (procfs for rtc0)" 75 boolean "/proc/driver/rtc (procfs for rtc0)"
@@ -78,11 +77,10 @@ config RTC_INTF_PROC
78 default RTC_CLASS 77 default RTC_CLASS
79 help 78 help
80 Say yes here if you want to use your first RTC through the proc 79 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 80 interface, /proc/driver/rtc. Other RTCs will not be available
82 through that API. 81 through that API.
83 82
84 This driver can also be built as a module. If so, the module 83 If unsure, say Y.
85 will be called rtc-proc.
86 84
87config RTC_INTF_DEV 85config RTC_INTF_DEV
88 boolean "/dev/rtcN (character devices)" 86 boolean "/dev/rtcN (character devices)"
@@ -90,12 +88,14 @@ config RTC_INTF_DEV
90 help 88 help
91 Say yes here if you want to use your RTCs using the /dev 89 Say yes here if you want to use your RTCs using the /dev
92 interfaces, which "udev" sets up as /dev/rtc0 through 90 interfaces, which "udev" sets up as /dev/rtc0 through
93 /dev/rtcN. You may want to set up a symbolic link so one 91 /dev/rtcN.
94 of these can be accessed as /dev/rtc, which is a name
95 expected by "hwclock" and some other programs.
96 92
97 This driver can also be built as a module. If so, the module 93 You may want to set up a symbolic link so one of these
98 will be called rtc-dev. 94 can be accessed as /dev/rtc, which is a name
95 expected by "hwclock" and some other programs. Recent
96 versions of "udev" are known to set up the symlink for you.
97
98 If unsure, say Y.
99 99
100config RTC_INTF_DEV_UIE_EMUL 100config RTC_INTF_DEV_UIE_EMUL
101 bool "RTC UIE emulation on dev interface" 101 bool "RTC UIE emulation on dev interface"
@@ -132,14 +132,14 @@ config RTC_DRV_DS1307
132 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00" 132 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00"
133 help 133 help
134 If you say yes here you get support for various compatible RTC 134 If you say yes here you get support for various compatible RTC
135 chips (often with battery backup) connected with I2C. This driver 135 chips (often with battery backup) connected with I2C. This driver
136 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00, 136 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
137 and probably other chips. In some cases the RTC must already 137 and probably other chips. In some cases the RTC must already
138 have been initialized (by manufacturing or a bootloader). 138 have been initialized (by manufacturing or a bootloader).
139 139
140 The first seven registers on these chips hold an RTC, and other 140 The first seven registers on these chips hold an RTC, and other
141 registers may add features such as NVRAM, a trickle charger for 141 registers may add features such as NVRAM, a trickle charger for
142 the RTC/NVRAM backup power, and alarms. NVRAM is visible in 142 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
143 sysfs, but other chip features may not be available. 143 sysfs, but other chip features may not be available.
144 144
145 This driver can also be built as a module. If so, the module 145 This driver can also be built as a module. If so, the module
@@ -150,10 +150,10 @@ config RTC_DRV_DS1374
150 depends on RTC_CLASS && I2C 150 depends on RTC_CLASS && I2C
151 help 151 help
152 If you say yes here you get support for Dallas Semiconductor 152 If you say yes here you get support for Dallas Semiconductor
153 DS1374 real-time clock chips. If an interrupt is associated 153 DS1374 real-time clock chips. If an interrupt is associated
154 with the device, the alarm functionality is supported. 154 with the device, the alarm functionality is supported.
155 155
156 This driver can also be built as a module. If so, the module 156 This driver can also be built as a module. If so, the module
157 will be called rtc-ds1374. 157 will be called rtc-ds1374.
158 158
159config RTC_DRV_DS1672 159config RTC_DRV_DS1672
@@ -247,7 +247,7 @@ config RTC_DRV_TWL92330
247 help 247 help
248 If you say yes here you get support for the RTC on the 248 If you say yes here you get support for the RTC on the
249 TWL92330 "Menelaus" power management chip, used with OMAP2 249 TWL92330 "Menelaus" power management chip, used with OMAP2
250 platforms. The support is integrated with the rest of 250 platforms. The support is integrated with the rest of
251 the Menelaus driver; it's not separate module. 251 the Menelaus driver; it's not separate module.
252 252
253config RTC_DRV_TWL4030 253config RTC_DRV_TWL4030
@@ -308,7 +308,7 @@ config RTC_DRV_DS1305
308 tristate "Dallas/Maxim DS1305/DS1306" 308 tristate "Dallas/Maxim DS1305/DS1306"
309 help 309 help
310 Select this driver to get support for the Dallas/Maxim DS1305 310 Select this driver to get support for the Dallas/Maxim DS1305
311 and DS1306 real time clock chips. These support a trickle 311 and DS1306 real time clock chips. These support a trickle
312 charger, alarms, and NVRAM in addition to the clock. 312 charger, alarms, and NVRAM in addition to the clock.
313 313
314 This driver can also be built as a module. If so, the module 314 This driver can also be built as a module. If so, the module
@@ -382,7 +382,7 @@ config RTC_DRV_CMOS
382 or LPC bus chips, and so on. 382 or LPC bus chips, and so on.
383 383
384 Your system will need to define the platform device used by 384 Your system will need to define the platform device used by
385 this driver, otherwise it won't be accessible. This means 385 this driver, otherwise it won't be accessible. This means
386 you can safely enable this driver if you don't know whether 386 you can safely enable this driver if you don't know whether
387 or not your board has this kind of hardware. 387 or not your board has this kind of hardware.
388 388
@@ -599,7 +599,7 @@ config RTC_DRV_AT91RM9200
599 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL 599 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
600 help 600 help
601 Driver for the internal RTC (Realtime Clock) module found on 601 Driver for the internal RTC (Realtime Clock) module found on
602 Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips 602 Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips
603 this is powered by the backup power supply. 603 this is powered by the backup power supply.
604 604
605config RTC_DRV_AT91SAM9 605config RTC_DRV_AT91SAM9
@@ -621,8 +621,8 @@ config RTC_DRV_AT91SAM9_RTT
621 prompt "RTT module Number" if ARCH_AT91SAM9263 621 prompt "RTT module Number" if ARCH_AT91SAM9263
622 depends on RTC_DRV_AT91SAM9 622 depends on RTC_DRV_AT91SAM9
623 help 623 help
624 More than one RTT module is available. You can choose which 624 More than one RTT module is available. You can choose which
625 one will be used as an RTC. The default of zero is normally 625 one will be used as an RTC. The default of zero is normally
626 OK to use, though some systems use that for non-RTC purposes. 626 OK to use, though some systems use that for non-RTC purposes.
627 627
628config RTC_DRV_AT91SAM9_GPBR 628config RTC_DRV_AT91SAM9_GPBR
@@ -634,8 +634,8 @@ config RTC_DRV_AT91SAM9_GPBR
634 depends on RTC_DRV_AT91SAM9 634 depends on RTC_DRV_AT91SAM9
635 help 635 help
636 The RTC driver needs to use one of the General Purpose Backup 636 The RTC driver needs to use one of the General Purpose Backup
637 Registers (GPBRs) as well as the RTT. You can choose which one 637 Registers (GPBRs) as well as the RTT. You can choose which one
638 will be used. The default of zero is normally OK to use, but 638 will be used. The default of zero is normally OK to use, but
639 on some systems other software needs to use that register. 639 on some systems other software needs to use that register.
640 640
641config RTC_DRV_BFIN 641config RTC_DRV_BFIN