Kconfig 25 KB

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