Kconfig 37 KB

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