Kconfig 25 KB

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