Kconfig 33 KB

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