Kconfig 32 KB

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