Kconfig 41 KB

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