Kconfig 26 KB

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