Kconfig 33 KB

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