Kconfig 27 KB

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