Kconfig 31 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073
  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
  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 Moorestown platforms"
  400. depends on X86_MRST
  401. default y if X86_MRST
  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_EFI
  445. tristate "EFI RTC"
  446. depends on IA64
  447. help
  448. If you say yes here you will get support for the EFI
  449. Real Time Clock.
  450. This driver can also be built as a module. If so, the module
  451. will be called rtc-efi.
  452. config RTC_DRV_STK17TA8
  453. tristate "Simtek STK17TA8"
  454. depends on RTC_CLASS
  455. help
  456. If you say yes here you get support for the
  457. Simtek STK17TA8 timekeeping chip.
  458. This driver can also be built as a module. If so, the module
  459. will be called rtc-stk17ta8.
  460. config RTC_DRV_M48T86
  461. tristate "ST M48T86/Dallas DS12887"
  462. help
  463. If you say Y here you will get support for the
  464. ST M48T86 and Dallas DS12887 RTC chips.
  465. This driver can also be built as a module. If so, the module
  466. will be called rtc-m48t86.
  467. config RTC_DRV_M48T35
  468. tristate "ST M48T35"
  469. help
  470. If you say Y here you will get support for the
  471. ST M48T35 RTC chip.
  472. This driver can also be built as a module, if so, the module
  473. will be called "rtc-m48t35".
  474. config RTC_DRV_M48T59
  475. tristate "ST M48T59/M48T08/M48T02"
  476. help
  477. If you say Y here you will get support for the
  478. ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
  479. These chips are usually found in Sun SPARC and UltraSPARC
  480. workstations.
  481. This driver can also be built as a module, if so, the module
  482. will be called "rtc-m48t59".
  483. config RTC_DRV_MSM6242
  484. tristate "Oki MSM6242"
  485. help
  486. If you say yes here you get support for the Oki MSM6242
  487. timekeeping chip. It is used in some Amiga models (e.g. A2000).
  488. This driver can also be built as a module. If so, the module
  489. will be called rtc-msm6242.
  490. config RTC_DRV_IMXDI
  491. tristate "Freescale IMX DryIce Real Time Clock"
  492. depends on ARCH_MX25
  493. depends on RTC_CLASS
  494. help
  495. Support for Freescale IMX DryIce RTC
  496. This driver can also be built as a module, if so, the module
  497. will be called "rtc-imxdi".
  498. config RTC_MXC
  499. tristate "Freescale MXC Real Time Clock"
  500. depends on ARCH_MXC
  501. depends on RTC_CLASS
  502. help
  503. If you say yes here you get support for the Freescale MXC
  504. RTC module.
  505. This driver can also be built as a module, if so, the module
  506. will be called "rtc-mxc".
  507. config RTC_DRV_BQ4802
  508. tristate "TI BQ4802"
  509. help
  510. If you say Y here you will get support for the TI
  511. BQ4802 RTC chip.
  512. This driver can also be built as a module. If so, the module
  513. will be called rtc-bq4802.
  514. config RTC_DRV_RP5C01
  515. tristate "Ricoh RP5C01"
  516. help
  517. If you say yes here you get support for the Ricoh RP5C01
  518. timekeeping chip. It is used in some Amiga models (e.g. A3000
  519. and A4000).
  520. This driver can also be built as a module. If so, the module
  521. will be called rtc-rp5c01.
  522. config RTC_DRV_V3020
  523. tristate "EM Microelectronic V3020"
  524. help
  525. If you say yes here you will get support for the
  526. EM Microelectronic v3020 RTC chip.
  527. This driver can also be built as a module. If so, the module
  528. will be called rtc-v3020.
  529. config RTC_DRV_WM831X
  530. tristate "Wolfson Microelectronics WM831x RTC"
  531. depends on MFD_WM831X
  532. help
  533. If you say yes here you will get support for the RTC subsystem
  534. of the Wolfson Microelectronics WM831X series PMICs.
  535. This driver can also be built as a module. If so, the module
  536. will be called "rtc-wm831x".
  537. config RTC_DRV_WM8350
  538. tristate "Wolfson Microelectronics WM8350 RTC"
  539. depends on MFD_WM8350
  540. help
  541. If you say yes here you will get support for the RTC subsystem
  542. of the Wolfson Microelectronics WM8350.
  543. This driver can also be built as a module. If so, the module
  544. will be called "rtc-wm8350".
  545. config RTC_DRV_SPEAR
  546. tristate "SPEAR ST RTC"
  547. depends on PLAT_SPEAR
  548. default y
  549. help
  550. If you say Y here you will get support for the RTC found on
  551. spear
  552. config RTC_DRV_PCF50633
  553. depends on MFD_PCF50633
  554. tristate "NXP PCF50633 RTC"
  555. help
  556. If you say yes here you get support for the RTC subsystem of the
  557. NXP PCF50633 used in embedded systems.
  558. config RTC_DRV_AB3100
  559. tristate "ST-Ericsson AB3100 RTC"
  560. depends on AB3100_CORE
  561. default y if AB3100_CORE
  562. help
  563. Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
  564. support. This chip contains a battery- and capacitor-backed RTC.
  565. config RTC_DRV_AB8500
  566. tristate "ST-Ericsson AB8500 RTC"
  567. depends on AB8500_CORE
  568. help
  569. Select this to enable the ST-Ericsson AB8500 power management IC RTC
  570. support. This chip contains a battery- and capacitor-backed RTC.
  571. config RTC_DRV_NUC900
  572. tristate "NUC910/NUC920 RTC driver"
  573. depends on RTC_CLASS && ARCH_W90X900
  574. help
  575. If you say yes here you get support for the RTC subsystem of the
  576. NUC910/NUC920 used in embedded systems.
  577. comment "on-CPU RTC drivers"
  578. config RTC_DRV_DAVINCI
  579. tristate "TI DaVinci RTC"
  580. depends on ARCH_DAVINCI_DM365
  581. help
  582. If you say yes here you get support for the RTC on the
  583. DaVinci platforms (DM365).
  584. This driver can also be built as a module. If so, the module
  585. will be called rtc-davinci.
  586. config RTC_DRV_OMAP
  587. tristate "TI OMAP1"
  588. depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
  589. help
  590. Say "yes" here to support the real time clock on TI OMAP1 and
  591. DA8xx/OMAP-L13x chips. This driver can also be built as a
  592. module called rtc-omap.
  593. config HAVE_S3C_RTC
  594. bool
  595. help
  596. This will include RTC support for Samsung SoCs. If
  597. you want to include RTC support for any machine, kindly
  598. select this in the respective mach-XXXX/Kconfig file.
  599. config RTC_DRV_S3C
  600. tristate "Samsung S3C series SoC RTC"
  601. depends on ARCH_S3C2410 || ARCH_S3C64XX || HAVE_S3C_RTC
  602. help
  603. RTC (Realtime Clock) driver for the clock inbuilt into the
  604. Samsung S3C24XX series of SoCs. This can provide periodic
  605. interrupt rates from 1Hz to 64Hz for user programs, and
  606. wakeup from Alarm.
  607. The driver currently supports the common features on all the
  608. S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
  609. and S3C2442.
  610. This driver can also be build as a module. If so, the module
  611. will be called rtc-s3c.
  612. config RTC_DRV_EP93XX
  613. tristate "Cirrus Logic EP93XX"
  614. depends on ARCH_EP93XX
  615. help
  616. If you say yes here you get support for the
  617. RTC embedded in the Cirrus Logic EP93XX processors.
  618. This driver can also be built as a module. If so, the module
  619. will be called rtc-ep93xx.
  620. config RTC_DRV_SA1100
  621. tristate "SA11x0/PXA2xx"
  622. depends on ARCH_SA1100 || ARCH_PXA
  623. help
  624. If you say Y here you will get access to the real time clock
  625. built into your SA11x0 or PXA2xx CPU.
  626. To compile this driver as a module, choose M here: the
  627. module will be called rtc-sa1100.
  628. config RTC_DRV_SH
  629. tristate "SuperH On-Chip RTC"
  630. depends on RTC_CLASS && SUPERH && HAVE_CLK
  631. help
  632. Say Y here to enable support for the on-chip RTC found in
  633. most SuperH processors.
  634. To compile this driver as a module, choose M here: the
  635. module will be called rtc-sh.
  636. config RTC_DRV_VR41XX
  637. tristate "NEC VR41XX"
  638. depends on CPU_VR41XX
  639. help
  640. If you say Y here you will get access to the real time clock
  641. built into your NEC VR41XX CPU.
  642. To compile this driver as a module, choose M here: the
  643. module will be called rtc-vr41xx.
  644. config RTC_DRV_PL030
  645. tristate "ARM AMBA PL030 RTC"
  646. depends on ARM_AMBA
  647. help
  648. If you say Y here you will get access to ARM AMBA
  649. PrimeCell PL030 RTC found on certain ARM SOCs.
  650. To compile this driver as a module, choose M here: the
  651. module will be called rtc-pl030.
  652. config RTC_DRV_PL031
  653. tristate "ARM AMBA PL031 RTC"
  654. depends on ARM_AMBA
  655. help
  656. If you say Y here you will get access to ARM AMBA
  657. PrimeCell PL031 RTC found on certain ARM SOCs.
  658. To compile this driver as a module, choose M here: the
  659. module will be called rtc-pl031.
  660. config RTC_DRV_AT32AP700X
  661. tristate "AT32AP700X series RTC"
  662. depends on PLATFORM_AT32AP
  663. help
  664. Driver for the internal RTC (Realtime Clock) on Atmel AVR32
  665. AT32AP700x family processors.
  666. config RTC_DRV_AT91RM9200
  667. tristate "AT91RM9200 or some AT91SAM9 RTC"
  668. depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
  669. help
  670. Driver for the internal RTC (Realtime Clock) module found on
  671. Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
  672. this is powered by the backup power supply.
  673. config RTC_DRV_AT91SAM9
  674. tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
  675. depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
  676. help
  677. RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
  678. (Real Time Timer). These timers are powered by the backup power
  679. supply (such as a small coin cell battery), but do not need to
  680. be used as RTCs.
  681. (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
  682. dedicated RTC module and leave the RTT available for other uses.)
  683. config RTC_DRV_AT91SAM9_RTT
  684. int
  685. range 0 1
  686. default 0
  687. prompt "RTT module Number" if ARCH_AT91SAM9263
  688. depends on RTC_DRV_AT91SAM9
  689. help
  690. More than one RTT module is available. You can choose which
  691. one will be used as an RTC. The default of zero is normally
  692. OK to use, though some systems use that for non-RTC purposes.
  693. config RTC_DRV_AT91SAM9_GPBR
  694. int
  695. range 0 3 if !ARCH_AT91SAM9263
  696. range 0 15 if ARCH_AT91SAM9263
  697. default 0
  698. prompt "Backup Register Number"
  699. depends on RTC_DRV_AT91SAM9
  700. help
  701. The RTC driver needs to use one of the General Purpose Backup
  702. Registers (GPBRs) as well as the RTT. You can choose which one
  703. will be used. The default of zero is normally OK to use, but
  704. on some systems other software needs to use that register.
  705. config RTC_DRV_AU1XXX
  706. tristate "Au1xxx Counter0 RTC support"
  707. depends on MIPS_ALCHEMY
  708. help
  709. This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
  710. counter) to be used as a RTC.
  711. This driver can also be built as a module. If so, the module
  712. will be called rtc-au1xxx.
  713. config RTC_DRV_BFIN
  714. tristate "Blackfin On-Chip RTC"
  715. depends on BLACKFIN && !BF561
  716. help
  717. If you say yes here you will get support for the
  718. Blackfin On-Chip Real Time Clock.
  719. This driver can also be built as a module. If so, the module
  720. will be called rtc-bfin.
  721. config RTC_DRV_RS5C313
  722. tristate "Ricoh RS5C313"
  723. depends on SH_LANDISK
  724. help
  725. If you say yes here you get support for the Ricoh RS5C313 RTC chips.
  726. config RTC_DRV_GENERIC
  727. tristate "Generic RTC support"
  728. # Please consider writing a new RTC driver instead of using the generic
  729. # RTC abstraction
  730. depends on PARISC || M68K || PPC || SUPERH32
  731. help
  732. Say Y or M here to enable RTC support on systems using the generic
  733. RTC abstraction. If you do not know what you are doing, you should
  734. just say Y.
  735. config RTC_DRV_PXA
  736. tristate "PXA27x/PXA3xx"
  737. depends on ARCH_PXA
  738. help
  739. If you say Y here you will get access to the real time clock
  740. built into your PXA27x or PXA3xx CPU.
  741. This RTC driver uses PXA RTC registers available since pxa27x
  742. series (RDxR, RYxR) instead of legacy RCNR, RTAR.
  743. config RTC_DRV_VT8500
  744. tristate "VIA/WonderMedia 85xx SoC RTC"
  745. depends on ARCH_VT8500
  746. help
  747. If you say Y here you will get access to the real time clock
  748. built into your VIA VT8500 SoC or its relatives.
  749. config RTC_DRV_SUN4V
  750. bool "SUN4V Hypervisor RTC"
  751. depends on SPARC64
  752. help
  753. If you say Y here you will get support for the Hypervisor
  754. based RTC on SUN4V systems.
  755. config RTC_DRV_STARFIRE
  756. bool "Starfire RTC"
  757. depends on SPARC64
  758. help
  759. If you say Y here you will get support for the RTC found on
  760. Starfire systems.
  761. config RTC_DRV_TX4939
  762. tristate "TX4939 SoC"
  763. depends on SOC_TX4939
  764. help
  765. Driver for the internal RTC (Realtime Clock) module found on
  766. Toshiba TX4939 SoC.
  767. config RTC_DRV_MV
  768. tristate "Marvell SoC RTC"
  769. depends on ARCH_KIRKWOOD || ARCH_DOVE
  770. help
  771. If you say yes here you will get support for the in-chip RTC
  772. that can be found in some of Marvell's SoC devices, such as
  773. the Kirkwood 88F6281 and 88F6192.
  774. This driver can also be built as a module. If so, the module
  775. will be called rtc-mv.
  776. config RTC_DRV_PS3
  777. tristate "PS3 RTC"
  778. depends on PPC_PS3
  779. help
  780. If you say yes here you will get support for the RTC on PS3.
  781. This driver can also be built as a module. If so, the module
  782. will be called rtc-ps3.
  783. config RTC_DRV_COH901331
  784. tristate "ST-Ericsson COH 901 331 RTC"
  785. depends on ARCH_U300
  786. help
  787. If you say Y here you will get access to ST-Ericsson
  788. COH 901 331 RTC clock found in some ST-Ericsson Mobile
  789. Platforms.
  790. This driver can also be built as a module. If so, the module
  791. will be called "rtc-coh901331".
  792. config RTC_DRV_STMP
  793. tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
  794. depends on ARCH_MXS
  795. help
  796. If you say yes here you will get support for the onboard
  797. STMP3xxx/i.MX23/i.MX28 RTC.
  798. This driver can also be built as a module. If so, the module
  799. will be called rtc-stmp3xxx.
  800. config RTC_DRV_PCAP
  801. tristate "PCAP RTC"
  802. depends on EZX_PCAP
  803. help
  804. If you say Y here you will get support for the RTC found on
  805. the PCAP2 ASIC used on some Motorola phones.
  806. config RTC_DRV_MC13XXX
  807. depends on MFD_MC13XXX
  808. tristate "Freescale MC13xxx RTC"
  809. help
  810. This enables support for the RTCs found on Freescale's PMICs
  811. MC13783 and MC13892.
  812. config RTC_DRV_MPC5121
  813. tristate "Freescale MPC5121 built-in RTC"
  814. depends on PPC_MPC512x || PPC_MPC52xx
  815. help
  816. If you say yes here you will get support for the
  817. built-in RTC on MPC5121 or on MPC5200.
  818. This driver can also be built as a module. If so, the module
  819. will be called rtc-mpc5121.
  820. config RTC_DRV_JZ4740
  821. tristate "Ingenic JZ4740 SoC"
  822. depends on RTC_CLASS
  823. depends on MACH_JZ4740
  824. help
  825. If you say yes here you get support for the Ingenic JZ4740 SoC RTC
  826. controller.
  827. This driver can also be buillt as a module. If so, the module
  828. will be called rtc-jz4740.
  829. config RTC_DRV_LPC32XX
  830. depends on ARCH_LPC32XX
  831. tristate "NXP LPC32XX RTC"
  832. help
  833. This enables support for the NXP RTC in the LPC32XX
  834. This driver can also be buillt as a module. If so, the module
  835. will be called rtc-lpc32xx.
  836. config RTC_DRV_PM8XXX
  837. tristate "Qualcomm PMIC8XXX RTC"
  838. depends on MFD_PM8XXX
  839. help
  840. If you say yes here you get support for the
  841. Qualcomm PMIC8XXX RTC.
  842. To compile this driver as a module, choose M here: the
  843. module will be called rtc-pm8xxx.
  844. config RTC_DRV_TEGRA
  845. tristate "NVIDIA Tegra Internal RTC driver"
  846. depends on RTC_CLASS && ARCH_TEGRA
  847. help
  848. If you say yes here you get support for the
  849. Tegra 200 series internal RTC module.
  850. This drive can also be built as a module. If so, the module
  851. will be called rtc-tegra.
  852. config RTC_DRV_TILE
  853. tristate "Tilera hypervisor RTC support"
  854. depends on TILE
  855. help
  856. Enable support for the Linux driver side of the Tilera
  857. hypervisor's real-time clock interface.
  858. config RTC_DRV_PUV3
  859. tristate "PKUnity v3 RTC support"
  860. depends on ARCH_PUV3
  861. help
  862. This enables support for the RTC in the PKUnity-v3 SoCs.
  863. This drive can also be built as a module. If so, the module
  864. will be called rtc-puv3.
  865. endif # RTC_CLASS