Kconfig 40 KB

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