Kconfig 35 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096109710981099110011011102110311041105110611071108110911101111111211131114111511161117111811191120112111221123112411251126112711281129113011311132113311341135113611371138113911401141114211431144114511461147114811491150115111521153115411551156115711581159116011611162116311641165116611671168116911701171117211731174117511761177117811791180118111821183118411851186118711881189119011911192119311941195119611971198119912001201120212031204120512061207120812091210121112121213121412151216121712181219122012211222122312241225122612271228
  1. #
  2. # RTC class/drivers configuration
  3. #
  4. config RTC_LIB
  5. bool
  6. menuconfig RTC_CLASS
  7. bool "Real Time Clock"
  8. default n
  9. depends on !S390 && !UML
  10. select RTC_LIB
  11. help
  12. Generic RTC class support. If you say yes here, you will
  13. be allowed to plug one or more RTCs to your system. You will
  14. probably want to enable one or more of the interfaces below.
  15. if RTC_CLASS
  16. config RTC_HCTOSYS
  17. bool "Set system time from RTC on startup and resume"
  18. default y
  19. depends on !ALWAYS_USE_PERSISTENT_CLOCK
  20. help
  21. If you say yes here, the system time (wall clock) will be set using
  22. the value read from a specified RTC device. This is useful to avoid
  23. unnecessary fsck runs at boot time, and to network better.
  24. config RTC_SYSTOHC
  25. bool "Set the RTC time based on NTP synchronization"
  26. default y
  27. depends on !ALWAYS_USE_PERSISTENT_CLOCK
  28. help
  29. If you say yes here, the system time (wall clock) will be stored
  30. in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
  31. minutes if userspace reports synchronized NTP status.
  32. config RTC_HCTOSYS_DEVICE
  33. string "RTC used to set the system time"
  34. depends on RTC_HCTOSYS = y || RTC_SYSTOHC = 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. The driver for this RTC device must be loaded before late_initcall
  43. functions run, so it must usually be statically linked.
  44. This clock should be battery-backed, so that it reads the correct
  45. time when the system boots from a power-off state. Otherwise, your
  46. system will need an external clock source (like an NTP server).
  47. If the clock you specify here is not battery backed, it may still
  48. be useful to reinitialize system time when resuming from system
  49. sleep states. Do not specify an RTC here unless it stays powered
  50. during all this system's supported sleep states.
  51. config RTC_DEBUG
  52. bool "RTC debug support"
  53. help
  54. Say yes here to enable debugging support in the RTC framework
  55. and individual RTC drivers.
  56. comment "RTC interfaces"
  57. config RTC_INTF_SYSFS
  58. boolean "/sys/class/rtc/rtcN (sysfs)"
  59. depends on SYSFS
  60. default RTC_CLASS
  61. help
  62. Say yes here if you want to use your RTCs using sysfs interfaces,
  63. /sys/class/rtc/rtc0 through /sys/.../rtcN.
  64. If unsure, say Y.
  65. config RTC_INTF_PROC
  66. boolean "/proc/driver/rtc (procfs for rtcN)"
  67. depends on PROC_FS
  68. default RTC_CLASS
  69. help
  70. Say yes here if you want to use your system clock RTC through
  71. the proc interface, /proc/driver/rtc.
  72. Other RTCs will not be available through that API.
  73. If there is no RTC for the system clock, then the first RTC(rtc0)
  74. is used by default.
  75. If unsure, say Y.
  76. config RTC_INTF_DEV
  77. boolean "/dev/rtcN (character devices)"
  78. default RTC_CLASS
  79. help
  80. Say yes here if you want to use your RTCs using the /dev
  81. interfaces, which "udev" sets up as /dev/rtc0 through
  82. /dev/rtcN.
  83. You may want to set up a symbolic link so one of these
  84. can be accessed as /dev/rtc, which is a name
  85. expected by "hwclock" and some other programs. Recent
  86. versions of "udev" are known to set up the symlink for you.
  87. If unsure, say Y.
  88. config RTC_INTF_DEV_UIE_EMUL
  89. bool "RTC UIE emulation on dev interface"
  90. depends on RTC_INTF_DEV
  91. help
  92. Provides an emulation for RTC_UIE if the underlying rtc chip
  93. driver does not expose RTC_UIE ioctls. Those requests generate
  94. once-per-second update interrupts, used for synchronization.
  95. The emulation code will read the time from the hardware
  96. clock several times per second, please enable this option
  97. only if you know that you really need it.
  98. config RTC_DRV_TEST
  99. tristate "Test driver/device"
  100. help
  101. If you say yes here you get support for the
  102. RTC test driver. It's a software RTC which can be
  103. used to test the RTC subsystem APIs. It gets
  104. the time from the system clock.
  105. You want this driver only if you are doing development
  106. on the RTC subsystem. Please read the source code
  107. for further details.
  108. This driver can also be built as a module. If so, the module
  109. will be called rtc-test.
  110. comment "I2C RTC drivers"
  111. depends on I2C
  112. if I2C
  113. config RTC_DRV_88PM860X
  114. tristate "Marvell 88PM860x"
  115. depends on I2C && MFD_88PM860X
  116. help
  117. If you say yes here you get support for RTC function in Marvell
  118. 88PM860x chips.
  119. This driver can also be built as a module. If so, the module
  120. will be called rtc-88pm860x.
  121. config RTC_DRV_88PM80X
  122. tristate "Marvell 88PM80x"
  123. depends on I2C && MFD_88PM800
  124. help
  125. If you say yes here you get support for RTC function in Marvell
  126. 88PM80x chips.
  127. This driver can also be built as a module. If so, the module
  128. will be called rtc-88pm80x.
  129. config RTC_DRV_DS1307
  130. tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
  131. help
  132. If you say yes here you get support for various compatible RTC
  133. chips (often with battery backup) connected with I2C. This driver
  134. should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
  135. EPSON RX-8025 and probably other chips. In some cases the RTC
  136. must already have been initialized (by manufacturing or a
  137. bootloader).
  138. The first seven registers on these chips hold an RTC, and other
  139. registers may add features such as NVRAM, a trickle charger for
  140. the RTC/NVRAM backup power, and alarms. NVRAM is visible in
  141. sysfs, but other chip features may not be available.
  142. This driver can also be built as a module. If so, the module
  143. will be called rtc-ds1307.
  144. config RTC_DRV_DS1374
  145. tristate "Dallas/Maxim DS1374"
  146. depends on 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. This driver can also be built as a module. If so, the module
  152. will be called rtc-ds1374.
  153. config RTC_DRV_DS1672
  154. tristate "Dallas/Maxim DS1672"
  155. help
  156. If you say yes here you get support for the
  157. Dallas/Maxim DS1672 timekeeping chip.
  158. This driver can also be built as a module. If so, the module
  159. will be called rtc-ds1672.
  160. config RTC_DRV_DS3232
  161. tristate "Dallas/Maxim DS3232"
  162. depends on I2C
  163. help
  164. If you say yes here you get support for Dallas Semiconductor
  165. DS3232 real-time clock chips. If an interrupt is associated
  166. with the device, the alarm functionality is supported.
  167. This driver can also be built as a module. If so, the module
  168. will be called rtc-ds3232.
  169. config RTC_DRV_LP8788
  170. tristate "TI LP8788 RTC driver"
  171. depends on MFD_LP8788
  172. help
  173. Say Y to enable support for the LP8788 RTC/ALARM driver.
  174. config RTC_DRV_MAX6900
  175. tristate "Maxim MAX6900"
  176. help
  177. If you say yes here you will get support for the
  178. Maxim MAX6900 I2C RTC chip.
  179. This driver can also be built as a module. If so, the module
  180. will be called rtc-max6900.
  181. config RTC_DRV_MAX8907
  182. tristate "Maxim MAX8907"
  183. depends on MFD_MAX8907
  184. help
  185. If you say yes here you will get support for the
  186. RTC of Maxim MAX8907 PMIC.
  187. This driver can also be built as a module. If so, the module
  188. will be called rtc-max8907.
  189. config RTC_DRV_MAX8925
  190. tristate "Maxim MAX8925"
  191. depends on MFD_MAX8925
  192. help
  193. If you say yes here you will get support for the
  194. RTC of Maxim MAX8925 PMIC.
  195. This driver can also be built as a module. If so, the module
  196. will be called rtc-max8925.
  197. config RTC_DRV_MAX8998
  198. tristate "Maxim MAX8998"
  199. depends on MFD_MAX8998
  200. help
  201. If you say yes here you will get support for the
  202. RTC of Maxim MAX8998 PMIC.
  203. This driver can also be built as a module. If so, the module
  204. will be called rtc-max8998.
  205. config RTC_DRV_MAX8997
  206. tristate "Maxim MAX8997"
  207. depends on MFD_MAX8997
  208. help
  209. If you say yes here you will get support for the
  210. RTC of Maxim MAX8997 PMIC.
  211. This driver can also be built as a module. If so, the module
  212. will be called rtc-max8997.
  213. config RTC_DRV_MAX77686
  214. tristate "Maxim MAX77686"
  215. depends on MFD_MAX77686
  216. help
  217. If you say yes here you will get support for the
  218. RTC of Maxim MAX77686 PMIC.
  219. This driver can also be built as a module. If so, the module
  220. will be called rtc-max77686.
  221. config RTC_DRV_RS5C372
  222. tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
  223. help
  224. If you say yes here you get support for the
  225. Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
  226. This driver can also be built as a module. If so, the module
  227. will be called rtc-rs5c372.
  228. config RTC_DRV_ISL1208
  229. tristate "Intersil ISL1208"
  230. help
  231. If you say yes here you get support for the
  232. Intersil ISL1208 RTC chip.
  233. This driver can also be built as a module. If so, the module
  234. will be called rtc-isl1208.
  235. config RTC_DRV_ISL12022
  236. tristate "Intersil ISL12022"
  237. help
  238. If you say yes here you get support for the
  239. Intersil ISL12022 RTC chip.
  240. This driver can also be built as a module. If so, the module
  241. will be called rtc-isl12022.
  242. config RTC_DRV_X1205
  243. tristate "Xicor/Intersil X1205"
  244. help
  245. If you say yes here you get support for the
  246. Xicor/Intersil X1205 RTC chip.
  247. This driver can also be built as a module. If so, the module
  248. will be called rtc-x1205.
  249. config RTC_DRV_PCF8523
  250. tristate "NXP PCF8523"
  251. help
  252. If you say yes here you get support for the NXP PCF8523 RTC
  253. chips.
  254. This driver can also be built as a module. If so, the module
  255. will be called rtc-pcf8523.
  256. config RTC_DRV_PCF8563
  257. tristate "Philips PCF8563/Epson RTC8564"
  258. help
  259. If you say yes here you get support for the
  260. Philips PCF8563 RTC chip. The Epson RTC8564
  261. should work as well.
  262. This driver can also be built as a module. If so, the module
  263. will be called rtc-pcf8563.
  264. config RTC_DRV_PCF8583
  265. tristate "Philips PCF8583"
  266. help
  267. If you say yes here you get support for the Philips PCF8583
  268. RTC chip found on Acorn RiscPCs. This driver supports the
  269. platform specific method of retrieving the current year from
  270. the RTC's SRAM. It will work on other platforms with the same
  271. chip, but the year will probably have to be tweaked.
  272. This driver can also be built as a module. If so, the module
  273. will be called rtc-pcf8583.
  274. config RTC_DRV_M41T80
  275. tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
  276. help
  277. If you say Y here you will get support for the ST M41T60
  278. and M41T80 RTC chips series. Currently, the following chips are
  279. supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
  280. M41ST85, and M41ST87.
  281. This driver can also be built as a module. If so, the module
  282. will be called rtc-m41t80.
  283. config RTC_DRV_M41T80_WDT
  284. bool "ST M41T65/M41T80 series RTC watchdog timer"
  285. depends on RTC_DRV_M41T80
  286. help
  287. If you say Y here you will get support for the
  288. watchdog timer in the ST M41T60 and M41T80 RTC chips series.
  289. config RTC_DRV_BQ32K
  290. tristate "TI BQ32000"
  291. help
  292. If you say Y here you will get support for the TI
  293. BQ32000 I2C RTC chip.
  294. This driver can also be built as a module. If so, the module
  295. will be called rtc-bq32k.
  296. config RTC_DRV_DM355EVM
  297. tristate "TI DaVinci DM355 EVM RTC"
  298. depends on MFD_DM355EVM_MSP
  299. help
  300. Supports the RTC firmware in the MSP430 on the DM355 EVM.
  301. config RTC_DRV_TWL92330
  302. boolean "TI TWL92330/Menelaus"
  303. depends on MENELAUS
  304. help
  305. If you say yes here you get support for the RTC on the
  306. TWL92330 "Menelaus" power management chip, used with OMAP2
  307. platforms. The support is integrated with the rest of
  308. the Menelaus driver; it's not separate module.
  309. config RTC_DRV_TWL4030
  310. tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
  311. depends on TWL4030_CORE
  312. help
  313. If you say yes here you get support for the RTC on the
  314. TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
  315. This driver can also be built as a module. If so, the module
  316. will be called rtc-twl.
  317. config RTC_DRV_TPS6586X
  318. tristate "TI TPS6586X RTC driver"
  319. depends on MFD_TPS6586X
  320. help
  321. TI Power Managment IC TPS6586X supports RTC functionality
  322. along with alarm. This driver supports the RTC driver for
  323. the TPS6586X RTC module.
  324. config RTC_DRV_TPS65910
  325. tristate "TI TPS65910 RTC driver"
  326. depends on RTC_CLASS && MFD_TPS65910
  327. help
  328. If you say yes here you get support for the RTC on the
  329. TPS65910 chips.
  330. This driver can also be built as a module. If so, the module
  331. will be called rtc-tps65910.
  332. config RTC_DRV_TPS80031
  333. tristate "TI TPS80031/TPS80032 RTC driver"
  334. depends on MFD_TPS80031
  335. help
  336. TI Power Managment IC TPS80031 supports RTC functionality
  337. along with alarm. This driver supports the RTC driver for
  338. the TPS80031 RTC module.
  339. config RTC_DRV_RC5T583
  340. tristate "RICOH 5T583 RTC driver"
  341. depends on MFD_RC5T583
  342. help
  343. If you say yes here you get support for the RTC on the
  344. RICOH 5T583 chips.
  345. This driver can also be built as a module. If so, the module
  346. will be called rtc-rc5t583.
  347. config RTC_DRV_S35390A
  348. tristate "Seiko Instruments S-35390A"
  349. select BITREVERSE
  350. help
  351. If you say yes here you will get support for the Seiko
  352. Instruments S-35390A.
  353. This driver can also be built as a module. If so the module
  354. will be called rtc-s35390a.
  355. config RTC_DRV_FM3130
  356. tristate "Ramtron FM3130"
  357. help
  358. If you say Y here you will get support for the
  359. Ramtron FM3130 RTC chips.
  360. Ramtron FM3130 is a chip with two separate devices inside,
  361. RTC clock and FRAM. This driver provides only RTC functionality.
  362. This driver can also be built as a module. If so the module
  363. will be called rtc-fm3130.
  364. config RTC_DRV_RX8581
  365. tristate "Epson RX-8581"
  366. help
  367. If you say yes here you will get support for the Epson RX-8581.
  368. This driver can also be built as a module. If so the module
  369. will be called rtc-rx8581.
  370. config RTC_DRV_RX8025
  371. tristate "Epson RX-8025SA/NB"
  372. help
  373. If you say yes here you get support for the Epson
  374. RX-8025SA/NB RTC chips.
  375. This driver can also be built as a module. If so, the module
  376. will be called rtc-rx8025.
  377. config RTC_DRV_EM3027
  378. tristate "EM Microelectronic EM3027"
  379. help
  380. If you say yes here you get support for the EM
  381. Microelectronic EM3027 RTC chips.
  382. This driver can also be built as a module. If so, the module
  383. will be called rtc-em3027.
  384. config RTC_DRV_RV3029C2
  385. tristate "Micro Crystal RTC"
  386. help
  387. If you say yes here you get support for the Micro Crystal
  388. RV3029-C2 RTC chips.
  389. This driver can also be built as a module. If so, the module
  390. will be called rtc-rv3029c2.
  391. endif # I2C
  392. comment "SPI RTC drivers"
  393. if SPI_MASTER
  394. config RTC_DRV_M41T93
  395. tristate "ST M41T93"
  396. help
  397. If you say yes here you will get support for the
  398. ST M41T93 SPI RTC chip.
  399. This driver can also be built as a module. If so, the module
  400. will be called rtc-m41t93.
  401. config RTC_DRV_M41T94
  402. tristate "ST M41T94"
  403. help
  404. If you say yes here you will get support for the
  405. ST M41T94 SPI RTC chip.
  406. This driver can also be built as a module. If so, the module
  407. will be called rtc-m41t94.
  408. config RTC_DRV_DS1305
  409. tristate "Dallas/Maxim DS1305/DS1306"
  410. help
  411. Select this driver to get support for the Dallas/Maxim DS1305
  412. and DS1306 real time clock chips. These support a trickle
  413. charger, alarms, and NVRAM in addition to the clock.
  414. This driver can also be built as a module. If so, the module
  415. will be called rtc-ds1305.
  416. config RTC_DRV_DS1390
  417. tristate "Dallas/Maxim DS1390/93/94"
  418. help
  419. If you say yes here you get support for the
  420. Dallas/Maxim DS1390/93/94 chips.
  421. This driver only supports the RTC feature, and not other chip
  422. features such as alarms and trickle charging.
  423. This driver can also be built as a module. If so, the module
  424. will be called rtc-ds1390.
  425. config RTC_DRV_MAX6902
  426. tristate "Maxim MAX6902"
  427. help
  428. If you say yes here you will get support for the
  429. Maxim MAX6902 SPI RTC chip.
  430. This driver can also be built as a module. If so, the module
  431. will be called rtc-max6902.
  432. config RTC_DRV_R9701
  433. tristate "Epson RTC-9701JE"
  434. help
  435. If you say yes here you will get support for the
  436. Epson RTC-9701JE SPI RTC chip.
  437. This driver can also be built as a module. If so, the module
  438. will be called rtc-r9701.
  439. config RTC_DRV_RS5C348
  440. tristate "Ricoh RS5C348A/B"
  441. help
  442. If you say yes here you get support for the
  443. Ricoh RS5C348A and RS5C348B RTC chips.
  444. This driver can also be built as a module. If so, the module
  445. will be called rtc-rs5c348.
  446. config RTC_DRV_DS3234
  447. tristate "Maxim/Dallas DS3234"
  448. help
  449. If you say yes here you get support for the
  450. Maxim/Dallas DS3234 SPI RTC chip.
  451. This driver can also be built as a module. If so, the module
  452. will be called rtc-ds3234.
  453. config RTC_DRV_PCF2123
  454. tristate "NXP PCF2123"
  455. help
  456. If you say yes here you get support for the NXP PCF2123
  457. RTC chip.
  458. This driver can also be built as a module. If so, the module
  459. will be called rtc-pcf2123.
  460. config RTC_DRV_RX4581
  461. tristate "Epson RX-4581"
  462. help
  463. If you say yes here you will get support for the Epson RX-4581.
  464. This driver can also be built as a module. If so the module
  465. will be called rtc-rx4581.
  466. endif # SPI_MASTER
  467. comment "Platform RTC drivers"
  468. # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
  469. # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
  470. # global rtc_lock ... it's not yet just another platform_device.
  471. config RTC_DRV_CMOS
  472. tristate "PC-style 'CMOS'"
  473. depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
  474. default y if X86
  475. help
  476. Say "yes" here to get direct support for the real time clock
  477. found in every PC or ACPI-based system, and some other boards.
  478. Specifically the original MC146818, compatibles like those in
  479. PC south bridges, the DS12887 or M48T86, some multifunction
  480. or LPC bus chips, and so on.
  481. Your system will need to define the platform device used by
  482. this driver, otherwise it won't be accessible. This means
  483. you can safely enable this driver if you don't know whether
  484. or not your board has this kind of hardware.
  485. This driver can also be built as a module. If so, the module
  486. will be called rtc-cmos.
  487. config RTC_DRV_VRTC
  488. tristate "Virtual RTC for Intel MID platforms"
  489. depends on X86_INTEL_MID
  490. default y if X86_INTEL_MID
  491. help
  492. Say "yes" here to get direct support for the real time clock
  493. found on Moorestown platforms. The VRTC is a emulated RTC that
  494. derives its clock source from a real RTC in the PMIC. The MC146818
  495. style programming interface is mostly conserved, but any
  496. updates are done via IPC calls to the system controller FW.
  497. config RTC_DRV_DS1216
  498. tristate "Dallas DS1216"
  499. depends on SNI_RM
  500. help
  501. If you say yes here you get support for the Dallas DS1216 RTC chips.
  502. config RTC_DRV_DS1286
  503. tristate "Dallas DS1286"
  504. help
  505. If you say yes here you get support for the Dallas DS1286 RTC chips.
  506. config RTC_DRV_DS1302
  507. tristate "Dallas DS1302"
  508. depends on SH_SECUREEDGE5410
  509. help
  510. If you say yes here you get support for the Dallas DS1302 RTC chips.
  511. config RTC_DRV_DS1511
  512. tristate "Dallas DS1511"
  513. help
  514. If you say yes here you get support for the
  515. Dallas DS1511 timekeeping/watchdog chip.
  516. This driver can also be built as a module. If so, the module
  517. will be called rtc-ds1511.
  518. config RTC_DRV_DS1553
  519. tristate "Maxim/Dallas DS1553"
  520. help
  521. If you say yes here you get support for the
  522. Maxim/Dallas DS1553 timekeeping chip.
  523. This driver can also be built as a module. If so, the module
  524. will be called rtc-ds1553.
  525. config RTC_DRV_DS1742
  526. tristate "Maxim/Dallas DS1742/1743"
  527. help
  528. If you say yes here you get support for the
  529. Maxim/Dallas DS1742/1743 timekeeping chip.
  530. This driver can also be built as a module. If so, the module
  531. will be called rtc-ds1742.
  532. config RTC_DRV_DA9052
  533. tristate "Dialog DA9052/DA9053 RTC"
  534. depends on PMIC_DA9052
  535. help
  536. Say y here to support the RTC driver for Dialog Semiconductor
  537. DA9052-BC and DA9053-AA/Bx PMICs.
  538. config RTC_DRV_DA9055
  539. tristate "Dialog Semiconductor DA9055 RTC"
  540. depends on MFD_DA9055
  541. help
  542. If you say yes here you will get support for the
  543. RTC of the Dialog DA9055 PMIC.
  544. This driver can also be built as a module. If so, the module
  545. will be called rtc-da9055
  546. config RTC_DRV_EFI
  547. tristate "EFI RTC"
  548. depends on IA64
  549. help
  550. If you say yes here you will get support for the EFI
  551. Real Time Clock.
  552. This driver can also be built as a module. If so, the module
  553. will be called rtc-efi.
  554. config RTC_DRV_STK17TA8
  555. tristate "Simtek STK17TA8"
  556. help
  557. If you say yes here you get support for the
  558. Simtek STK17TA8 timekeeping chip.
  559. This driver can also be built as a module. If so, the module
  560. will be called rtc-stk17ta8.
  561. config RTC_DRV_M48T86
  562. tristate "ST M48T86/Dallas DS12887"
  563. help
  564. If you say Y here you will get support for the
  565. ST M48T86 and Dallas DS12887 RTC chips.
  566. This driver can also be built as a module. If so, the module
  567. will be called rtc-m48t86.
  568. config RTC_DRV_M48T35
  569. tristate "ST M48T35"
  570. help
  571. If you say Y here you will get support for the
  572. ST M48T35 RTC chip.
  573. This driver can also be built as a module, if so, the module
  574. will be called "rtc-m48t35".
  575. config RTC_DRV_M48T59
  576. tristate "ST M48T59/M48T08/M48T02"
  577. help
  578. If you say Y here you will get support for the
  579. ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
  580. These chips are usually found in Sun SPARC and UltraSPARC
  581. workstations.
  582. This driver can also be built as a module, if so, the module
  583. will be called "rtc-m48t59".
  584. config RTC_DRV_MSM6242
  585. tristate "Oki MSM6242"
  586. help
  587. If you say yes here you get support for the Oki MSM6242
  588. timekeeping chip. It is used in some Amiga models (e.g. A2000).
  589. This driver can also be built as a module. If so, the module
  590. will be called rtc-msm6242.
  591. config RTC_DRV_BQ4802
  592. tristate "TI BQ4802"
  593. help
  594. If you say Y here you will get support for the TI
  595. BQ4802 RTC chip.
  596. This driver can also be built as a module. If so, the module
  597. will be called rtc-bq4802.
  598. config RTC_DRV_RP5C01
  599. tristate "Ricoh RP5C01"
  600. help
  601. If you say yes here you get support for the Ricoh RP5C01
  602. timekeeping chip. It is used in some Amiga models (e.g. A3000
  603. and A4000).
  604. This driver can also be built as a module. If so, the module
  605. will be called rtc-rp5c01.
  606. config RTC_DRV_V3020
  607. tristate "EM Microelectronic V3020"
  608. help
  609. If you say yes here you will get support for the
  610. EM Microelectronic v3020 RTC chip.
  611. This driver can also be built as a module. If so, the module
  612. will be called rtc-v3020.
  613. config RTC_DRV_DS2404
  614. tristate "Dallas DS2404"
  615. help
  616. If you say yes here you get support for the
  617. Dallas DS2404 RTC chip.
  618. This driver can also be built as a module. If so, the module
  619. will be called rtc-ds2404.
  620. config RTC_DRV_WM831X
  621. tristate "Wolfson Microelectronics WM831x RTC"
  622. depends on MFD_WM831X
  623. help
  624. If you say yes here you will get support for the RTC subsystem
  625. of the Wolfson Microelectronics WM831X series PMICs.
  626. This driver can also be built as a module. If so, the module
  627. will be called "rtc-wm831x".
  628. config RTC_DRV_WM8350
  629. tristate "Wolfson Microelectronics WM8350 RTC"
  630. depends on MFD_WM8350
  631. help
  632. If you say yes here you will get support for the RTC subsystem
  633. of the Wolfson Microelectronics WM8350.
  634. This driver can also be built as a module. If so, the module
  635. will be called "rtc-wm8350".
  636. config RTC_DRV_SPEAR
  637. tristate "SPEAR ST RTC"
  638. depends on PLAT_SPEAR
  639. default y
  640. help
  641. If you say Y here you will get support for the RTC found on
  642. spear
  643. config RTC_DRV_PCF50633
  644. depends on MFD_PCF50633
  645. tristate "NXP PCF50633 RTC"
  646. help
  647. If you say yes here you get support for the RTC subsystem of the
  648. NXP PCF50633 used in embedded systems.
  649. config RTC_DRV_AB3100
  650. tristate "ST-Ericsson AB3100 RTC"
  651. depends on AB3100_CORE
  652. default y if AB3100_CORE
  653. help
  654. Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
  655. support. This chip contains a battery- and capacitor-backed RTC.
  656. config RTC_DRV_AB8500
  657. tristate "ST-Ericsson AB8500 RTC"
  658. depends on AB8500_CORE
  659. select RTC_INTF_DEV
  660. select RTC_INTF_DEV_UIE_EMUL
  661. help
  662. Select this to enable the ST-Ericsson AB8500 power management IC RTC
  663. support. This chip contains a battery- and capacitor-backed RTC.
  664. config RTC_DRV_NUC900
  665. tristate "NUC910/NUC920 RTC driver"
  666. depends on ARCH_W90X900
  667. help
  668. If you say yes here you get support for the RTC subsystem of the
  669. NUC910/NUC920 used in embedded systems.
  670. comment "on-CPU RTC drivers"
  671. config RTC_DRV_DAVINCI
  672. tristate "TI DaVinci RTC"
  673. depends on ARCH_DAVINCI_DM365
  674. help
  675. If you say yes here you get support for the RTC on the
  676. DaVinci platforms (DM365).
  677. This driver can also be built as a module. If so, the module
  678. will be called rtc-davinci.
  679. config RTC_DRV_IMXDI
  680. tristate "Freescale IMX DryIce Real Time Clock"
  681. depends on ARCH_MXC
  682. help
  683. Support for Freescale IMX DryIce RTC
  684. This driver can also be built as a module, if so, the module
  685. will be called "rtc-imxdi".
  686. config RTC_DRV_OMAP
  687. tristate "TI OMAP1"
  688. depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
  689. help
  690. Say "yes" here to support the on chip real time clock
  691. present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
  692. This driver can also be built as a module, if so, module
  693. will be called rtc-omap.
  694. config HAVE_S3C_RTC
  695. bool
  696. help
  697. This will include RTC support for Samsung SoCs. If
  698. you want to include RTC support for any machine, kindly
  699. select this in the respective mach-XXXX/Kconfig file.
  700. config RTC_DRV_S3C
  701. tristate "Samsung S3C series SoC RTC"
  702. depends on ARCH_S3C64XX || HAVE_S3C_RTC
  703. help
  704. RTC (Realtime Clock) driver for the clock inbuilt into the
  705. Samsung S3C24XX series of SoCs. This can provide periodic
  706. interrupt rates from 1Hz to 64Hz for user programs, and
  707. wakeup from Alarm.
  708. The driver currently supports the common features on all the
  709. S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
  710. and S3C2442.
  711. This driver can also be build as a module. If so, the module
  712. will be called rtc-s3c.
  713. config RTC_DRV_EP93XX
  714. tristate "Cirrus Logic EP93XX"
  715. depends on ARCH_EP93XX
  716. help
  717. If you say yes here you get support for the
  718. RTC embedded in the Cirrus Logic EP93XX processors.
  719. This driver can also be built as a module. If so, the module
  720. will be called rtc-ep93xx.
  721. config RTC_DRV_SA1100
  722. tristate "SA11x0/PXA2xx/PXA910"
  723. depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
  724. help
  725. If you say Y here you will get access to the real time clock
  726. built into your SA11x0 or PXA2xx CPU.
  727. To compile this driver as a module, choose M here: the
  728. module will be called rtc-sa1100.
  729. config RTC_DRV_SH
  730. tristate "SuperH On-Chip RTC"
  731. depends on SUPERH && HAVE_CLK
  732. help
  733. Say Y here to enable support for the on-chip RTC found in
  734. most SuperH processors.
  735. To compile this driver as a module, choose M here: the
  736. module will be called rtc-sh.
  737. config RTC_DRV_VR41XX
  738. tristate "NEC VR41XX"
  739. depends on CPU_VR41XX
  740. help
  741. If you say Y here you will get access to the real time clock
  742. built into your NEC VR41XX CPU.
  743. To compile this driver as a module, choose M here: the
  744. module will be called rtc-vr41xx.
  745. config RTC_DRV_PL030
  746. tristate "ARM AMBA PL030 RTC"
  747. depends on ARM_AMBA
  748. help
  749. If you say Y here you will get access to ARM AMBA
  750. PrimeCell PL030 RTC found on certain ARM SOCs.
  751. To compile this driver as a module, choose M here: the
  752. module will be called rtc-pl030.
  753. config RTC_DRV_PL031
  754. tristate "ARM AMBA PL031 RTC"
  755. depends on ARM_AMBA
  756. help
  757. If you say Y here you will get access to ARM AMBA
  758. PrimeCell PL031 RTC found on certain ARM SOCs.
  759. To compile this driver as a module, choose M here: the
  760. module will be called rtc-pl031.
  761. config RTC_DRV_AT32AP700X
  762. tristate "AT32AP700X series RTC"
  763. depends on PLATFORM_AT32AP
  764. help
  765. Driver for the internal RTC (Realtime Clock) on Atmel AVR32
  766. AT32AP700x family processors.
  767. config RTC_DRV_AT91RM9200
  768. tristate "AT91RM9200 or some AT91SAM9 RTC"
  769. depends on ARCH_AT91
  770. help
  771. Driver for the internal RTC (Realtime Clock) module found on
  772. Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
  773. this is powered by the backup power supply.
  774. config RTC_DRV_AT91SAM9
  775. tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
  776. depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
  777. help
  778. RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
  779. (Real Time Timer). These timers are powered by the backup power
  780. supply (such as a small coin cell battery), but do not need to
  781. be used as RTCs.
  782. (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
  783. dedicated RTC module and leave the RTT available for other uses.)
  784. config RTC_DRV_AT91SAM9_RTT
  785. int
  786. range 0 1
  787. default 0
  788. prompt "RTT module Number" if ARCH_AT91SAM9263
  789. depends on RTC_DRV_AT91SAM9
  790. help
  791. More than one RTT module is available. You can choose which
  792. one will be used as an RTC. The default of zero is normally
  793. OK to use, though some systems use that for non-RTC purposes.
  794. config RTC_DRV_AT91SAM9_GPBR
  795. int
  796. range 0 3 if !ARCH_AT91SAM9263
  797. range 0 15 if ARCH_AT91SAM9263
  798. default 0
  799. prompt "Backup Register Number"
  800. depends on RTC_DRV_AT91SAM9
  801. help
  802. The RTC driver needs to use one of the General Purpose Backup
  803. Registers (GPBRs) as well as the RTT. You can choose which one
  804. will be used. The default of zero is normally OK to use, but
  805. on some systems other software needs to use that register.
  806. config RTC_DRV_AU1XXX
  807. tristate "Au1xxx Counter0 RTC support"
  808. depends on MIPS_ALCHEMY
  809. help
  810. This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
  811. counter) to be used as a RTC.
  812. This driver can also be built as a module. If so, the module
  813. will be called rtc-au1xxx.
  814. config RTC_DRV_BFIN
  815. tristate "Blackfin On-Chip RTC"
  816. depends on BLACKFIN && !BF561
  817. help
  818. If you say yes here you will get support for the
  819. Blackfin On-Chip Real Time Clock.
  820. This driver can also be built as a module. If so, the module
  821. will be called rtc-bfin.
  822. config RTC_DRV_RS5C313
  823. tristate "Ricoh RS5C313"
  824. depends on SH_LANDISK
  825. help
  826. If you say yes here you get support for the Ricoh RS5C313 RTC chips.
  827. config RTC_DRV_GENERIC
  828. tristate "Generic RTC support"
  829. # Please consider writing a new RTC driver instead of using the generic
  830. # RTC abstraction
  831. depends on PARISC || M68K || PPC || SUPERH32
  832. help
  833. Say Y or M here to enable RTC support on systems using the generic
  834. RTC abstraction. If you do not know what you are doing, you should
  835. just say Y.
  836. config RTC_DRV_PXA
  837. tristate "PXA27x/PXA3xx"
  838. depends on ARCH_PXA
  839. help
  840. If you say Y here you will get access to the real time clock
  841. built into your PXA27x or PXA3xx CPU.
  842. This RTC driver uses PXA RTC registers available since pxa27x
  843. series (RDxR, RYxR) instead of legacy RCNR, RTAR.
  844. config RTC_DRV_VT8500
  845. tristate "VIA/WonderMedia 85xx SoC RTC"
  846. depends on ARCH_VT8500
  847. help
  848. If you say Y here you will get access to the real time clock
  849. built into your VIA VT8500 SoC or its relatives.
  850. config RTC_DRV_SUN4V
  851. bool "SUN4V Hypervisor RTC"
  852. depends on SPARC64
  853. help
  854. If you say Y here you will get support for the Hypervisor
  855. based RTC on SUN4V systems.
  856. config RTC_DRV_STARFIRE
  857. bool "Starfire RTC"
  858. depends on SPARC64
  859. help
  860. If you say Y here you will get support for the RTC found on
  861. Starfire systems.
  862. config RTC_DRV_TX4939
  863. tristate "TX4939 SoC"
  864. depends on SOC_TX4939
  865. help
  866. Driver for the internal RTC (Realtime Clock) module found on
  867. Toshiba TX4939 SoC.
  868. config RTC_DRV_MV
  869. tristate "Marvell SoC RTC"
  870. depends on ARCH_KIRKWOOD || ARCH_DOVE
  871. help
  872. If you say yes here you will get support for the in-chip RTC
  873. that can be found in some of Marvell's SoC devices, such as
  874. the Kirkwood 88F6281 and 88F6192.
  875. This driver can also be built as a module. If so, the module
  876. will be called rtc-mv.
  877. config RTC_DRV_PS3
  878. tristate "PS3 RTC"
  879. depends on PPC_PS3
  880. help
  881. If you say yes here you will get support for the RTC on PS3.
  882. This driver can also be built as a module. If so, the module
  883. will be called rtc-ps3.
  884. config RTC_DRV_COH901331
  885. tristate "ST-Ericsson COH 901 331 RTC"
  886. depends on ARCH_U300
  887. help
  888. If you say Y here you will get access to ST-Ericsson
  889. COH 901 331 RTC clock found in some ST-Ericsson Mobile
  890. Platforms.
  891. This driver can also be built as a module. If so, the module
  892. will be called "rtc-coh901331".
  893. config RTC_DRV_STMP
  894. tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
  895. depends on ARCH_MXS
  896. help
  897. If you say yes here you will get support for the onboard
  898. STMP3xxx/i.MX23/i.MX28 RTC.
  899. This driver can also be built as a module. If so, the module
  900. will be called rtc-stmp3xxx.
  901. config RTC_DRV_PCAP
  902. tristate "PCAP RTC"
  903. depends on EZX_PCAP
  904. help
  905. If you say Y here you will get support for the RTC found on
  906. the PCAP2 ASIC used on some Motorola phones.
  907. config RTC_DRV_MC13XXX
  908. depends on MFD_MC13XXX
  909. tristate "Freescale MC13xxx RTC"
  910. help
  911. This enables support for the RTCs found on Freescale's PMICs
  912. MC13783 and MC13892.
  913. config RTC_DRV_MPC5121
  914. tristate "Freescale MPC5121 built-in RTC"
  915. depends on PPC_MPC512x || PPC_MPC52xx
  916. help
  917. If you say yes here you will get support for the
  918. built-in RTC on MPC5121 or on MPC5200.
  919. This driver can also be built as a module. If so, the module
  920. will be called rtc-mpc5121.
  921. config RTC_DRV_JZ4740
  922. tristate "Ingenic JZ4740 SoC"
  923. depends on MACH_JZ4740
  924. help
  925. If you say yes here you get support for the Ingenic JZ4740 SoC RTC
  926. controller.
  927. This driver can also be buillt as a module. If so, the module
  928. will be called rtc-jz4740.
  929. config RTC_DRV_LPC32XX
  930. depends on ARCH_LPC32XX
  931. tristate "NXP LPC32XX RTC"
  932. help
  933. This enables support for the NXP RTC in the LPC32XX
  934. This driver can also be buillt as a module. If so, the module
  935. will be called rtc-lpc32xx.
  936. config RTC_DRV_PM8XXX
  937. tristate "Qualcomm PMIC8XXX RTC"
  938. depends on MFD_PM8XXX
  939. help
  940. If you say yes here you get support for the
  941. Qualcomm PMIC8XXX RTC.
  942. To compile this driver as a module, choose M here: the
  943. module will be called rtc-pm8xxx.
  944. config RTC_DRV_TEGRA
  945. tristate "NVIDIA Tegra Internal RTC driver"
  946. depends on ARCH_TEGRA
  947. help
  948. If you say yes here you get support for the
  949. Tegra 200 series internal RTC module.
  950. This drive can also be built as a module. If so, the module
  951. will be called rtc-tegra.
  952. config RTC_DRV_TILE
  953. tristate "Tilera hypervisor RTC support"
  954. depends on TILE
  955. help
  956. Enable support for the Linux driver side of the Tilera
  957. hypervisor's real-time clock interface.
  958. config RTC_DRV_PUV3
  959. tristate "PKUnity v3 RTC support"
  960. depends on ARCH_PUV3
  961. help
  962. This enables support for the RTC in the PKUnity-v3 SoCs.
  963. This drive can also be built as a module. If so, the module
  964. will be called rtc-puv3.
  965. config RTC_DRV_LOONGSON1
  966. tristate "loongson1 RTC support"
  967. depends on MACH_LOONGSON1
  968. help
  969. This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
  970. counter) to be used as a RTC.
  971. This driver can also be built as a module. If so, the module
  972. will be called rtc-ls1x.
  973. config RTC_DRV_MXC
  974. tristate "Freescale MXC Real Time Clock"
  975. depends on ARCH_MXC
  976. help
  977. If you say yes here you get support for the Freescale MXC
  978. RTC module.
  979. This driver can also be built as a module, if so, the module
  980. will be called "rtc-mxc".
  981. config RTC_DRV_SNVS
  982. tristate "Freescale SNVS RTC support"
  983. depends on HAS_IOMEM
  984. depends on OF
  985. help
  986. If you say yes here you get support for the Freescale SNVS
  987. Low Power (LP) RTC module.
  988. This driver can also be built as a module, if so, the module
  989. will be called "rtc-snvs".
  990. endif # RTC_CLASS