Kconfig 36 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182118311841185118611871188118911901191119211931194119511961197119811991200120112021203120412051206120712081209121012111212121312141215121612171218121912201221122212231224122512261227122812291230123112321233123412351236123712381239124012411242124312441245124612471248124912501251125212531254125512561257125812591260126112621263126412651266126712681269127012711272127312741275127612771278127912801281128212831284128512861287
  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_LP8788
  168. tristate "TI LP8788 RTC driver"
  169. depends on MFD_LP8788
  170. help
  171. Say Y to enable support for the LP8788 RTC/ALARM driver.
  172. config RTC_DRV_MAX6900
  173. tristate "Maxim MAX6900"
  174. help
  175. If you say yes here you will get support for the
  176. Maxim MAX6900 I2C RTC chip.
  177. This driver can also be built as a module. If so, the module
  178. will be called rtc-max6900.
  179. config RTC_DRV_MAX8907
  180. tristate "Maxim MAX8907"
  181. depends on MFD_MAX8907
  182. help
  183. If you say yes here you will get support for the
  184. RTC of Maxim MAX8907 PMIC.
  185. This driver can also be built as a module. If so, the module
  186. will be called rtc-max8907.
  187. config RTC_DRV_MAX8925
  188. tristate "Maxim MAX8925"
  189. depends on MFD_MAX8925
  190. help
  191. If you say yes here you will get support for the
  192. RTC of Maxim MAX8925 PMIC.
  193. This driver can also be built as a module. If so, the module
  194. will be called rtc-max8925.
  195. config RTC_DRV_MAX8998
  196. tristate "Maxim MAX8998"
  197. depends on MFD_MAX8998
  198. help
  199. If you say yes here you will get support for the
  200. RTC of Maxim MAX8998 PMIC.
  201. This driver can also be built as a module. If so, the module
  202. will be called rtc-max8998.
  203. config RTC_DRV_MAX8997
  204. tristate "Maxim MAX8997"
  205. depends on MFD_MAX8997
  206. help
  207. If you say yes here you will get support for the
  208. RTC of Maxim MAX8997 PMIC.
  209. This driver can also be built as a module. If so, the module
  210. will be called rtc-max8997.
  211. config RTC_DRV_MAX77686
  212. tristate "Maxim MAX77686"
  213. depends on MFD_MAX77686
  214. help
  215. If you say yes here you will get support for the
  216. RTC of Maxim MAX77686 PMIC.
  217. This driver can also be built as a module. If so, the module
  218. will be called rtc-max77686.
  219. config RTC_DRV_RS5C372
  220. tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
  221. help
  222. If you say yes here you get support for the
  223. Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
  224. This driver can also be built as a module. If so, the module
  225. will be called rtc-rs5c372.
  226. config RTC_DRV_ISL1208
  227. tristate "Intersil ISL1208"
  228. help
  229. If you say yes here you get support for the
  230. Intersil ISL1208 RTC chip.
  231. This driver can also be built as a module. If so, the module
  232. will be called rtc-isl1208.
  233. config RTC_DRV_ISL12022
  234. tristate "Intersil ISL12022"
  235. help
  236. If you say yes here you get support for the
  237. Intersil ISL12022 RTC chip.
  238. This driver can also be built as a module. If so, the module
  239. will be called rtc-isl12022.
  240. config RTC_DRV_X1205
  241. tristate "Xicor/Intersil X1205"
  242. help
  243. If you say yes here you get support for the
  244. Xicor/Intersil X1205 RTC chip.
  245. This driver can also be built as a module. If so, the module
  246. will be called rtc-x1205.
  247. config RTC_DRV_PALMAS
  248. tristate "TI Palmas RTC driver"
  249. depends on MFD_PALMAS
  250. help
  251. If you say yes here you get support for the RTC of TI PALMA series PMIC
  252. chips.
  253. This driver can also be built as a module. If so, the module
  254. will be called rtc-palma.
  255. config RTC_DRV_PCF2127
  256. tristate "NXP PCF2127"
  257. help
  258. If you say yes here you get support for the NXP PCF2127/29 RTC
  259. chips.
  260. This driver can also be built as a module. If so, the module
  261. will be called rtc-pcf2127.
  262. config RTC_DRV_PCF8523
  263. tristate "NXP PCF8523"
  264. help
  265. If you say yes here you get support for the NXP PCF8523 RTC
  266. chips.
  267. This driver can also be built as a module. If so, the module
  268. will be called rtc-pcf8523.
  269. config RTC_DRV_PCF8563
  270. tristate "Philips PCF8563/Epson RTC8564"
  271. help
  272. If you say yes here you get support for the
  273. Philips PCF8563 RTC chip. The Epson RTC8564
  274. should work as well.
  275. This driver can also be built as a module. If so, the module
  276. will be called rtc-pcf8563.
  277. config RTC_DRV_PCF8583
  278. tristate "Philips PCF8583"
  279. help
  280. If you say yes here you get support for the Philips PCF8583
  281. RTC chip found on Acorn RiscPCs. This driver supports the
  282. platform specific method of retrieving the current year from
  283. the RTC's SRAM. It will work on other platforms with the same
  284. chip, but the year will probably have to be tweaked.
  285. This driver can also be built as a module. If so, the module
  286. will be called rtc-pcf8583.
  287. config RTC_DRV_M41T80
  288. tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
  289. help
  290. If you say Y here you will get support for the ST M41T60
  291. and M41T80 RTC chips series. Currently, the following chips are
  292. supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
  293. M41ST85, and M41ST87.
  294. This driver can also be built as a module. If so, the module
  295. will be called rtc-m41t80.
  296. config RTC_DRV_M41T80_WDT
  297. bool "ST M41T65/M41T80 series RTC watchdog timer"
  298. depends on RTC_DRV_M41T80
  299. help
  300. If you say Y here you will get support for the
  301. watchdog timer in the ST M41T60 and M41T80 RTC chips series.
  302. config RTC_DRV_BQ32K
  303. tristate "TI BQ32000"
  304. help
  305. If you say Y here you will get support for the TI
  306. BQ32000 I2C RTC chip.
  307. This driver can also be built as a module. If so, the module
  308. will be called rtc-bq32k.
  309. config RTC_DRV_DM355EVM
  310. tristate "TI DaVinci DM355 EVM RTC"
  311. depends on MFD_DM355EVM_MSP
  312. help
  313. Supports the RTC firmware in the MSP430 on the DM355 EVM.
  314. config RTC_DRV_TWL92330
  315. boolean "TI TWL92330/Menelaus"
  316. depends on MENELAUS
  317. help
  318. If you say yes here you get support for the RTC on the
  319. TWL92330 "Menelaus" power management chip, used with OMAP2
  320. platforms. The support is integrated with the rest of
  321. the Menelaus driver; it's not separate module.
  322. config RTC_DRV_TWL4030
  323. tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
  324. depends on TWL4030_CORE
  325. help
  326. If you say yes here you get support for the RTC on the
  327. TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
  328. This driver can also be built as a module. If so, the module
  329. will be called rtc-twl.
  330. config RTC_DRV_TPS6586X
  331. tristate "TI TPS6586X RTC driver"
  332. depends on MFD_TPS6586X
  333. help
  334. TI Power Management IC TPS6586X supports RTC functionality
  335. along with alarm. This driver supports the RTC driver for
  336. the TPS6586X RTC module.
  337. config RTC_DRV_TPS65910
  338. tristate "TI TPS65910 RTC driver"
  339. depends on RTC_CLASS && MFD_TPS65910
  340. help
  341. If you say yes here you get support for the RTC on the
  342. TPS65910 chips.
  343. This driver can also be built as a module. If so, the module
  344. will be called rtc-tps65910.
  345. config RTC_DRV_TPS80031
  346. tristate "TI TPS80031/TPS80032 RTC driver"
  347. depends on MFD_TPS80031
  348. help
  349. TI Power Management IC TPS80031 supports RTC functionality
  350. along with alarm. This driver supports the RTC driver for
  351. the TPS80031 RTC module.
  352. config RTC_DRV_RC5T583
  353. tristate "RICOH 5T583 RTC driver"
  354. depends on MFD_RC5T583
  355. help
  356. If you say yes here you get support for the RTC on the
  357. RICOH 5T583 chips.
  358. This driver can also be built as a module. If so, the module
  359. will be called rtc-rc5t583.
  360. config RTC_DRV_S35390A
  361. tristate "Seiko Instruments S-35390A"
  362. select BITREVERSE
  363. help
  364. If you say yes here you will get support for the Seiko
  365. Instruments S-35390A.
  366. This driver can also be built as a module. If so the module
  367. will be called rtc-s35390a.
  368. config RTC_DRV_FM3130
  369. tristate "Ramtron FM3130"
  370. help
  371. If you say Y here you will get support for the
  372. Ramtron FM3130 RTC chips.
  373. Ramtron FM3130 is a chip with two separate devices inside,
  374. RTC clock and FRAM. This driver provides only RTC functionality.
  375. This driver can also be built as a module. If so the module
  376. will be called rtc-fm3130.
  377. config RTC_DRV_RX8581
  378. tristate "Epson RX-8581"
  379. help
  380. If you say yes here you will get support for the Epson RX-8581.
  381. This driver can also be built as a module. If so the module
  382. will be called rtc-rx8581.
  383. config RTC_DRV_RX8025
  384. tristate "Epson RX-8025SA/NB"
  385. help
  386. If you say yes here you get support for the Epson
  387. RX-8025SA/NB RTC chips.
  388. This driver can also be built as a module. If so, the module
  389. will be called rtc-rx8025.
  390. config RTC_DRV_EM3027
  391. tristate "EM Microelectronic EM3027"
  392. help
  393. If you say yes here you get support for the EM
  394. Microelectronic EM3027 RTC chips.
  395. This driver can also be built as a module. If so, the module
  396. will be called rtc-em3027.
  397. config RTC_DRV_RV3029C2
  398. tristate "Micro Crystal RTC"
  399. help
  400. If you say yes here you get support for the Micro Crystal
  401. RV3029-C2 RTC chips.
  402. This driver can also be built as a module. If so, the module
  403. will be called rtc-rv3029c2.
  404. config RTC_DRV_S5M
  405. tristate "Samsung S5M series"
  406. depends on MFD_SEC_CORE
  407. help
  408. If you say yes here you will get support for the
  409. RTC of Samsung S5M PMIC series.
  410. This driver can also be built as a module. If so, the module
  411. will be called rtc-s5m.
  412. endif # I2C
  413. comment "SPI RTC drivers"
  414. if SPI_MASTER
  415. config RTC_DRV_M41T93
  416. tristate "ST M41T93"
  417. help
  418. If you say yes here you will get support for the
  419. ST M41T93 SPI RTC chip.
  420. This driver can also be built as a module. If so, the module
  421. will be called rtc-m41t93.
  422. config RTC_DRV_M41T94
  423. tristate "ST M41T94"
  424. help
  425. If you say yes here you will get support for the
  426. ST M41T94 SPI RTC chip.
  427. This driver can also be built as a module. If so, the module
  428. will be called rtc-m41t94.
  429. config RTC_DRV_DS1305
  430. tristate "Dallas/Maxim DS1305/DS1306"
  431. help
  432. Select this driver to get support for the Dallas/Maxim DS1305
  433. and DS1306 real time clock chips. These support a trickle
  434. charger, alarms, and NVRAM in addition to the clock.
  435. This driver can also be built as a module. If so, the module
  436. will be called rtc-ds1305.
  437. config RTC_DRV_DS1390
  438. tristate "Dallas/Maxim DS1390/93/94"
  439. help
  440. If you say yes here you get support for the
  441. Dallas/Maxim DS1390/93/94 chips.
  442. This driver only supports the RTC feature, and not other chip
  443. features such as alarms and trickle charging.
  444. This driver can also be built as a module. If so, the module
  445. will be called rtc-ds1390.
  446. config RTC_DRV_MAX6902
  447. tristate "Maxim MAX6902"
  448. help
  449. If you say yes here you will get support for the
  450. Maxim MAX6902 SPI RTC chip.
  451. This driver can also be built as a module. If so, the module
  452. will be called rtc-max6902.
  453. config RTC_DRV_R9701
  454. tristate "Epson RTC-9701JE"
  455. help
  456. If you say yes here you will get support for the
  457. Epson RTC-9701JE SPI RTC chip.
  458. This driver can also be built as a module. If so, the module
  459. will be called rtc-r9701.
  460. config RTC_DRV_RS5C348
  461. tristate "Ricoh RS5C348A/B"
  462. help
  463. If you say yes here you get support for the
  464. Ricoh RS5C348A and RS5C348B RTC chips.
  465. This driver can also be built as a module. If so, the module
  466. will be called rtc-rs5c348.
  467. config RTC_DRV_DS3234
  468. tristate "Maxim/Dallas DS3234"
  469. help
  470. If you say yes here you get support for the
  471. Maxim/Dallas DS3234 SPI RTC chip.
  472. This driver can also be built as a module. If so, the module
  473. will be called rtc-ds3234.
  474. config RTC_DRV_PCF2123
  475. tristate "NXP PCF2123"
  476. help
  477. If you say yes here you get support for the NXP PCF2123
  478. RTC chip.
  479. This driver can also be built as a module. If so, the module
  480. will be called rtc-pcf2123.
  481. config RTC_DRV_RX4581
  482. tristate "Epson RX-4581"
  483. help
  484. If you say yes here you will get support for the Epson RX-4581.
  485. This driver can also be built as a module. If so the module
  486. will be called rtc-rx4581.
  487. endif # SPI_MASTER
  488. comment "Platform RTC drivers"
  489. # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
  490. # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
  491. # global rtc_lock ... it's not yet just another platform_device.
  492. config RTC_DRV_CMOS
  493. tristate "PC-style 'CMOS'"
  494. depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
  495. default y if X86
  496. help
  497. Say "yes" here to get direct support for the real time clock
  498. found in every PC or ACPI-based system, and some other boards.
  499. Specifically the original MC146818, compatibles like those in
  500. PC south bridges, the DS12887 or M48T86, some multifunction
  501. or LPC bus chips, and so on.
  502. Your system will need to define the platform device used by
  503. this driver, otherwise it won't be accessible. This means
  504. you can safely enable this driver if you don't know whether
  505. or not your board has this kind of hardware.
  506. This driver can also be built as a module. If so, the module
  507. will be called rtc-cmos.
  508. config RTC_DRV_VRTC
  509. tristate "Virtual RTC for Intel MID platforms"
  510. depends on X86_INTEL_MID
  511. default y if X86_INTEL_MID
  512. help
  513. Say "yes" here to get direct support for the real time clock
  514. found on Moorestown platforms. The VRTC is a emulated RTC that
  515. derives its clock source from a real RTC in the PMIC. The MC146818
  516. style programming interface is mostly conserved, but any
  517. updates are done via IPC calls to the system controller FW.
  518. config RTC_DRV_DS1216
  519. tristate "Dallas DS1216"
  520. depends on SNI_RM
  521. help
  522. If you say yes here you get support for the Dallas DS1216 RTC chips.
  523. config RTC_DRV_DS1286
  524. tristate "Dallas DS1286"
  525. help
  526. If you say yes here you get support for the Dallas DS1286 RTC chips.
  527. config RTC_DRV_DS1302
  528. tristate "Dallas DS1302"
  529. depends on SH_SECUREEDGE5410
  530. help
  531. If you say yes here you get support for the Dallas DS1302 RTC chips.
  532. config RTC_DRV_DS1511
  533. tristate "Dallas DS1511"
  534. help
  535. If you say yes here you get support for the
  536. Dallas DS1511 timekeeping/watchdog chip.
  537. This driver can also be built as a module. If so, the module
  538. will be called rtc-ds1511.
  539. config RTC_DRV_DS1553
  540. tristate "Maxim/Dallas DS1553"
  541. help
  542. If you say yes here you get support for the
  543. Maxim/Dallas DS1553 timekeeping chip.
  544. This driver can also be built as a module. If so, the module
  545. will be called rtc-ds1553.
  546. config RTC_DRV_DS1742
  547. tristate "Maxim/Dallas DS1742/1743"
  548. help
  549. If you say yes here you get support for the
  550. Maxim/Dallas DS1742/1743 timekeeping chip.
  551. This driver can also be built as a module. If so, the module
  552. will be called rtc-ds1742.
  553. config RTC_DRV_DA9052
  554. tristate "Dialog DA9052/DA9053 RTC"
  555. depends on PMIC_DA9052
  556. help
  557. Say y here to support the RTC driver for Dialog Semiconductor
  558. DA9052-BC and DA9053-AA/Bx PMICs.
  559. config RTC_DRV_DA9055
  560. tristate "Dialog Semiconductor DA9055 RTC"
  561. depends on MFD_DA9055
  562. help
  563. If you say yes here you will get support for the
  564. RTC of the Dialog DA9055 PMIC.
  565. This driver can also be built as a module. If so, the module
  566. will be called rtc-da9055
  567. config RTC_DRV_EFI
  568. tristate "EFI RTC"
  569. depends on IA64
  570. help
  571. If you say yes here you will get support for the EFI
  572. Real Time Clock.
  573. This driver can also be built as a module. If so, the module
  574. will be called rtc-efi.
  575. config RTC_DRV_STK17TA8
  576. tristate "Simtek STK17TA8"
  577. help
  578. If you say yes here you get support for the
  579. Simtek STK17TA8 timekeeping chip.
  580. This driver can also be built as a module. If so, the module
  581. will be called rtc-stk17ta8.
  582. config RTC_DRV_M48T86
  583. tristate "ST M48T86/Dallas DS12887"
  584. help
  585. If you say Y here you will get support for the
  586. ST M48T86 and Dallas DS12887 RTC chips.
  587. This driver can also be built as a module. If so, the module
  588. will be called rtc-m48t86.
  589. config RTC_DRV_M48T35
  590. tristate "ST M48T35"
  591. help
  592. If you say Y here you will get support for the
  593. ST M48T35 RTC chip.
  594. This driver can also be built as a module, if so, the module
  595. will be called "rtc-m48t35".
  596. config RTC_DRV_M48T59
  597. tristate "ST M48T59/M48T08/M48T02"
  598. help
  599. If you say Y here you will get support for the
  600. ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
  601. These chips are usually found in Sun SPARC and UltraSPARC
  602. workstations.
  603. This driver can also be built as a module, if so, the module
  604. will be called "rtc-m48t59".
  605. config RTC_DRV_MSM6242
  606. tristate "Oki MSM6242"
  607. help
  608. If you say yes here you get support for the Oki MSM6242
  609. timekeeping chip. It is used in some Amiga models (e.g. A2000).
  610. This driver can also be built as a module. If so, the module
  611. will be called rtc-msm6242.
  612. config RTC_DRV_BQ4802
  613. tristate "TI BQ4802"
  614. help
  615. If you say Y here you will get support for the TI
  616. BQ4802 RTC chip.
  617. This driver can also be built as a module. If so, the module
  618. will be called rtc-bq4802.
  619. config RTC_DRV_RP5C01
  620. tristate "Ricoh RP5C01"
  621. help
  622. If you say yes here you get support for the Ricoh RP5C01
  623. timekeeping chip. It is used in some Amiga models (e.g. A3000
  624. and A4000).
  625. This driver can also be built as a module. If so, the module
  626. will be called rtc-rp5c01.
  627. config RTC_DRV_V3020
  628. tristate "EM Microelectronic V3020"
  629. help
  630. If you say yes here you will get support for the
  631. EM Microelectronic v3020 RTC chip.
  632. This driver can also be built as a module. If so, the module
  633. will be called rtc-v3020.
  634. config RTC_DRV_DS2404
  635. tristate "Dallas DS2404"
  636. help
  637. If you say yes here you get support for the
  638. Dallas DS2404 RTC chip.
  639. This driver can also be built as a module. If so, the module
  640. will be called rtc-ds2404.
  641. config RTC_DRV_WM831X
  642. tristate "Wolfson Microelectronics WM831x RTC"
  643. depends on MFD_WM831X
  644. help
  645. If you say yes here you will get support for the RTC subsystem
  646. of the Wolfson Microelectronics WM831X series PMICs.
  647. This driver can also be built as a module. If so, the module
  648. will be called "rtc-wm831x".
  649. config RTC_DRV_WM8350
  650. tristate "Wolfson Microelectronics WM8350 RTC"
  651. depends on MFD_WM8350
  652. help
  653. If you say yes here you will get support for the RTC subsystem
  654. of the Wolfson Microelectronics WM8350.
  655. This driver can also be built as a module. If so, the module
  656. will be called "rtc-wm8350".
  657. config RTC_DRV_SPEAR
  658. tristate "SPEAR ST RTC"
  659. depends on PLAT_SPEAR
  660. default y
  661. help
  662. If you say Y here you will get support for the RTC found on
  663. spear
  664. config RTC_DRV_PCF50633
  665. depends on MFD_PCF50633
  666. tristate "NXP PCF50633 RTC"
  667. help
  668. If you say yes here you get support for the RTC subsystem of the
  669. NXP PCF50633 used in embedded systems.
  670. config RTC_DRV_AB3100
  671. tristate "ST-Ericsson AB3100 RTC"
  672. depends on AB3100_CORE
  673. default y if AB3100_CORE
  674. help
  675. Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
  676. support. This chip contains a battery- and capacitor-backed RTC.
  677. config RTC_DRV_AB8500
  678. tristate "ST-Ericsson AB8500 RTC"
  679. depends on AB8500_CORE
  680. select RTC_INTF_DEV
  681. select RTC_INTF_DEV_UIE_EMUL
  682. help
  683. Select this to enable the ST-Ericsson AB8500 power management IC RTC
  684. support. This chip contains a battery- and capacitor-backed RTC.
  685. config RTC_DRV_NUC900
  686. tristate "NUC910/NUC920 RTC driver"
  687. depends on ARCH_W90X900
  688. help
  689. If you say yes here you get support for the RTC subsystem of the
  690. NUC910/NUC920 used in embedded systems.
  691. comment "on-CPU RTC drivers"
  692. config RTC_DRV_DAVINCI
  693. tristate "TI DaVinci RTC"
  694. depends on ARCH_DAVINCI_DM365
  695. help
  696. If you say yes here you get support for the RTC on the
  697. DaVinci platforms (DM365).
  698. This driver can also be built as a module. If so, the module
  699. will be called rtc-davinci.
  700. config RTC_DRV_IMXDI
  701. tristate "Freescale IMX DryIce Real Time Clock"
  702. depends on ARCH_MXC
  703. help
  704. Support for Freescale IMX DryIce RTC
  705. This driver can also be built as a module, if so, the module
  706. will be called "rtc-imxdi".
  707. config RTC_DRV_OMAP
  708. tristate "TI OMAP1"
  709. depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
  710. help
  711. Say "yes" here to support the on chip real time clock
  712. present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x.
  713. This driver can also be built as a module, if so, module
  714. will be called rtc-omap.
  715. config HAVE_S3C_RTC
  716. bool
  717. help
  718. This will include RTC support for Samsung SoCs. If
  719. you want to include RTC support for any machine, kindly
  720. select this in the respective mach-XXXX/Kconfig file.
  721. config RTC_DRV_S3C
  722. tristate "Samsung S3C series SoC RTC"
  723. depends on ARCH_S3C64XX || HAVE_S3C_RTC
  724. help
  725. RTC (Realtime Clock) driver for the clock inbuilt into the
  726. Samsung S3C24XX series of SoCs. This can provide periodic
  727. interrupt rates from 1Hz to 64Hz for user programs, and
  728. wakeup from Alarm.
  729. The driver currently supports the common features on all the
  730. S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
  731. and S3C2442.
  732. This driver can also be build as a module. If so, the module
  733. will be called rtc-s3c.
  734. config RTC_DRV_EP93XX
  735. tristate "Cirrus Logic EP93XX"
  736. depends on ARCH_EP93XX
  737. help
  738. If you say yes here you get support for the
  739. RTC embedded in the Cirrus Logic EP93XX processors.
  740. This driver can also be built as a module. If so, the module
  741. will be called rtc-ep93xx.
  742. config RTC_DRV_SA1100
  743. tristate "SA11x0/PXA2xx/PXA910"
  744. depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
  745. help
  746. If you say Y here you will get access to the real time clock
  747. built into your SA11x0 or PXA2xx CPU.
  748. To compile this driver as a module, choose M here: the
  749. module will be called rtc-sa1100.
  750. config RTC_DRV_SH
  751. tristate "SuperH On-Chip RTC"
  752. depends on SUPERH && HAVE_CLK
  753. help
  754. Say Y here to enable support for the on-chip RTC found in
  755. most SuperH processors.
  756. To compile this driver as a module, choose M here: the
  757. module will be called rtc-sh.
  758. config RTC_DRV_VR41XX
  759. tristate "NEC VR41XX"
  760. depends on CPU_VR41XX
  761. help
  762. If you say Y here you will get access to the real time clock
  763. built into your NEC VR41XX CPU.
  764. To compile this driver as a module, choose M here: the
  765. module will be called rtc-vr41xx.
  766. config RTC_DRV_PL030
  767. tristate "ARM AMBA PL030 RTC"
  768. depends on ARM_AMBA
  769. help
  770. If you say Y here you will get access to ARM AMBA
  771. PrimeCell PL030 RTC found on certain ARM SOCs.
  772. To compile this driver as a module, choose M here: the
  773. module will be called rtc-pl030.
  774. config RTC_DRV_PL031
  775. tristate "ARM AMBA PL031 RTC"
  776. depends on ARM_AMBA
  777. help
  778. If you say Y here you will get access to ARM AMBA
  779. PrimeCell PL031 RTC found on certain ARM SOCs.
  780. To compile this driver as a module, choose M here: the
  781. module will be called rtc-pl031.
  782. config RTC_DRV_AT32AP700X
  783. tristate "AT32AP700X series RTC"
  784. depends on PLATFORM_AT32AP
  785. help
  786. Driver for the internal RTC (Realtime Clock) on Atmel AVR32
  787. AT32AP700x family processors.
  788. config RTC_DRV_AT91RM9200
  789. tristate "AT91RM9200 or some AT91SAM9 RTC"
  790. depends on ARCH_AT91
  791. help
  792. Driver for the internal RTC (Realtime Clock) module found on
  793. Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
  794. this is powered by the backup power supply.
  795. config RTC_DRV_AT91SAM9
  796. tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
  797. depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
  798. help
  799. RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
  800. (Real Time Timer). These timers are powered by the backup power
  801. supply (such as a small coin cell battery), but do not need to
  802. be used as RTCs.
  803. (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
  804. dedicated RTC module and leave the RTT available for other uses.)
  805. config RTC_DRV_AT91SAM9_RTT
  806. int
  807. range 0 1
  808. default 0
  809. prompt "RTT module Number" if ARCH_AT91SAM9263
  810. depends on RTC_DRV_AT91SAM9
  811. help
  812. More than one RTT module is available. You can choose which
  813. one will be used as an RTC. The default of zero is normally
  814. OK to use, though some systems use that for non-RTC purposes.
  815. config RTC_DRV_AT91SAM9_GPBR
  816. int
  817. range 0 3 if !ARCH_AT91SAM9263
  818. range 0 15 if ARCH_AT91SAM9263
  819. default 0
  820. prompt "Backup Register Number"
  821. depends on RTC_DRV_AT91SAM9
  822. help
  823. The RTC driver needs to use one of the General Purpose Backup
  824. Registers (GPBRs) as well as the RTT. You can choose which one
  825. will be used. The default of zero is normally OK to use, but
  826. on some systems other software needs to use that register.
  827. config RTC_DRV_AU1XXX
  828. tristate "Au1xxx Counter0 RTC support"
  829. depends on MIPS_ALCHEMY
  830. help
  831. This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
  832. counter) to be used as a RTC.
  833. This driver can also be built as a module. If so, the module
  834. will be called rtc-au1xxx.
  835. config RTC_DRV_BFIN
  836. tristate "Blackfin On-Chip RTC"
  837. depends on BLACKFIN && !BF561
  838. help
  839. If you say yes here you will get support for the
  840. Blackfin On-Chip Real Time Clock.
  841. This driver can also be built as a module. If so, the module
  842. will be called rtc-bfin.
  843. config RTC_DRV_RS5C313
  844. tristate "Ricoh RS5C313"
  845. depends on SH_LANDISK
  846. help
  847. If you say yes here you get support for the Ricoh RS5C313 RTC chips.
  848. config RTC_DRV_GENERIC
  849. tristate "Generic RTC support"
  850. # Please consider writing a new RTC driver instead of using the generic
  851. # RTC abstraction
  852. depends on PARISC || M68K || PPC || SUPERH32
  853. help
  854. Say Y or M here to enable RTC support on systems using the generic
  855. RTC abstraction. If you do not know what you are doing, you should
  856. just say Y.
  857. config RTC_DRV_PXA
  858. tristate "PXA27x/PXA3xx"
  859. depends on ARCH_PXA
  860. help
  861. If you say Y here you will get access to the real time clock
  862. built into your PXA27x or PXA3xx CPU.
  863. This RTC driver uses PXA RTC registers available since pxa27x
  864. series (RDxR, RYxR) instead of legacy RCNR, RTAR.
  865. config RTC_DRV_VT8500
  866. tristate "VIA/WonderMedia 85xx SoC RTC"
  867. depends on ARCH_VT8500
  868. help
  869. If you say Y here you will get access to the real time clock
  870. built into your VIA VT8500 SoC or its relatives.
  871. config RTC_DRV_SUN4V
  872. bool "SUN4V Hypervisor RTC"
  873. depends on SPARC64
  874. help
  875. If you say Y here you will get support for the Hypervisor
  876. based RTC on SUN4V systems.
  877. config RTC_DRV_STARFIRE
  878. bool "Starfire RTC"
  879. depends on SPARC64
  880. help
  881. If you say Y here you will get support for the RTC found on
  882. Starfire systems.
  883. config RTC_DRV_TX4939
  884. tristate "TX4939 SoC"
  885. depends on SOC_TX4939
  886. help
  887. Driver for the internal RTC (Realtime Clock) module found on
  888. Toshiba TX4939 SoC.
  889. config RTC_DRV_MV
  890. tristate "Marvell SoC RTC"
  891. depends on ARCH_KIRKWOOD || ARCH_DOVE || ARCH_MVEBU
  892. help
  893. If you say yes here you will get support for the in-chip RTC
  894. that can be found in some of Marvell's SoC devices, such as
  895. the Kirkwood 88F6281 and 88F6192.
  896. This driver can also be built as a module. If so, the module
  897. will be called rtc-mv.
  898. config RTC_DRV_PS3
  899. tristate "PS3 RTC"
  900. depends on PPC_PS3
  901. help
  902. If you say yes here you will get support for the RTC on PS3.
  903. This driver can also be built as a module. If so, the module
  904. will be called rtc-ps3.
  905. config RTC_DRV_COH901331
  906. tristate "ST-Ericsson COH 901 331 RTC"
  907. depends on ARCH_U300
  908. help
  909. If you say Y here you will get access to ST-Ericsson
  910. COH 901 331 RTC clock found in some ST-Ericsson Mobile
  911. Platforms.
  912. This driver can also be built as a module. If so, the module
  913. will be called "rtc-coh901331".
  914. config RTC_DRV_STMP
  915. tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
  916. depends on ARCH_MXS
  917. help
  918. If you say yes here you will get support for the onboard
  919. STMP3xxx/i.MX23/i.MX28 RTC.
  920. This driver can also be built as a module. If so, the module
  921. will be called rtc-stmp3xxx.
  922. config RTC_DRV_PCAP
  923. tristate "PCAP RTC"
  924. depends on EZX_PCAP
  925. help
  926. If you say Y here you will get support for the RTC found on
  927. the PCAP2 ASIC used on some Motorola phones.
  928. config RTC_DRV_MC13XXX
  929. depends on MFD_MC13XXX
  930. tristate "Freescale MC13xxx RTC"
  931. help
  932. This enables support for the RTCs found on Freescale's PMICs
  933. MC13783 and MC13892.
  934. config RTC_DRV_MPC5121
  935. tristate "Freescale MPC5121 built-in RTC"
  936. depends on PPC_MPC512x || PPC_MPC52xx
  937. help
  938. If you say yes here you will get support for the
  939. built-in RTC on MPC5121 or on MPC5200.
  940. This driver can also be built as a module. If so, the module
  941. will be called rtc-mpc5121.
  942. config RTC_DRV_JZ4740
  943. tristate "Ingenic JZ4740 SoC"
  944. depends on MACH_JZ4740
  945. help
  946. If you say yes here you get support for the Ingenic JZ4740 SoC RTC
  947. controller.
  948. This driver can also be buillt as a module. If so, the module
  949. will be called rtc-jz4740.
  950. config RTC_DRV_LPC32XX
  951. depends on ARCH_LPC32XX
  952. tristate "NXP LPC32XX RTC"
  953. help
  954. This enables support for the NXP RTC in the LPC32XX
  955. This driver can also be buillt as a module. If so, the module
  956. will be called rtc-lpc32xx.
  957. config RTC_DRV_PM8XXX
  958. tristate "Qualcomm PMIC8XXX RTC"
  959. depends on MFD_PM8XXX
  960. help
  961. If you say yes here you get support for the
  962. Qualcomm PMIC8XXX RTC.
  963. To compile this driver as a module, choose M here: the
  964. module will be called rtc-pm8xxx.
  965. config RTC_DRV_TEGRA
  966. tristate "NVIDIA Tegra Internal RTC driver"
  967. depends on ARCH_TEGRA
  968. help
  969. If you say yes here you get support for the
  970. Tegra 200 series internal RTC module.
  971. This drive can also be built as a module. If so, the module
  972. will be called rtc-tegra.
  973. config RTC_DRV_TILE
  974. tristate "Tilera hypervisor RTC support"
  975. depends on TILE
  976. help
  977. Enable support for the Linux driver side of the Tilera
  978. hypervisor's real-time clock interface.
  979. config RTC_DRV_PUV3
  980. tristate "PKUnity v3 RTC support"
  981. depends on ARCH_PUV3
  982. help
  983. This enables support for the RTC in the PKUnity-v3 SoCs.
  984. This drive can also be built as a module. If so, the module
  985. will be called rtc-puv3.
  986. config RTC_DRV_LOONGSON1
  987. tristate "loongson1 RTC support"
  988. depends on MACH_LOONGSON1
  989. help
  990. This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
  991. counter) to be used as a RTC.
  992. This driver can also be built as a module. If so, the module
  993. will be called rtc-ls1x.
  994. config RTC_DRV_MXC
  995. tristate "Freescale MXC Real Time Clock"
  996. depends on ARCH_MXC
  997. help
  998. If you say yes here you get support for the Freescale MXC
  999. RTC module.
  1000. This driver can also be built as a module, if so, the module
  1001. will be called "rtc-mxc".
  1002. config RTC_DRV_SNVS
  1003. tristate "Freescale SNVS RTC support"
  1004. depends on HAS_IOMEM
  1005. depends on OF
  1006. help
  1007. If you say yes here you get support for the Freescale SNVS
  1008. Low Power (LP) RTC module.
  1009. This driver can also be built as a module, if so, the module
  1010. will be called "rtc-snvs".
  1011. config RTC_DRV_SIRFSOC
  1012. tristate "SiRFSOC RTC"
  1013. depends on ARCH_SIRF
  1014. help
  1015. Say "yes" here to support the real time clock on SiRF SOC chips.
  1016. This driver can also be built as a module called rtc-sirfsoc.
  1017. config RTC_DRV_MOXART
  1018. tristate "MOXA ART RTC"
  1019. help
  1020. If you say yes here you get support for the MOXA ART
  1021. RTC module.
  1022. This driver can also be built as a module. If so, the module
  1023. will be called rtc-moxart
  1024. comment "HID Sensor RTC drivers"
  1025. config RTC_DRV_HID_SENSOR_TIME
  1026. tristate "HID Sensor Time"
  1027. depends on USB_HID
  1028. select IIO
  1029. select HID_SENSOR_HUB
  1030. select HID_SENSOR_IIO_COMMON
  1031. help
  1032. Say yes here to build support for the HID Sensors of type Time.
  1033. This drivers makes such sensors available as RTCs.
  1034. If this driver is compiled as a module, it will be named
  1035. rtc-hid-sensor-time.
  1036. endif # RTC_CLASS