Kconfig 33 KB

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