Kconfig 32 KB

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