aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/rtc/Kconfig
diff options
context:
space:
mode:
Diffstat (limited to 'drivers/rtc/Kconfig')
-rw-r--r--drivers/rtc/Kconfig72
1 files changed, 70 insertions, 2 deletions
diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
index 923a9da9c829..e6ab071fb6fd 100644
--- a/drivers/rtc/Kconfig
+++ b/drivers/rtc/Kconfig
@@ -20,14 +20,24 @@ if RTC_CLASS
20config RTC_HCTOSYS 20config RTC_HCTOSYS
21 bool "Set system time from RTC on startup and resume" 21 bool "Set system time from RTC on startup and resume"
22 default y 22 default y
23 depends on !ALWAYS_USE_PERSISTENT_CLOCK
23 help 24 help
24 If you say yes here, the system time (wall clock) will be set using 25 If you say yes here, the system time (wall clock) will be set using
25 the value read from a specified RTC device. This is useful to avoid 26 the value read from a specified RTC device. This is useful to avoid
26 unnecessary fsck runs at boot time, and to network better. 27 unnecessary fsck runs at boot time, and to network better.
27 28
29config RTC_SYSTOHC
30 bool "Set the RTC time based on NTP synchronization"
31 default y
32 depends on !ALWAYS_USE_PERSISTENT_CLOCK
33 help
34 If you say yes here, the system time (wall clock) will be stored
35 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
36 minutes if userspace reports synchronized NTP status.
37
28config RTC_HCTOSYS_DEVICE 38config RTC_HCTOSYS_DEVICE
29 string "RTC used to set the system time" 39 string "RTC used to set the system time"
30 depends on RTC_HCTOSYS = y 40 depends on RTC_HCTOSYS = y || RTC_SYSTOHC = y
31 default "rtc0" 41 default "rtc0"
32 help 42 help
33 The RTC device that will be used to (re)initialize the system 43 The RTC device that will be used to (re)initialize the system
@@ -194,6 +204,12 @@ config RTC_DRV_DS3232
194 This driver can also be built as a module. If so, the module 204 This driver can also be built as a module. If so, the module
195 will be called rtc-ds3232. 205 will be called rtc-ds3232.
196 206
207config RTC_DRV_LP8788
208 tristate "TI LP8788 RTC driver"
209 depends on MFD_LP8788
210 help
211 Say Y to enable support for the LP8788 RTC/ALARM driver.
212
197config RTC_DRV_MAX6900 213config RTC_DRV_MAX6900
198 tristate "Maxim MAX6900" 214 tristate "Maxim MAX6900"
199 help 215 help
@@ -233,6 +249,26 @@ config RTC_DRV_MAX8998
233 This driver can also be built as a module. If so, the module 249 This driver can also be built as a module. If so, the module
234 will be called rtc-max8998. 250 will be called rtc-max8998.
235 251
252config RTC_DRV_MAX8997
253 tristate "Maxim MAX8997"
254 depends on MFD_MAX8997
255 help
256 If you say yes here you will get support for the
257 RTC of Maxim MAX8997 PMIC.
258
259 This driver can also be built as a module. If so, the module
260 will be called rtc-max8997.
261
262config RTC_DRV_MAX77686
263 tristate "Maxim MAX77686"
264 depends on MFD_MAX77686
265 help
266 If you say yes here you will get support for the
267 RTC of Maxim MAX77686 PMIC.
268
269 This driver can also be built as a module. If so, the module
270 will be called rtc-max77686.
271
236config RTC_DRV_RS5C372 272config RTC_DRV_RS5C372
237 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A" 273 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
238 help 274 help
@@ -370,6 +406,14 @@ config RTC_DRV_TPS65910
370 This driver can also be built as a module. If so, the module 406 This driver can also be built as a module. If so, the module
371 will be called rtc-tps65910. 407 will be called rtc-tps65910.
372 408
409config RTC_DRV_TPS80031
410 tristate "TI TPS80031/TPS80032 RTC driver"
411 depends on MFD_TPS80031
412 help
413 TI Power Managment IC TPS80031 supports RTC functionality
414 along with alarm. This driver supports the RTC driver for
415 the TPS80031 RTC module.
416
373config RTC_DRV_RC5T583 417config RTC_DRV_RC5T583
374 tristate "RICOH 5T583 RTC driver" 418 tristate "RICOH 5T583 RTC driver"
375 depends on MFD_RC5T583 419 depends on MFD_RC5T583
@@ -527,6 +571,14 @@ config RTC_DRV_PCF2123
527 This driver can also be built as a module. If so, the module 571 This driver can also be built as a module. If so, the module
528 will be called rtc-pcf2123. 572 will be called rtc-pcf2123.
529 573
574config RTC_DRV_RX4581
575 tristate "Epson RX-4581"
576 help
577 If you say yes here you will get support for the Epson RX-4581.
578
579 This driver can also be built as a module. If so the module
580 will be called rtc-rx4581.
581
530endif # SPI_MASTER 582endif # SPI_MASTER
531 583
532comment "Platform RTC drivers" 584comment "Platform RTC drivers"
@@ -1023,7 +1075,7 @@ config RTC_DRV_TX4939
1023 1075
1024config RTC_DRV_MV 1076config RTC_DRV_MV
1025 tristate "Marvell SoC RTC" 1077 tristate "Marvell SoC RTC"
1026 depends on ARCH_KIRKWOOD || ARCH_DOVE 1078 depends on ARCH_KIRKWOOD || ARCH_DOVE || ARCH_MVEBU
1027 help 1079 help
1028 If you say yes here you will get support for the in-chip RTC 1080 If you say yes here you will get support for the in-chip RTC
1029 that can be found in some of Marvell's SoC devices, such as 1081 that can be found in some of Marvell's SoC devices, such as
@@ -1173,4 +1225,20 @@ config RTC_DRV_SNVS
1173 This driver can also be built as a module, if so, the module 1225 This driver can also be built as a module, if so, the module
1174 will be called "rtc-snvs". 1226 will be called "rtc-snvs".
1175 1227
1228comment "HID Sensor RTC drivers"
1229
1230config RTC_DRV_HID_SENSOR_TIME
1231 tristate "HID Sensor Time"
1232 depends on USB_HID
1233 select IIO
1234 select HID_SENSOR_HUB
1235 select HID_SENSOR_IIO_COMMON
1236 help
1237 Say yes here to build support for the HID Sensors of type Time.
1238 This drivers makes such sensors available as RTCs.
1239
1240 If this driver is compiled as a module, it will be named
1241 rtc-hid-sensor-time.
1242
1243
1176endif # RTC_CLASS 1244endif # RTC_CLASS