Kconfig 34 KB

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