Kconfig 28 KB

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