Kconfig 30 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037
  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_M41T94
  312. tristate "ST M41T94"
  313. help
  314. If you say yes here you will get support for the
  315. ST M41T94 SPI RTC chip.
  316. This driver can also be built as a module. If so, the module
  317. will be called rtc-m41t94.
  318. config RTC_DRV_DS1305
  319. tristate "Dallas/Maxim DS1305/DS1306"
  320. help
  321. Select this driver to get support for the Dallas/Maxim DS1305
  322. and DS1306 real time clock chips. These support a trickle
  323. charger, alarms, and NVRAM in addition to the clock.
  324. This driver can also be built as a module. If so, the module
  325. will be called rtc-ds1305.
  326. config RTC_DRV_DS1390
  327. tristate "Dallas/Maxim DS1390/93/94"
  328. help
  329. If you say yes here you get support for the
  330. Dallas/Maxim DS1390/93/94 chips.
  331. This driver only supports the RTC feature, and not other chip
  332. features such as alarms and trickle charging.
  333. This driver can also be built as a module. If so, the module
  334. will be called rtc-ds1390.
  335. config RTC_DRV_MAX6902
  336. tristate "Maxim MAX6902"
  337. help
  338. If you say yes here you will get support for the
  339. Maxim MAX6902 SPI RTC chip.
  340. This driver can also be built as a module. If so, the module
  341. will be called rtc-max6902.
  342. config RTC_DRV_R9701
  343. tristate "Epson RTC-9701JE"
  344. help
  345. If you say yes here you will get support for the
  346. Epson RTC-9701JE SPI RTC chip.
  347. This driver can also be built as a module. If so, the module
  348. will be called rtc-r9701.
  349. config RTC_DRV_RS5C348
  350. tristate "Ricoh RS5C348A/B"
  351. help
  352. If you say yes here you get support for the
  353. Ricoh RS5C348A and RS5C348B RTC chips.
  354. This driver can also be built as a module. If so, the module
  355. will be called rtc-rs5c348.
  356. config RTC_DRV_DS3234
  357. tristate "Maxim/Dallas DS3234"
  358. help
  359. If you say yes here you get support for the
  360. Maxim/Dallas DS3234 SPI RTC chip.
  361. This driver can also be built as a module. If so, the module
  362. will be called rtc-ds3234.
  363. config RTC_DRV_PCF2123
  364. tristate "NXP PCF2123"
  365. help
  366. If you say yes here you get support for the NXP PCF2123
  367. RTC chip.
  368. This driver can also be built as a module. If so, the module
  369. will be called rtc-pcf2123.
  370. endif # SPI_MASTER
  371. comment "Platform RTC drivers"
  372. # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
  373. # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
  374. # global rtc_lock ... it's not yet just another platform_device.
  375. config RTC_DRV_CMOS
  376. tristate "PC-style 'CMOS'"
  377. depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
  378. default y if X86
  379. help
  380. Say "yes" here to get direct support for the real time clock
  381. found in every PC or ACPI-based system, and some other boards.
  382. Specifically the original MC146818, compatibles like those in
  383. PC south bridges, the DS12887 or M48T86, some multifunction
  384. or LPC bus chips, and so on.
  385. Your system will need to define the platform device used by
  386. this driver, otherwise it won't be accessible. This means
  387. you can safely enable this driver if you don't know whether
  388. or not your board has this kind of hardware.
  389. This driver can also be built as a module. If so, the module
  390. will be called rtc-cmos.
  391. config RTC_DRV_VRTC
  392. tristate "Virtual RTC for Moorestown platforms"
  393. depends on X86_MRST
  394. default y if X86_MRST
  395. help
  396. Say "yes" here to get direct support for the real time clock
  397. found on Moorestown platforms. The VRTC is a emulated RTC that
  398. derives its clock source from a real RTC in the PMIC. The MC146818
  399. style programming interface is mostly conserved, but any
  400. updates are done via IPC calls to the system controller FW.
  401. config RTC_DRV_DS1216
  402. tristate "Dallas DS1216"
  403. depends on SNI_RM
  404. help
  405. If you say yes here you get support for the Dallas DS1216 RTC chips.
  406. config RTC_DRV_DS1286
  407. tristate "Dallas DS1286"
  408. help
  409. If you say yes here you get support for the Dallas DS1286 RTC chips.
  410. config RTC_DRV_DS1302
  411. tristate "Dallas DS1302"
  412. depends on SH_SECUREEDGE5410
  413. help
  414. If you say yes here you get support for the Dallas DS1302 RTC chips.
  415. config RTC_DRV_DS1511
  416. tristate "Dallas DS1511"
  417. depends on RTC_CLASS
  418. help
  419. If you say yes here you get support for the
  420. Dallas DS1511 timekeeping/watchdog chip.
  421. This driver can also be built as a module. If so, the module
  422. will be called rtc-ds1511.
  423. config RTC_DRV_DS1553
  424. tristate "Maxim/Dallas DS1553"
  425. help
  426. If you say yes here you get support for the
  427. Maxim/Dallas DS1553 timekeeping chip.
  428. This driver can also be built as a module. If so, the module
  429. will be called rtc-ds1553.
  430. config RTC_DRV_DS1742
  431. tristate "Maxim/Dallas DS1742/1743"
  432. help
  433. If you say yes here you get support for the
  434. Maxim/Dallas DS1742/1743 timekeeping chip.
  435. This driver can also be built as a module. If so, the module
  436. will be called rtc-ds1742.
  437. config RTC_DRV_EFI
  438. tristate "EFI RTC"
  439. depends on IA64
  440. help
  441. If you say yes here you will get support for the EFI
  442. Real Time Clock.
  443. This driver can also be built as a module. If so, the module
  444. will be called rtc-efi.
  445. config RTC_DRV_STK17TA8
  446. tristate "Simtek STK17TA8"
  447. depends on RTC_CLASS
  448. help
  449. If you say yes here you get support for the
  450. Simtek STK17TA8 timekeeping chip.
  451. This driver can also be built as a module. If so, the module
  452. will be called rtc-stk17ta8.
  453. config RTC_DRV_M48T86
  454. tristate "ST M48T86/Dallas DS12887"
  455. help
  456. If you say Y here you will get support for the
  457. ST M48T86 and Dallas DS12887 RTC chips.
  458. This driver can also be built as a module. If so, the module
  459. will be called rtc-m48t86.
  460. config RTC_DRV_M48T35
  461. tristate "ST M48T35"
  462. help
  463. If you say Y here you will get support for the
  464. ST M48T35 RTC chip.
  465. This driver can also be built as a module, if so, the module
  466. will be called "rtc-m48t35".
  467. config RTC_DRV_M48T59
  468. tristate "ST M48T59/M48T08/M48T02"
  469. help
  470. If you say Y here you will get support for the
  471. ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
  472. These chips are usually found in Sun SPARC and UltraSPARC
  473. workstations.
  474. This driver can also be built as a module, if so, the module
  475. will be called "rtc-m48t59".
  476. config RTC_DRV_MSM6242
  477. tristate "Oki MSM6242"
  478. help
  479. If you say yes here you get support for the Oki MSM6242
  480. timekeeping chip. It is used in some Amiga models (e.g. A2000).
  481. This driver can also be built as a module. If so, the module
  482. will be called rtc-msm6242.
  483. config RTC_DRV_IMXDI
  484. tristate "Freescale IMX DryIce Real Time Clock"
  485. depends on ARCH_MX25
  486. depends on RTC_CLASS
  487. help
  488. Support for Freescale IMX DryIce RTC
  489. This driver can also be built as a module, if so, the module
  490. will be called "rtc-imxdi".
  491. config RTC_MXC
  492. tristate "Freescale MXC Real Time Clock"
  493. depends on ARCH_MXC
  494. depends on RTC_CLASS
  495. help
  496. If you say yes here you get support for the Freescale MXC
  497. RTC module.
  498. This driver can also be built as a module, if so, the module
  499. will be called "rtc-mxc".
  500. config RTC_DRV_BQ4802
  501. tristate "TI BQ4802"
  502. help
  503. If you say Y here you will get support for the TI
  504. BQ4802 RTC chip.
  505. This driver can also be built as a module. If so, the module
  506. will be called rtc-bq4802.
  507. config RTC_DRV_RP5C01
  508. tristate "Ricoh RP5C01"
  509. help
  510. If you say yes here you get support for the Ricoh RP5C01
  511. timekeeping chip. It is used in some Amiga models (e.g. A3000
  512. and A4000).
  513. This driver can also be built as a module. If so, the module
  514. will be called rtc-rp5c01.
  515. config RTC_DRV_V3020
  516. tristate "EM Microelectronic V3020"
  517. help
  518. If you say yes here you will get support for the
  519. EM Microelectronic v3020 RTC chip.
  520. This driver can also be built as a module. If so, the module
  521. will be called rtc-v3020.
  522. config RTC_DRV_WM831X
  523. tristate "Wolfson Microelectronics WM831x RTC"
  524. depends on MFD_WM831X
  525. help
  526. If you say yes here you will get support for the RTC subsystem
  527. of the Wolfson Microelectronics WM831X series PMICs.
  528. This driver can also be built as a module. If so, the module
  529. will be called "rtc-wm831x".
  530. config RTC_DRV_WM8350
  531. tristate "Wolfson Microelectronics WM8350 RTC"
  532. depends on MFD_WM8350
  533. help
  534. If you say yes here you will get support for the RTC subsystem
  535. of the Wolfson Microelectronics WM8350.
  536. This driver can also be built as a module. If so, the module
  537. will be called "rtc-wm8350".
  538. config RTC_DRV_PCF50633
  539. depends on MFD_PCF50633
  540. tristate "NXP PCF50633 RTC"
  541. help
  542. If you say yes here you get support for the RTC subsystem of the
  543. NXP PCF50633 used in embedded systems.
  544. config RTC_DRV_AB3100
  545. tristate "ST-Ericsson AB3100 RTC"
  546. depends on AB3100_CORE
  547. default y if AB3100_CORE
  548. help
  549. Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
  550. support. This chip contains a battery- and capacitor-backed RTC.
  551. config RTC_DRV_AB8500
  552. tristate "ST-Ericsson AB8500 RTC"
  553. depends on AB8500_CORE
  554. help
  555. Select this to enable the ST-Ericsson AB8500 power management IC RTC
  556. support. This chip contains a battery- and capacitor-backed RTC.
  557. config RTC_DRV_NUC900
  558. tristate "NUC910/NUC920 RTC driver"
  559. depends on RTC_CLASS && ARCH_W90X900
  560. help
  561. If you say yes here you get support for the RTC subsystem of the
  562. NUC910/NUC920 used in embedded systems.
  563. comment "on-CPU RTC drivers"
  564. config RTC_DRV_DAVINCI
  565. tristate "TI DaVinci RTC"
  566. depends on ARCH_DAVINCI_DM365
  567. help
  568. If you say yes here you get support for the RTC on the
  569. DaVinci platforms (DM365).
  570. This driver can also be built as a module. If so, the module
  571. will be called rtc-davinci.
  572. config RTC_DRV_OMAP
  573. tristate "TI OMAP1"
  574. depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX
  575. help
  576. Say "yes" here to support the real time clock on TI OMAP1 and
  577. DA8xx/OMAP-L13x chips. This driver can also be built as a
  578. module called rtc-omap.
  579. config HAVE_S3C_RTC
  580. bool
  581. help
  582. This will include RTC support for Samsung SoCs. If
  583. you want to include RTC support for any machine, kindly
  584. select this in the respective mach-XXXX/Kconfig file.
  585. config RTC_DRV_S3C
  586. tristate "Samsung S3C series SoC RTC"
  587. depends on ARCH_S3C2410 || ARCH_S3C64XX || HAVE_S3C_RTC
  588. help
  589. RTC (Realtime Clock) driver for the clock inbuilt into the
  590. Samsung S3C24XX series of SoCs. This can provide periodic
  591. interrupt rates from 1Hz to 64Hz for user programs, and
  592. wakeup from Alarm.
  593. The driver currently supports the common features on all the
  594. S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
  595. and S3C2442.
  596. This driver can also be build as a module. If so, the module
  597. will be called rtc-s3c.
  598. config RTC_DRV_EP93XX
  599. tristate "Cirrus Logic EP93XX"
  600. depends on ARCH_EP93XX
  601. help
  602. If you say yes here you get support for the
  603. RTC embedded in the Cirrus Logic EP93XX processors.
  604. This driver can also be built as a module. If so, the module
  605. will be called rtc-ep93xx.
  606. config RTC_DRV_SA1100
  607. tristate "SA11x0/PXA2xx"
  608. depends on ARCH_SA1100 || ARCH_PXA
  609. help
  610. If you say Y here you will get access to the real time clock
  611. built into your SA11x0 or PXA2xx CPU.
  612. To compile this driver as a module, choose M here: the
  613. module will be called rtc-sa1100.
  614. config RTC_DRV_SH
  615. tristate "SuperH On-Chip RTC"
  616. depends on RTC_CLASS && SUPERH && HAVE_CLK
  617. help
  618. Say Y here to enable support for the on-chip RTC found in
  619. most SuperH processors.
  620. To compile this driver as a module, choose M here: the
  621. module will be called rtc-sh.
  622. config RTC_DRV_VR41XX
  623. tristate "NEC VR41XX"
  624. depends on CPU_VR41XX
  625. help
  626. If you say Y here you will get access to the real time clock
  627. built into your NEC VR41XX CPU.
  628. To compile this driver as a module, choose M here: the
  629. module will be called rtc-vr41xx.
  630. config RTC_DRV_PL030
  631. tristate "ARM AMBA PL030 RTC"
  632. depends on ARM_AMBA
  633. help
  634. If you say Y here you will get access to ARM AMBA
  635. PrimeCell PL030 RTC found on certain ARM SOCs.
  636. To compile this driver as a module, choose M here: the
  637. module will be called rtc-pl030.
  638. config RTC_DRV_PL031
  639. tristate "ARM AMBA PL031 RTC"
  640. depends on ARM_AMBA
  641. help
  642. If you say Y here you will get access to ARM AMBA
  643. PrimeCell PL031 RTC found on certain ARM SOCs.
  644. To compile this driver as a module, choose M here: the
  645. module will be called rtc-pl031.
  646. config RTC_DRV_AT32AP700X
  647. tristate "AT32AP700X series RTC"
  648. depends on PLATFORM_AT32AP
  649. help
  650. Driver for the internal RTC (Realtime Clock) on Atmel AVR32
  651. AT32AP700x family processors.
  652. config RTC_DRV_AT91RM9200
  653. tristate "AT91RM9200 or some AT91SAM9 RTC"
  654. depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
  655. help
  656. Driver for the internal RTC (Realtime Clock) module found on
  657. Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
  658. this is powered by the backup power supply.
  659. config RTC_DRV_AT91SAM9
  660. tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
  661. depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
  662. help
  663. RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
  664. (Real Time Timer). These timers are powered by the backup power
  665. supply (such as a small coin cell battery), but do not need to
  666. be used as RTCs.
  667. (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
  668. dedicated RTC module and leave the RTT available for other uses.)
  669. config RTC_DRV_AT91SAM9_RTT
  670. int
  671. range 0 1
  672. default 0
  673. prompt "RTT module Number" if ARCH_AT91SAM9263
  674. depends on RTC_DRV_AT91SAM9
  675. help
  676. More than one RTT module is available. You can choose which
  677. one will be used as an RTC. The default of zero is normally
  678. OK to use, though some systems use that for non-RTC purposes.
  679. config RTC_DRV_AT91SAM9_GPBR
  680. int
  681. range 0 3 if !ARCH_AT91SAM9263
  682. range 0 15 if ARCH_AT91SAM9263
  683. default 0
  684. prompt "Backup Register Number"
  685. depends on RTC_DRV_AT91SAM9
  686. help
  687. The RTC driver needs to use one of the General Purpose Backup
  688. Registers (GPBRs) as well as the RTT. You can choose which one
  689. will be used. The default of zero is normally OK to use, but
  690. on some systems other software needs to use that register.
  691. config RTC_DRV_AU1XXX
  692. tristate "Au1xxx Counter0 RTC support"
  693. depends on MIPS_ALCHEMY
  694. help
  695. This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
  696. counter) to be used as a RTC.
  697. This driver can also be built as a module. If so, the module
  698. will be called rtc-au1xxx.
  699. config RTC_DRV_BFIN
  700. tristate "Blackfin On-Chip RTC"
  701. depends on BLACKFIN && !BF561
  702. help
  703. If you say yes here you will get support for the
  704. Blackfin On-Chip Real Time Clock.
  705. This driver can also be built as a module. If so, the module
  706. will be called rtc-bfin.
  707. config RTC_DRV_RS5C313
  708. tristate "Ricoh RS5C313"
  709. depends on SH_LANDISK
  710. help
  711. If you say yes here you get support for the Ricoh RS5C313 RTC chips.
  712. config RTC_DRV_GENERIC
  713. tristate "Generic RTC support"
  714. # Please consider writing a new RTC driver instead of using the generic
  715. # RTC abstraction
  716. depends on PARISC || M68K || PPC || SUPERH32
  717. help
  718. Say Y or M here to enable RTC support on systems using the generic
  719. RTC abstraction. If you do not know what you are doing, you should
  720. just say Y.
  721. config RTC_DRV_PXA
  722. tristate "PXA27x/PXA3xx"
  723. depends on ARCH_PXA
  724. help
  725. If you say Y here you will get access to the real time clock
  726. built into your PXA27x or PXA3xx CPU.
  727. This RTC driver uses PXA RTC registers available since pxa27x
  728. series (RDxR, RYxR) instead of legacy RCNR, RTAR.
  729. config RTC_DRV_VT8500
  730. tristate "VIA/WonderMedia 85xx SoC RTC"
  731. depends on ARCH_VT8500
  732. help
  733. If you say Y here you will get access to the real time clock
  734. built into your VIA VT8500 SoC or its relatives.
  735. config RTC_DRV_SUN4V
  736. bool "SUN4V Hypervisor RTC"
  737. depends on SPARC64
  738. help
  739. If you say Y here you will get support for the Hypervisor
  740. based RTC on SUN4V systems.
  741. config RTC_DRV_STARFIRE
  742. bool "Starfire RTC"
  743. depends on SPARC64
  744. help
  745. If you say Y here you will get support for the RTC found on
  746. Starfire systems.
  747. config RTC_DRV_TX4939
  748. tristate "TX4939 SoC"
  749. depends on SOC_TX4939
  750. help
  751. Driver for the internal RTC (Realtime Clock) module found on
  752. Toshiba TX4939 SoC.
  753. config RTC_DRV_MV
  754. tristate "Marvell SoC RTC"
  755. depends on ARCH_KIRKWOOD || ARCH_DOVE
  756. help
  757. If you say yes here you will get support for the in-chip RTC
  758. that can be found in some of Marvell's SoC devices, such as
  759. the Kirkwood 88F6281 and 88F6192.
  760. This driver can also be built as a module. If so, the module
  761. will be called rtc-mv.
  762. config RTC_DRV_PS3
  763. tristate "PS3 RTC"
  764. depends on PPC_PS3
  765. help
  766. If you say yes here you will get support for the RTC on PS3.
  767. This driver can also be built as a module. If so, the module
  768. will be called rtc-ps3.
  769. config RTC_DRV_COH901331
  770. tristate "ST-Ericsson COH 901 331 RTC"
  771. depends on ARCH_U300
  772. help
  773. If you say Y here you will get access to ST-Ericsson
  774. COH 901 331 RTC clock found in some ST-Ericsson Mobile
  775. Platforms.
  776. This driver can also be built as a module. If so, the module
  777. will be called "rtc-coh901331".
  778. config RTC_DRV_STMP
  779. tristate "Freescale STMP3xxx RTC"
  780. depends on ARCH_STMP3XXX
  781. help
  782. If you say yes here you will get support for the onboard
  783. STMP3xxx RTC.
  784. This driver can also be built as a module. If so, the module
  785. will be called rtc-stmp3xxx.
  786. config RTC_DRV_PCAP
  787. tristate "PCAP RTC"
  788. depends on EZX_PCAP
  789. help
  790. If you say Y here you will get support for the RTC found on
  791. the PCAP2 ASIC used on some Motorola phones.
  792. config RTC_DRV_MC13XXX
  793. depends on MFD_MC13XXX
  794. tristate "Freescale MC13xxx RTC"
  795. help
  796. This enables support for the RTCs found on Freescale's PMICs
  797. MC13783 and MC13892.
  798. config RTC_DRV_MPC5121
  799. tristate "Freescale MPC5121 built-in RTC"
  800. depends on PPC_MPC512x && RTC_CLASS
  801. help
  802. If you say yes here you will get support for the
  803. built-in RTC MPC5121.
  804. This driver can also be built as a module. If so, the module
  805. will be called rtc-mpc5121.
  806. config RTC_DRV_JZ4740
  807. tristate "Ingenic JZ4740 SoC"
  808. depends on RTC_CLASS
  809. depends on MACH_JZ4740
  810. help
  811. If you say yes here you get support for the Ingenic JZ4740 SoC RTC
  812. controller.
  813. This driver can also be buillt as a module. If so, the module
  814. will be called rtc-jz4740.
  815. config RTC_DRV_LPC32XX
  816. depends on ARCH_LPC32XX
  817. tristate "NXP LPC32XX RTC"
  818. help
  819. This enables support for the NXP RTC in the LPC32XX
  820. This driver can also be buillt as a module. If so, the module
  821. will be called rtc-lpc32xx.
  822. config RTC_DRV_TEGRA
  823. tristate "NVIDIA Tegra Internal RTC driver"
  824. depends on RTC_CLASS && ARCH_TEGRA
  825. help
  826. If you say yes here you get support for the
  827. Tegra 200 series internal RTC module.
  828. This drive can also be built as a module. If so, the module
  829. will be called rtc-tegra.
  830. config RTC_DRV_TILE
  831. tristate "Tilera hypervisor RTC support"
  832. depends on TILE
  833. help
  834. Enable support for the Linux driver side of the Tilera
  835. hypervisor's real-time clock interface.
  836. endif # RTC_CLASS