Kconfig 39 KB

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