Kconfig 46 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091109210931094109510961097109810991100110111021103110411051106110711081109111011111112111311141115111611171118111911201121112211231124112511261127112811291130113111321133113411351136113711381139114011411142114311441145114611471148114911501151115211531154115511561157115811591160116111621163116411651166116711681169117011711172117311741175117611771178117911801181118211831184118511861187118811891190119111921193119411951196119711981199120012011202120312041205120612071208120912101211121212131214121512161217121812191220122112221223122412251226122712281229123012311232123312341235123612371238123912401241124212431244124512461247124812491250125112521253125412551256125712581259126012611262126312641265126612671268126912701271127212731274127512761277127812791280128112821283128412851286128712881289129012911292129312941295129612971298129913001301130213031304130513061307130813091310131113121313131413151316131713181319132013211322132313241325132613271328132913301331133213331334133513361337133813391340134113421343134413451346134713481349135013511352135313541355135613571358135913601361136213631364136513661367136813691370137113721373137413751376137713781379138013811382138313841385138613871388138913901391139213931394139513961397139813991400140114021403140414051406140714081409141014111412141314141415141614171418141914201421142214231424142514261427142814291430143114321433143414351436143714381439144014411442144314441445144614471448144914501451145214531454145514561457145814591460146114621463146414651466146714681469147014711472147314741475147614771478147914801481148214831484148514861487148814891490149114921493149414951496149714981499150015011502150315041505150615071508150915101511151215131514151515161517151815191520152115221523152415251526152715281529153015311532153315341535153615371538153915401541154215431544154515461547154815491550155115521553155415551556155715581559156015611562156315641565156615671568156915701571157215731574157515761577157815791580158115821583158415851586158715881589159015911592159315941595159615971598159916001601160216031604160516061607160816091610161116121613161416151616161716181619162016211622162316241625162616271628162916301631
  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_HCTOSYS_DEVICE
  24. string "RTC used to set the system time"
  25. depends on RTC_HCTOSYS
  26. default "rtc0"
  27. help
  28. The RTC device that will be used to (re)initialize the system
  29. clock, usually rtc0. Initialization is done when the system
  30. starts up, and when it resumes from a low power state. This
  31. device should record time in UTC, since the kernel won't do
  32. timezone correction.
  33. The driver for this RTC device must be loaded before late_initcall
  34. functions run, so it must usually be statically linked.
  35. This clock should be battery-backed, so that it reads the correct
  36. time when the system boots from a power-off state. Otherwise, your
  37. system will need an external clock source (like an NTP server).
  38. If the clock you specify here is not battery backed, it may still
  39. be useful to reinitialize system time when resuming from system
  40. sleep states. Do not specify an RTC here unless it stays powered
  41. during all this system's supported sleep states.
  42. config RTC_SYSTOHC
  43. bool "Set the RTC time based on NTP synchronization"
  44. default y
  45. help
  46. If you say yes here, the system time (wall clock) will be stored
  47. in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
  48. minutes if userspace reports synchronized NTP status.
  49. config RTC_SYSTOHC_DEVICE
  50. string "RTC used to synchronize NTP adjustment"
  51. depends on RTC_SYSTOHC
  52. default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS
  53. default "rtc0"
  54. help
  55. The RTC device used for NTP synchronization. The main difference
  56. between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this
  57. one can sleep when setting time, because it runs in the workqueue
  58. context.
  59. config RTC_DEBUG
  60. bool "RTC debug support"
  61. help
  62. Say yes here to enable debugging support in the RTC framework
  63. and individual RTC drivers.
  64. comment "RTC interfaces"
  65. config RTC_INTF_SYSFS
  66. bool "/sys/class/rtc/rtcN (sysfs)"
  67. depends on SYSFS
  68. default RTC_CLASS
  69. help
  70. Say yes here if you want to use your RTCs using sysfs interfaces,
  71. /sys/class/rtc/rtc0 through /sys/.../rtcN.
  72. If unsure, say Y.
  73. config RTC_INTF_PROC
  74. bool "/proc/driver/rtc (procfs for rtcN)"
  75. depends on PROC_FS
  76. default RTC_CLASS
  77. help
  78. Say yes here if you want to use your system clock RTC through
  79. the proc interface, /proc/driver/rtc.
  80. Other RTCs will not be available through that API.
  81. If there is no RTC for the system clock, then the first RTC(rtc0)
  82. is used by default.
  83. If unsure, say Y.
  84. config RTC_INTF_DEV
  85. bool "/dev/rtcN (character devices)"
  86. default RTC_CLASS
  87. help
  88. Say yes here if you want to use your RTCs using the /dev
  89. interfaces, which "udev" sets up as /dev/rtc0 through
  90. /dev/rtcN.
  91. You may want to set up a symbolic link so one of these
  92. can be accessed as /dev/rtc, which is a name
  93. expected by "hwclock" and some other programs. Recent
  94. versions of "udev" are known to set up the symlink for you.
  95. If unsure, say Y.
  96. config RTC_INTF_DEV_UIE_EMUL
  97. bool "RTC UIE emulation on dev interface"
  98. depends on RTC_INTF_DEV
  99. help
  100. Provides an emulation for RTC_UIE if the underlying rtc chip
  101. driver does not expose RTC_UIE ioctls. Those requests generate
  102. once-per-second update interrupts, used for synchronization.
  103. The emulation code will read the time from the hardware
  104. clock several times per second, please enable this option
  105. only if you know that you really need it.
  106. config RTC_DRV_TEST
  107. tristate "Test driver/device"
  108. help
  109. If you say yes here you get support for the
  110. RTC test driver. It's a software RTC which can be
  111. used to test the RTC subsystem APIs. It gets
  112. the time from the system clock.
  113. You want this driver only if you are doing development
  114. on the RTC subsystem. Please read the source code
  115. for further details.
  116. This driver can also be built as a module. If so, the module
  117. will be called rtc-test.
  118. comment "I2C RTC drivers"
  119. depends on I2C
  120. if I2C
  121. config RTC_DRV_88PM860X
  122. tristate "Marvell 88PM860x"
  123. depends on MFD_88PM860X
  124. help
  125. If you say yes here you get support for RTC function in Marvell
  126. 88PM860x chips.
  127. This driver can also be built as a module. If so, the module
  128. will be called rtc-88pm860x.
  129. config RTC_DRV_88PM80X
  130. tristate "Marvell 88PM80x"
  131. depends on MFD_88PM800
  132. help
  133. If you say yes here you get support for RTC function in Marvell
  134. 88PM80x chips.
  135. This driver can also be built as a module. If so, the module
  136. will be called rtc-88pm80x.
  137. config RTC_DRV_ABB5ZES3
  138. select REGMAP_I2C
  139. tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
  140. help
  141. If you say yes here you get support for the Abracon
  142. AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
  143. This driver can also be built as a module. If so, the module
  144. will be called rtc-ab-b5ze-s3.
  145. config RTC_DRV_ABX80X
  146. tristate "Abracon ABx80x"
  147. help
  148. If you say yes here you get support for Abracon AB080X and AB180X
  149. families of ultra-low-power battery- and capacitor-backed real-time
  150. clock chips.
  151. This driver can also be built as a module. If so, the module
  152. will be called rtc-abx80x.
  153. config RTC_DRV_AS3722
  154. tristate "ams AS3722 RTC driver"
  155. depends on MFD_AS3722
  156. help
  157. If you say yes here you get support for the RTC of ams AS3722 PMIC
  158. chips.
  159. This driver can also be built as a module. If so, the module
  160. will be called rtc-as3722.
  161. config RTC_DRV_DS1307
  162. tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
  163. help
  164. If you say yes here you get support for various compatible RTC
  165. chips (often with battery backup) connected with I2C. This driver
  166. should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
  167. EPSON RX-8025 and probably other chips. In some cases the RTC
  168. must already have been initialized (by manufacturing or a
  169. bootloader).
  170. The first seven registers on these chips hold an RTC, and other
  171. registers may add features such as NVRAM, a trickle charger for
  172. the RTC/NVRAM backup power, and alarms. NVRAM is visible in
  173. sysfs, but other chip features may not be available.
  174. This driver can also be built as a module. If so, the module
  175. will be called rtc-ds1307.
  176. config RTC_DRV_DS1374
  177. tristate "Dallas/Maxim DS1374"
  178. help
  179. If you say yes here you get support for Dallas Semiconductor
  180. DS1374 real-time clock chips. If an interrupt is associated
  181. with the device, the alarm functionality is supported.
  182. This driver can also be built as a module. If so, the module
  183. will be called rtc-ds1374.
  184. config RTC_DRV_DS1374_WDT
  185. bool "Dallas/Maxim DS1374 watchdog timer"
  186. depends on RTC_DRV_DS1374
  187. help
  188. If you say Y here you will get support for the
  189. watchdog timer in the Dallas Semiconductor DS1374
  190. real-time clock chips.
  191. config RTC_DRV_DS1672
  192. tristate "Dallas/Maxim DS1672"
  193. help
  194. If you say yes here you get support for the
  195. Dallas/Maxim DS1672 timekeeping chip.
  196. This driver can also be built as a module. If so, the module
  197. will be called rtc-ds1672.
  198. config RTC_DRV_DS3232
  199. tristate "Dallas/Maxim DS3232"
  200. help
  201. If you say yes here you get support for Dallas Semiconductor
  202. DS3232 real-time clock chips. If an interrupt is associated
  203. with the device, the alarm functionality is supported.
  204. This driver can also be built as a module. If so, the module
  205. will be called rtc-ds3232.
  206. config RTC_DRV_HYM8563
  207. tristate "Haoyu Microelectronics HYM8563"
  208. depends on OF
  209. help
  210. Say Y to enable support for the HYM8563 I2C RTC chip. Apart
  211. from the usual rtc functions it provides a clock output of
  212. up to 32kHz.
  213. This driver can also be built as a module. If so, the module
  214. will be called rtc-hym8563.
  215. config RTC_DRV_LP8788
  216. tristate "TI LP8788 RTC driver"
  217. depends on MFD_LP8788
  218. help
  219. Say Y to enable support for the LP8788 RTC/ALARM driver.
  220. config RTC_DRV_MAX6900
  221. tristate "Maxim MAX6900"
  222. help
  223. If you say yes here you will get support for the
  224. Maxim MAX6900 I2C RTC chip.
  225. This driver can also be built as a module. If so, the module
  226. will be called rtc-max6900.
  227. config RTC_DRV_MAX8907
  228. tristate "Maxim MAX8907"
  229. depends on MFD_MAX8907
  230. help
  231. If you say yes here you will get support for the
  232. RTC of Maxim MAX8907 PMIC.
  233. This driver can also be built as a module. If so, the module
  234. will be called rtc-max8907.
  235. config RTC_DRV_MAX8925
  236. tristate "Maxim MAX8925"
  237. depends on MFD_MAX8925
  238. help
  239. If you say yes here you will get support for the
  240. RTC of Maxim MAX8925 PMIC.
  241. This driver can also be built as a module. If so, the module
  242. will be called rtc-max8925.
  243. config RTC_DRV_MAX8998
  244. tristate "Maxim MAX8998"
  245. depends on MFD_MAX8998
  246. help
  247. If you say yes here you will get support for the
  248. RTC of Maxim MAX8998 PMIC.
  249. This driver can also be built as a module. If so, the module
  250. will be called rtc-max8998.
  251. config RTC_DRV_MAX8997
  252. tristate "Maxim MAX8997"
  253. depends on MFD_MAX8997
  254. help
  255. If you say yes here you will get support for the
  256. RTC of Maxim MAX8997 PMIC.
  257. This driver can also be built as a module. If so, the module
  258. will be called rtc-max8997.
  259. config RTC_DRV_MAX77686
  260. tristate "Maxim MAX77686"
  261. depends on MFD_MAX77686
  262. help
  263. If you say yes here you will get support for the
  264. RTC of Maxim MAX77686 PMIC.
  265. This driver can also be built as a module. If so, the module
  266. will be called rtc-max77686.
  267. config RTC_DRV_RK808
  268. tristate "Rockchip RK808 RTC"
  269. depends on MFD_RK808
  270. help
  271. If you say yes here you will get support for the
  272. RTC of RK808 PMIC.
  273. This driver can also be built as a module. If so, the module
  274. will be called rk808-rtc.
  275. config RTC_DRV_MAX77802
  276. tristate "Maxim 77802 RTC"
  277. depends on MFD_MAX77686
  278. help
  279. If you say yes here you will get support for the
  280. RTC of Maxim MAX77802 PMIC.
  281. This driver can also be built as a module. If so, the module
  282. will be called rtc-max77802.
  283. config RTC_DRV_RS5C372
  284. tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
  285. help
  286. If you say yes here you get support for the
  287. Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
  288. This driver can also be built as a module. If so, the module
  289. will be called rtc-rs5c372.
  290. config RTC_DRV_ISL1208
  291. tristate "Intersil ISL1208"
  292. help
  293. If you say yes here you get support for the
  294. Intersil ISL1208 RTC chip.
  295. This driver can also be built as a module. If so, the module
  296. will be called rtc-isl1208.
  297. config RTC_DRV_ISL12022
  298. tristate "Intersil ISL12022"
  299. help
  300. If you say yes here you get support for the
  301. Intersil ISL12022 RTC chip.
  302. This driver can also be built as a module. If so, the module
  303. will be called rtc-isl12022.
  304. config RTC_DRV_ISL12057
  305. select REGMAP_I2C
  306. tristate "Intersil ISL12057"
  307. help
  308. If you say yes here you get support for the Intersil ISL12057
  309. I2C RTC chip.
  310. This driver can also be built as a module. If so, the module
  311. will be called rtc-isl12057.
  312. config RTC_DRV_X1205
  313. tristate "Xicor/Intersil X1205"
  314. help
  315. If you say yes here you get support for the
  316. Xicor/Intersil X1205 RTC chip.
  317. This driver can also be built as a module. If so, the module
  318. will be called rtc-x1205.
  319. config RTC_DRV_PALMAS
  320. tristate "TI Palmas RTC driver"
  321. depends on MFD_PALMAS
  322. help
  323. If you say yes here you get support for the RTC of TI PALMA series PMIC
  324. chips.
  325. This driver can also be built as a module. If so, the module
  326. will be called rtc-palma.
  327. config RTC_DRV_PCF2127
  328. tristate "NXP PCF2127"
  329. help
  330. If you say yes here you get support for the NXP PCF2127/29 RTC
  331. chips.
  332. This driver can also be built as a module. If so, the module
  333. will be called rtc-pcf2127.
  334. config RTC_DRV_PCF8523
  335. tristate "NXP PCF8523"
  336. help
  337. If you say yes here you get support for the NXP PCF8523 RTC
  338. chips.
  339. This driver can also be built as a module. If so, the module
  340. will be called rtc-pcf8523.
  341. config RTC_DRV_PCF8563
  342. tristate "Philips PCF8563/Epson RTC8564"
  343. help
  344. If you say yes here you get support for the
  345. Philips PCF8563 RTC chip. The Epson RTC8564
  346. should work as well.
  347. This driver can also be built as a module. If so, the module
  348. will be called rtc-pcf8563.
  349. config RTC_DRV_PCF85063
  350. tristate "nxp PCF85063"
  351. help
  352. If you say yes here you get support for the PCF85063 RTC chip
  353. This driver can also be built as a module. If so, the module
  354. will be called rtc-pcf85063.
  355. config RTC_DRV_PCF8583
  356. tristate "Philips PCF8583"
  357. help
  358. If you say yes here you get support for the Philips PCF8583
  359. RTC chip found on Acorn RiscPCs. This driver supports the
  360. platform specific method of retrieving the current year from
  361. the RTC's SRAM. It will work on other platforms with the same
  362. chip, but the year will probably have to be tweaked.
  363. This driver can also be built as a module. If so, the module
  364. will be called rtc-pcf8583.
  365. config RTC_DRV_M41T80
  366. tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
  367. help
  368. If you say Y here you will get support for the ST M41T60
  369. and M41T80 RTC chips series. Currently, the following chips are
  370. supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
  371. M41ST85, M41ST87, and MicroCrystal RV4162.
  372. This driver can also be built as a module. If so, the module
  373. will be called rtc-m41t80.
  374. config RTC_DRV_M41T80_WDT
  375. bool "ST M41T65/M41T80 series RTC watchdog timer"
  376. depends on RTC_DRV_M41T80
  377. help
  378. If you say Y here you will get support for the
  379. watchdog timer in the ST M41T60 and M41T80 RTC chips series.
  380. config RTC_DRV_BQ32K
  381. tristate "TI BQ32000"
  382. help
  383. If you say Y here you will get support for the TI
  384. BQ32000 I2C RTC chip.
  385. This driver can also be built as a module. If so, the module
  386. will be called rtc-bq32k.
  387. config RTC_DRV_DM355EVM
  388. tristate "TI DaVinci DM355 EVM RTC"
  389. depends on MFD_DM355EVM_MSP
  390. help
  391. Supports the RTC firmware in the MSP430 on the DM355 EVM.
  392. config RTC_DRV_TWL92330
  393. bool "TI TWL92330/Menelaus"
  394. depends on MENELAUS
  395. help
  396. If you say yes here you get support for the RTC on the
  397. TWL92330 "Menelaus" power management chip, used with OMAP2
  398. platforms. The support is integrated with the rest of
  399. the Menelaus driver; it's not separate module.
  400. config RTC_DRV_TWL4030
  401. tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
  402. depends on TWL4030_CORE
  403. help
  404. If you say yes here you get support for the RTC on the
  405. TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
  406. This driver can also be built as a module. If so, the module
  407. will be called rtc-twl.
  408. config RTC_DRV_TPS6586X
  409. tristate "TI TPS6586X RTC driver"
  410. depends on MFD_TPS6586X
  411. help
  412. TI Power Management IC TPS6586X supports RTC functionality
  413. along with alarm. This driver supports the RTC driver for
  414. the TPS6586X RTC module.
  415. config RTC_DRV_TPS65910
  416. tristate "TI TPS65910 RTC driver"
  417. depends on RTC_CLASS && MFD_TPS65910
  418. help
  419. If you say yes here you get support for the RTC on the
  420. TPS65910 chips.
  421. This driver can also be built as a module. If so, the module
  422. will be called rtc-tps65910.
  423. config RTC_DRV_TPS80031
  424. tristate "TI TPS80031/TPS80032 RTC driver"
  425. depends on MFD_TPS80031
  426. help
  427. TI Power Management IC TPS80031 supports RTC functionality
  428. along with alarm. This driver supports the RTC driver for
  429. the TPS80031 RTC module.
  430. config RTC_DRV_RC5T583
  431. tristate "RICOH 5T583 RTC driver"
  432. depends on MFD_RC5T583
  433. help
  434. If you say yes here you get support for the RTC on the
  435. RICOH 5T583 chips.
  436. This driver can also be built as a module. If so, the module
  437. will be called rtc-rc5t583.
  438. config RTC_DRV_S35390A
  439. tristate "Seiko Instruments S-35390A"
  440. select BITREVERSE
  441. help
  442. If you say yes here you will get support for the Seiko
  443. Instruments S-35390A.
  444. This driver can also be built as a module. If so the module
  445. will be called rtc-s35390a.
  446. config RTC_DRV_FM3130
  447. tristate "Ramtron FM3130"
  448. help
  449. If you say Y here you will get support for the
  450. Ramtron FM3130 RTC chips.
  451. Ramtron FM3130 is a chip with two separate devices inside,
  452. RTC clock and FRAM. This driver provides only RTC functionality.
  453. This driver can also be built as a module. If so the module
  454. will be called rtc-fm3130.
  455. config RTC_DRV_RX8581
  456. tristate "Epson RX-8581"
  457. help
  458. If you say yes here you will get support for the Epson RX-8581.
  459. This driver can also be built as a module. If so the module
  460. will be called rtc-rx8581.
  461. config RTC_DRV_RX8025
  462. tristate "Epson RX-8025SA/NB"
  463. help
  464. If you say yes here you get support for the Epson
  465. RX-8025SA/NB RTC chips.
  466. This driver can also be built as a module. If so, the module
  467. will be called rtc-rx8025.
  468. config RTC_DRV_EM3027
  469. tristate "EM Microelectronic EM3027"
  470. help
  471. If you say yes here you get support for the EM
  472. Microelectronic EM3027 RTC chips.
  473. This driver can also be built as a module. If so, the module
  474. will be called rtc-em3027.
  475. config RTC_DRV_RV3029C2
  476. tristate "Micro Crystal RTC"
  477. help
  478. If you say yes here you get support for the Micro Crystal
  479. RV3029-C2 RTC chips.
  480. This driver can also be built as a module. If so, the module
  481. will be called rtc-rv3029c2.
  482. config RTC_DRV_RV8803
  483. tristate "Micro Crystal RV8803"
  484. help
  485. If you say yes here you get support for the Micro Crystal
  486. RV8803 RTC chips.
  487. This driver can also be built as a module. If so, the module
  488. will be called rtc-rv8803.
  489. config RTC_DRV_S5M
  490. tristate "Samsung S2M/S5M series"
  491. depends on MFD_SEC_CORE
  492. help
  493. If you say yes here you will get support for the
  494. RTC of Samsung S2MPS14 and S5M PMIC series.
  495. This driver can also be built as a module. If so, the module
  496. will be called rtc-s5m.
  497. endif # I2C
  498. comment "SPI RTC drivers"
  499. if SPI_MASTER
  500. config RTC_DRV_M41T93
  501. tristate "ST M41T93"
  502. help
  503. If you say yes here you will get support for the
  504. ST M41T93 SPI RTC chip.
  505. This driver can also be built as a module. If so, the module
  506. will be called rtc-m41t93.
  507. config RTC_DRV_M41T94
  508. tristate "ST M41T94"
  509. help
  510. If you say yes here you will get support for the
  511. ST M41T94 SPI RTC chip.
  512. This driver can also be built as a module. If so, the module
  513. will be called rtc-m41t94.
  514. config RTC_DRV_DS1305
  515. tristate "Dallas/Maxim DS1305/DS1306"
  516. help
  517. Select this driver to get support for the Dallas/Maxim DS1305
  518. and DS1306 real time clock chips. These support a trickle
  519. charger, alarms, and NVRAM in addition to the clock.
  520. This driver can also be built as a module. If so, the module
  521. will be called rtc-ds1305.
  522. config RTC_DRV_DS1343
  523. select REGMAP_SPI
  524. tristate "Dallas/Maxim DS1343/DS1344"
  525. help
  526. If you say yes here you get support for the
  527. Dallas/Maxim DS1343 and DS1344 real time clock chips.
  528. Support for trickle charger, alarm is provided.
  529. This driver can also be built as a module. If so, the module
  530. will be called rtc-ds1343.
  531. config RTC_DRV_DS1347
  532. tristate "Dallas/Maxim DS1347"
  533. help
  534. If you say yes here you get support for the
  535. Dallas/Maxim DS1347 chips.
  536. This driver only supports the RTC feature, and not other chip
  537. features such as alarms.
  538. This driver can also be built as a module. If so, the module
  539. will be called rtc-ds1347.
  540. config RTC_DRV_DS1390
  541. tristate "Dallas/Maxim DS1390/93/94"
  542. help
  543. If you say yes here you get support for the
  544. Dallas/Maxim DS1390/93/94 chips.
  545. This driver supports the RTC feature and trickle charging but not
  546. other chip features such as alarms.
  547. This driver can also be built as a module. If so, the module
  548. will be called rtc-ds1390.
  549. config RTC_DRV_MAX6902
  550. tristate "Maxim MAX6902"
  551. help
  552. If you say yes here you will get support for the
  553. Maxim MAX6902 SPI RTC chip.
  554. This driver can also be built as a module. If so, the module
  555. will be called rtc-max6902.
  556. config RTC_DRV_R9701
  557. tristate "Epson RTC-9701JE"
  558. help
  559. If you say yes here you will get support for the
  560. Epson RTC-9701JE SPI RTC chip.
  561. This driver can also be built as a module. If so, the module
  562. will be called rtc-r9701.
  563. config RTC_DRV_RS5C348
  564. tristate "Ricoh RS5C348A/B"
  565. help
  566. If you say yes here you get support for the
  567. Ricoh RS5C348A and RS5C348B RTC chips.
  568. This driver can also be built as a module. If so, the module
  569. will be called rtc-rs5c348.
  570. config RTC_DRV_DS3234
  571. tristate "Maxim/Dallas DS3234"
  572. help
  573. If you say yes here you get support for the
  574. Maxim/Dallas DS3234 SPI RTC chip.
  575. This driver can also be built as a module. If so, the module
  576. will be called rtc-ds3234.
  577. config RTC_DRV_PCF2123
  578. tristate "NXP PCF2123"
  579. help
  580. If you say yes here you get support for the NXP PCF2123
  581. RTC chip.
  582. This driver can also be built as a module. If so, the module
  583. will be called rtc-pcf2123.
  584. config RTC_DRV_RX4581
  585. tristate "Epson RX-4581"
  586. help
  587. If you say yes here you will get support for the Epson RX-4581.
  588. This driver can also be built as a module. If so the module
  589. will be called rtc-rx4581.
  590. config RTC_DRV_MCP795
  591. tristate "Microchip MCP795"
  592. help
  593. If you say yes here you will get support for the Microchip MCP795.
  594. This driver can also be built as a module. If so the module
  595. will be called rtc-mcp795.
  596. endif # SPI_MASTER
  597. comment "Platform RTC drivers"
  598. # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
  599. # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
  600. # global rtc_lock ... it's not yet just another platform_device.
  601. config RTC_DRV_CMOS
  602. tristate "PC-style 'CMOS'"
  603. depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
  604. default y if X86
  605. help
  606. Say "yes" here to get direct support for the real time clock
  607. found in every PC or ACPI-based system, and some other boards.
  608. Specifically the original MC146818, compatibles like those in
  609. PC south bridges, the DS12887 or M48T86, some multifunction
  610. or LPC bus chips, and so on.
  611. Your system will need to define the platform device used by
  612. this driver, otherwise it won't be accessible. This means
  613. you can safely enable this driver if you don't know whether
  614. or not your board has this kind of hardware.
  615. This driver can also be built as a module. If so, the module
  616. will be called rtc-cmos.
  617. config RTC_DRV_ALPHA
  618. bool "Alpha PC-style CMOS"
  619. depends on ALPHA
  620. default y
  621. help
  622. Direct support for the real-time clock found on every Alpha
  623. system, specifically MC146818 compatibles. If in doubt, say Y.
  624. config RTC_DRV_VRTC
  625. tristate "Virtual RTC for Intel MID platforms"
  626. depends on X86_INTEL_MID
  627. default y if X86_INTEL_MID
  628. help
  629. Say "yes" here to get direct support for the real time clock
  630. found on Moorestown platforms. The VRTC is a emulated RTC that
  631. derives its clock source from a real RTC in the PMIC. The MC146818
  632. style programming interface is mostly conserved, but any
  633. updates are done via IPC calls to the system controller FW.
  634. config RTC_DRV_DS1216
  635. tristate "Dallas DS1216"
  636. depends on SNI_RM
  637. help
  638. If you say yes here you get support for the Dallas DS1216 RTC chips.
  639. config RTC_DRV_DS1286
  640. tristate "Dallas DS1286"
  641. depends on HAS_IOMEM
  642. help
  643. If you say yes here you get support for the Dallas DS1286 RTC chips.
  644. config RTC_DRV_DS1302
  645. tristate "Dallas DS1302"
  646. depends on SH_SECUREEDGE5410
  647. help
  648. If you say yes here you get support for the Dallas DS1302 RTC chips.
  649. config RTC_DRV_DS1511
  650. tristate "Dallas DS1511"
  651. depends on HAS_IOMEM
  652. help
  653. If you say yes here you get support for the
  654. Dallas DS1511 timekeeping/watchdog chip.
  655. This driver can also be built as a module. If so, the module
  656. will be called rtc-ds1511.
  657. config RTC_DRV_DS1553
  658. tristate "Maxim/Dallas DS1553"
  659. depends on HAS_IOMEM
  660. help
  661. If you say yes here you get support for the
  662. Maxim/Dallas DS1553 timekeeping chip.
  663. This driver can also be built as a module. If so, the module
  664. will be called rtc-ds1553.
  665. config RTC_DRV_DS1685_FAMILY
  666. tristate "Dallas/Maxim DS1685 Family"
  667. help
  668. If you say yes here you get support for the Dallas/Maxim DS1685
  669. family of real time chips. This family includes the DS1685/DS1687,
  670. DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
  671. DS17885/DS17887 chips.
  672. This driver can also be built as a module. If so, the module
  673. will be called rtc-ds1685.
  674. choice
  675. prompt "Subtype"
  676. depends on RTC_DRV_DS1685_FAMILY
  677. default RTC_DRV_DS1685
  678. config RTC_DRV_DS1685
  679. bool "DS1685/DS1687"
  680. help
  681. This enables support for the Dallas/Maxim DS1685/DS1687 real time
  682. clock chip.
  683. This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
  684. systems, as well as EPPC-405-UC modules by electronic system design
  685. GmbH.
  686. config RTC_DRV_DS1689
  687. bool "DS1689/DS1693"
  688. help
  689. This enables support for the Dallas/Maxim DS1689/DS1693 real time
  690. clock chip.
  691. This is an older RTC chip, supplanted by the DS1685/DS1687 above,
  692. which supports a few minor features such as Vcc, Vbat, and Power
  693. Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
  694. It also works for the even older DS1688/DS1691 RTC chips, which are
  695. virtually the same and carry the same model number. Both chips
  696. have 114 bytes of user NVRAM.
  697. config RTC_DRV_DS17285
  698. bool "DS17285/DS17287"
  699. help
  700. This enables support for the Dallas/Maxim DS17285/DS17287 real time
  701. clock chip.
  702. This chip features 2kb of extended NV-SRAM. It may possibly be
  703. found in some SGI O2 systems (rare).
  704. config RTC_DRV_DS17485
  705. bool "DS17485/DS17487"
  706. help
  707. This enables support for the Dallas/Maxim DS17485/DS17487 real time
  708. clock chip.
  709. This chip features 4kb of extended NV-SRAM.
  710. config RTC_DRV_DS17885
  711. bool "DS17885/DS17887"
  712. help
  713. This enables support for the Dallas/Maxim DS17885/DS17887 real time
  714. clock chip.
  715. This chip features 8kb of extended NV-SRAM.
  716. endchoice
  717. config RTC_DS1685_PROC_REGS
  718. bool "Display register values in /proc"
  719. depends on RTC_DRV_DS1685_FAMILY && PROC_FS
  720. help
  721. Enable this to display a readout of all of the RTC registers in
  722. /proc/drivers/rtc. Keep in mind that this can potentially lead
  723. to lost interrupts, as reading Control Register C will clear
  724. all pending IRQ flags.
  725. Unless you are debugging this driver, choose N.
  726. config RTC_DS1685_SYSFS_REGS
  727. bool "SysFS access to RTC register bits"
  728. depends on RTC_DRV_DS1685_FAMILY && SYSFS
  729. help
  730. Enable this to provide access to the RTC control register bits
  731. in /sys. Some of the bits are read-write, others are read-only.
  732. Keep in mind that reading Control C's bits automatically clears
  733. all pending IRQ flags - this can cause lost interrupts.
  734. If you know that you need access to these bits, choose Y, Else N.
  735. config RTC_DRV_DS1742
  736. tristate "Maxim/Dallas DS1742/1743"
  737. depends on HAS_IOMEM
  738. help
  739. If you say yes here you get support for the
  740. Maxim/Dallas DS1742/1743 timekeeping chip.
  741. This driver can also be built as a module. If so, the module
  742. will be called rtc-ds1742.
  743. config RTC_DRV_DS2404
  744. tristate "Maxim/Dallas DS2404"
  745. help
  746. If you say yes here you get support for the
  747. Dallas DS2404 RTC chip.
  748. This driver can also be built as a module. If so, the module
  749. will be called rtc-ds2404.
  750. config RTC_DRV_DA9052
  751. tristate "Dialog DA9052/DA9053 RTC"
  752. depends on PMIC_DA9052
  753. help
  754. Say y here to support the RTC driver for Dialog Semiconductor
  755. DA9052-BC and DA9053-AA/Bx PMICs.
  756. config RTC_DRV_DA9055
  757. tristate "Dialog Semiconductor DA9055 RTC"
  758. depends on MFD_DA9055
  759. help
  760. If you say yes here you will get support for the
  761. RTC of the Dialog DA9055 PMIC.
  762. This driver can also be built as a module. If so, the module
  763. will be called rtc-da9055
  764. config RTC_DRV_DA9063
  765. tristate "Dialog Semiconductor DA9063/DA9062 RTC"
  766. depends on MFD_DA9063 || MFD_DA9062
  767. help
  768. If you say yes here you will get support for the RTC subsystem
  769. for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
  770. This driver can also be built as a module. If so, the module
  771. will be called "rtc-da9063".
  772. config RTC_DRV_EFI
  773. tristate "EFI RTC"
  774. depends on EFI && !X86
  775. help
  776. If you say yes here you will get support for the EFI
  777. Real Time Clock.
  778. This driver can also be built as a module. If so, the module
  779. will be called rtc-efi.
  780. config RTC_DRV_STK17TA8
  781. tristate "Simtek STK17TA8"
  782. depends on HAS_IOMEM
  783. help
  784. If you say yes here you get support for the
  785. Simtek STK17TA8 timekeeping chip.
  786. This driver can also be built as a module. If so, the module
  787. will be called rtc-stk17ta8.
  788. config RTC_DRV_M48T86
  789. tristate "ST M48T86/Dallas DS12887"
  790. help
  791. If you say Y here you will get support for the
  792. ST M48T86 and Dallas DS12887 RTC chips.
  793. This driver can also be built as a module. If so, the module
  794. will be called rtc-m48t86.
  795. config RTC_DRV_M48T35
  796. tristate "ST M48T35"
  797. depends on HAS_IOMEM
  798. help
  799. If you say Y here you will get support for the
  800. ST M48T35 RTC chip.
  801. This driver can also be built as a module, if so, the module
  802. will be called "rtc-m48t35".
  803. config RTC_DRV_M48T59
  804. tristate "ST M48T59/M48T08/M48T02"
  805. depends on HAS_IOMEM
  806. help
  807. If you say Y here you will get support for the
  808. ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
  809. These chips are usually found in Sun SPARC and UltraSPARC
  810. workstations.
  811. This driver can also be built as a module, if so, the module
  812. will be called "rtc-m48t59".
  813. config RTC_DRV_MSM6242
  814. tristate "Oki MSM6242"
  815. depends on HAS_IOMEM
  816. help
  817. If you say yes here you get support for the Oki MSM6242
  818. timekeeping chip. It is used in some Amiga models (e.g. A2000).
  819. This driver can also be built as a module. If so, the module
  820. will be called rtc-msm6242.
  821. config RTC_DRV_BQ4802
  822. tristate "TI BQ4802"
  823. depends on HAS_IOMEM
  824. help
  825. If you say Y here you will get support for the TI
  826. BQ4802 RTC chip.
  827. This driver can also be built as a module. If so, the module
  828. will be called rtc-bq4802.
  829. config RTC_DRV_RP5C01
  830. tristate "Ricoh RP5C01"
  831. depends on HAS_IOMEM
  832. help
  833. If you say yes here you get support for the Ricoh RP5C01
  834. timekeeping chip. It is used in some Amiga models (e.g. A3000
  835. and A4000).
  836. This driver can also be built as a module. If so, the module
  837. will be called rtc-rp5c01.
  838. config RTC_DRV_V3020
  839. tristate "EM Microelectronic V3020"
  840. help
  841. If you say yes here you will get support for the
  842. EM Microelectronic v3020 RTC chip.
  843. This driver can also be built as a module. If so, the module
  844. will be called rtc-v3020.
  845. config RTC_DRV_WM831X
  846. tristate "Wolfson Microelectronics WM831x RTC"
  847. depends on MFD_WM831X
  848. help
  849. If you say yes here you will get support for the RTC subsystem
  850. of the Wolfson Microelectronics WM831X series PMICs.
  851. This driver can also be built as a module. If so, the module
  852. will be called "rtc-wm831x".
  853. config RTC_DRV_WM8350
  854. tristate "Wolfson Microelectronics WM8350 RTC"
  855. depends on MFD_WM8350
  856. help
  857. If you say yes here you will get support for the RTC subsystem
  858. of the Wolfson Microelectronics WM8350.
  859. This driver can also be built as a module. If so, the module
  860. will be called "rtc-wm8350".
  861. config RTC_DRV_SPEAR
  862. tristate "SPEAR ST RTC"
  863. depends on PLAT_SPEAR
  864. default y
  865. help
  866. If you say Y here you will get support for the RTC found on
  867. spear
  868. config RTC_DRV_PCF50633
  869. depends on MFD_PCF50633
  870. tristate "NXP PCF50633 RTC"
  871. help
  872. If you say yes here you get support for the RTC subsystem of the
  873. NXP PCF50633 used in embedded systems.
  874. config RTC_DRV_AB3100
  875. tristate "ST-Ericsson AB3100 RTC"
  876. depends on AB3100_CORE
  877. default y if AB3100_CORE
  878. help
  879. Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
  880. support. This chip contains a battery- and capacitor-backed RTC.
  881. config RTC_DRV_AB8500
  882. tristate "ST-Ericsson AB8500 RTC"
  883. depends on AB8500_CORE
  884. select RTC_INTF_DEV
  885. select RTC_INTF_DEV_UIE_EMUL
  886. help
  887. Select this to enable the ST-Ericsson AB8500 power management IC RTC
  888. support. This chip contains a battery- and capacitor-backed RTC.
  889. config RTC_DRV_NUC900
  890. tristate "NUC910/NUC920 RTC driver"
  891. depends on ARCH_W90X900
  892. help
  893. If you say yes here you get support for the RTC subsystem of the
  894. NUC910/NUC920 used in embedded systems.
  895. config RTC_DRV_OPAL
  896. tristate "IBM OPAL RTC driver"
  897. depends on PPC_POWERNV
  898. default y
  899. help
  900. If you say yes here you get support for the PowerNV platform RTC
  901. driver based on OPAL interfaces.
  902. This driver can also be built as a module. If so, the module
  903. will be called rtc-opal.
  904. config RTC_DRV_ZYNQMP
  905. tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
  906. depends on OF
  907. help
  908. If you say yes here you get support for the RTC controller found on
  909. Xilinx Zynq Ultrascale+ MPSoC.
  910. comment "on-CPU RTC drivers"
  911. config RTC_DRV_DAVINCI
  912. tristate "TI DaVinci RTC"
  913. depends on ARCH_DAVINCI_DM365
  914. help
  915. If you say yes here you get support for the RTC on the
  916. DaVinci platforms (DM365).
  917. This driver can also be built as a module. If so, the module
  918. will be called rtc-davinci.
  919. config RTC_DRV_DIGICOLOR
  920. tristate "Conexant Digicolor RTC"
  921. depends on ARCH_DIGICOLOR
  922. help
  923. If you say yes here you get support for the RTC on Conexant
  924. Digicolor platforms. This currently includes the CX92755 SoC.
  925. This driver can also be built as a module. If so, the module
  926. will be called rtc-digicolor.
  927. config RTC_DRV_IMXDI
  928. tristate "Freescale IMX DryIce Real Time Clock"
  929. depends on ARCH_MXC
  930. help
  931. Support for Freescale IMX DryIce RTC
  932. This driver can also be built as a module, if so, the module
  933. will be called "rtc-imxdi".
  934. config RTC_DRV_OMAP
  935. tristate "TI OMAP Real Time Clock"
  936. depends on ARCH_OMAP || ARCH_DAVINCI
  937. help
  938. Say "yes" here to support the on chip real time clock
  939. present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
  940. This driver can also be built as a module, if so, module
  941. will be called rtc-omap.
  942. config HAVE_S3C_RTC
  943. bool
  944. help
  945. This will include RTC support for Samsung SoCs. If
  946. you want to include RTC support for any machine, kindly
  947. select this in the respective mach-XXXX/Kconfig file.
  948. config RTC_DRV_S3C
  949. tristate "Samsung S3C series SoC RTC"
  950. depends on ARCH_S3C64XX || HAVE_S3C_RTC
  951. help
  952. RTC (Realtime Clock) driver for the clock inbuilt into the
  953. Samsung S3C24XX series of SoCs. This can provide periodic
  954. interrupt rates from 1Hz to 64Hz for user programs, and
  955. wakeup from Alarm.
  956. The driver currently supports the common features on all the
  957. S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
  958. and S3C2442.
  959. This driver can also be build as a module. If so, the module
  960. will be called rtc-s3c.
  961. config RTC_DRV_EP93XX
  962. tristate "Cirrus Logic EP93XX"
  963. depends on ARCH_EP93XX
  964. help
  965. If you say yes here you get support for the
  966. RTC embedded in the Cirrus Logic EP93XX processors.
  967. This driver can also be built as a module. If so, the module
  968. will be called rtc-ep93xx.
  969. config RTC_DRV_SA1100
  970. tristate "SA11x0/PXA2xx/PXA910"
  971. depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
  972. help
  973. If you say Y here you will get access to the real time clock
  974. built into your SA11x0 or PXA2xx CPU.
  975. To compile this driver as a module, choose M here: the
  976. module will be called rtc-sa1100.
  977. config RTC_DRV_SH
  978. tristate "SuperH On-Chip RTC"
  979. depends on SUPERH && HAVE_CLK
  980. help
  981. Say Y here to enable support for the on-chip RTC found in
  982. most SuperH processors.
  983. To compile this driver as a module, choose M here: the
  984. module will be called rtc-sh.
  985. config RTC_DRV_VR41XX
  986. tristate "NEC VR41XX"
  987. depends on CPU_VR41XX
  988. help
  989. If you say Y here you will get access to the real time clock
  990. built into your NEC VR41XX CPU.
  991. To compile this driver as a module, choose M here: the
  992. module will be called rtc-vr41xx.
  993. config RTC_DRV_PL030
  994. tristate "ARM AMBA PL030 RTC"
  995. depends on ARM_AMBA
  996. help
  997. If you say Y here you will get access to ARM AMBA
  998. PrimeCell PL030 RTC found on certain ARM SOCs.
  999. To compile this driver as a module, choose M here: the
  1000. module will be called rtc-pl030.
  1001. config RTC_DRV_PL031
  1002. tristate "ARM AMBA PL031 RTC"
  1003. depends on ARM_AMBA
  1004. help
  1005. If you say Y here you will get access to ARM AMBA
  1006. PrimeCell PL031 RTC found on certain ARM SOCs.
  1007. To compile this driver as a module, choose M here: the
  1008. module will be called rtc-pl031.
  1009. config RTC_DRV_AT32AP700X
  1010. tristate "AT32AP700X series RTC"
  1011. depends on PLATFORM_AT32AP
  1012. help
  1013. Driver for the internal RTC (Realtime Clock) on Atmel AVR32
  1014. AT32AP700x family processors.
  1015. config RTC_DRV_AT91RM9200
  1016. tristate "AT91RM9200 or some AT91SAM9 RTC"
  1017. depends on ARCH_AT91
  1018. help
  1019. Driver for the internal RTC (Realtime Clock) module found on
  1020. Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
  1021. this is powered by the backup power supply.
  1022. config RTC_DRV_AT91SAM9
  1023. tristate "AT91SAM9 RTT as RTC"
  1024. depends on ARCH_AT91
  1025. select MFD_SYSCON
  1026. help
  1027. Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
  1028. can be used as an RTC thanks to the backup power supply (e.g. a
  1029. small coin cell battery) which keeps this block and the GPBR
  1030. (General Purpose Backup Registers) block powered when the device
  1031. is shutdown.
  1032. Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
  1033. probably want to use the real RTC block instead of the "RTT as an
  1034. RTC" driver.
  1035. config RTC_DRV_AU1XXX
  1036. tristate "Au1xxx Counter0 RTC support"
  1037. depends on MIPS_ALCHEMY
  1038. help
  1039. This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
  1040. counter) to be used as a RTC.
  1041. This driver can also be built as a module. If so, the module
  1042. will be called rtc-au1xxx.
  1043. config RTC_DRV_BFIN
  1044. tristate "Blackfin On-Chip RTC"
  1045. depends on BLACKFIN && !BF561
  1046. help
  1047. If you say yes here you will get support for the
  1048. Blackfin On-Chip Real Time Clock.
  1049. This driver can also be built as a module. If so, the module
  1050. will be called rtc-bfin.
  1051. config RTC_DRV_RS5C313
  1052. tristate "Ricoh RS5C313"
  1053. depends on SH_LANDISK
  1054. help
  1055. If you say yes here you get support for the Ricoh RS5C313 RTC chips.
  1056. config RTC_DRV_GENERIC
  1057. tristate "Generic RTC support"
  1058. # Please consider writing a new RTC driver instead of using the generic
  1059. # RTC abstraction
  1060. depends on PARISC || M68K || PPC || SUPERH32
  1061. help
  1062. Say Y or M here to enable RTC support on systems using the generic
  1063. RTC abstraction. If you do not know what you are doing, you should
  1064. just say Y.
  1065. config RTC_DRV_PXA
  1066. tristate "PXA27x/PXA3xx"
  1067. depends on ARCH_PXA
  1068. select RTC_DRV_SA1100
  1069. help
  1070. If you say Y here you will get access to the real time clock
  1071. built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
  1072. consisting of an SA1100 compatible RTC and the extended PXA RTC.
  1073. This RTC driver uses PXA RTC registers available since pxa27x
  1074. series (RDxR, RYxR) instead of legacy RCNR, RTAR.
  1075. config RTC_DRV_VT8500
  1076. tristate "VIA/WonderMedia 85xx SoC RTC"
  1077. depends on ARCH_VT8500
  1078. help
  1079. If you say Y here you will get access to the real time clock
  1080. built into your VIA VT8500 SoC or its relatives.
  1081. config RTC_DRV_SUN4V
  1082. bool "SUN4V Hypervisor RTC"
  1083. depends on SPARC64
  1084. help
  1085. If you say Y here you will get support for the Hypervisor
  1086. based RTC on SUN4V systems.
  1087. config RTC_DRV_SUN6I
  1088. tristate "Allwinner A31 RTC"
  1089. depends on MACH_SUN6I || MACH_SUN8I
  1090. help
  1091. If you say Y here you will get support for the RTC found on
  1092. Allwinner A31.
  1093. config RTC_DRV_SUNXI
  1094. tristate "Allwinner sun4i/sun7i RTC"
  1095. depends on MACH_SUN4I || MACH_SUN7I
  1096. help
  1097. If you say Y here you will get support for the RTC found on
  1098. Allwinner A10/A20.
  1099. config RTC_DRV_STARFIRE
  1100. bool "Starfire RTC"
  1101. depends on SPARC64
  1102. help
  1103. If you say Y here you will get support for the RTC found on
  1104. Starfire systems.
  1105. config RTC_DRV_TX4939
  1106. tristate "TX4939 SoC"
  1107. depends on SOC_TX4939
  1108. help
  1109. Driver for the internal RTC (Realtime Clock) module found on
  1110. Toshiba TX4939 SoC.
  1111. config RTC_DRV_MV
  1112. tristate "Marvell SoC RTC"
  1113. depends on ARCH_DOVE || ARCH_MVEBU
  1114. help
  1115. If you say yes here you will get support for the in-chip RTC
  1116. that can be found in some of Marvell's SoC devices, such as
  1117. the Kirkwood 88F6281 and 88F6192.
  1118. This driver can also be built as a module. If so, the module
  1119. will be called rtc-mv.
  1120. config RTC_DRV_ARMADA38X
  1121. tristate "Armada 38x Marvell SoC RTC"
  1122. depends on ARCH_MVEBU
  1123. help
  1124. If you say yes here you will get support for the in-chip RTC
  1125. that can be found in the Armada 38x Marvell's SoC device
  1126. This driver can also be built as a module. If so, the module
  1127. will be called armada38x-rtc.
  1128. config RTC_DRV_GEMINI
  1129. tristate "Gemini SoC RTC"
  1130. depends on ARCH_GEMINI || COMPILE_TEST
  1131. depends on HAS_IOMEM
  1132. help
  1133. If you say Y here you will get support for the
  1134. RTC found on Gemini SoC's.
  1135. This driver can also be built as a module. If so, the module
  1136. will be called rtc-gemini.
  1137. config RTC_DRV_PS3
  1138. tristate "PS3 RTC"
  1139. depends on PPC_PS3
  1140. help
  1141. If you say yes here you will get support for the RTC on PS3.
  1142. This driver can also be built as a module. If so, the module
  1143. will be called rtc-ps3.
  1144. config RTC_DRV_COH901331
  1145. tristate "ST-Ericsson COH 901 331 RTC"
  1146. depends on ARCH_U300
  1147. help
  1148. If you say Y here you will get access to ST-Ericsson
  1149. COH 901 331 RTC clock found in some ST-Ericsson Mobile
  1150. Platforms.
  1151. This driver can also be built as a module. If so, the module
  1152. will be called "rtc-coh901331".
  1153. config RTC_DRV_STMP
  1154. tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
  1155. depends on ARCH_MXS
  1156. select STMP_DEVICE
  1157. help
  1158. If you say yes here you will get support for the onboard
  1159. STMP3xxx/i.MX23/i.MX28 RTC.
  1160. This driver can also be built as a module. If so, the module
  1161. will be called rtc-stmp3xxx.
  1162. config RTC_DRV_PCAP
  1163. tristate "PCAP RTC"
  1164. depends on EZX_PCAP
  1165. help
  1166. If you say Y here you will get support for the RTC found on
  1167. the PCAP2 ASIC used on some Motorola phones.
  1168. config RTC_DRV_MC13XXX
  1169. depends on MFD_MC13XXX
  1170. tristate "Freescale MC13xxx RTC"
  1171. help
  1172. This enables support for the RTCs found on Freescale's PMICs
  1173. MC13783 and MC13892.
  1174. config RTC_DRV_MPC5121
  1175. tristate "Freescale MPC5121 built-in RTC"
  1176. depends on PPC_MPC512x || PPC_MPC52xx
  1177. help
  1178. If you say yes here you will get support for the
  1179. built-in RTC on MPC5121 or on MPC5200.
  1180. This driver can also be built as a module. If so, the module
  1181. will be called rtc-mpc5121.
  1182. config RTC_DRV_JZ4740
  1183. tristate "Ingenic JZ4740 SoC"
  1184. depends on MACH_JZ4740
  1185. help
  1186. If you say yes here you get support for the Ingenic JZ4740 SoC RTC
  1187. controller.
  1188. This driver can also be buillt as a module. If so, the module
  1189. will be called rtc-jz4740.
  1190. config RTC_DRV_LPC24XX
  1191. tristate "NXP RTC for LPC178x/18xx/408x/43xx"
  1192. depends on ARCH_LPC18XX || COMPILE_TEST
  1193. depends on OF && HAS_IOMEM
  1194. help
  1195. This enables support for the NXP RTC found which can be found on
  1196. NXP LPC178x/18xx/408x/43xx devices.
  1197. If you have one of the devices above enable this driver to use
  1198. the hardware RTC. This driver can also be buillt as a module. If
  1199. so, the module will be called rtc-lpc24xx.
  1200. config RTC_DRV_LPC32XX
  1201. depends on ARCH_LPC32XX
  1202. tristate "NXP LPC32XX RTC"
  1203. help
  1204. This enables support for the NXP RTC in the LPC32XX
  1205. This driver can also be buillt as a module. If so, the module
  1206. will be called rtc-lpc32xx.
  1207. config RTC_DRV_PM8XXX
  1208. tristate "Qualcomm PMIC8XXX RTC"
  1209. depends on MFD_PM8XXX || MFD_SPMI_PMIC
  1210. help
  1211. If you say yes here you get support for the
  1212. Qualcomm PMIC8XXX RTC.
  1213. To compile this driver as a module, choose M here: the
  1214. module will be called rtc-pm8xxx.
  1215. config RTC_DRV_TEGRA
  1216. tristate "NVIDIA Tegra Internal RTC driver"
  1217. depends on ARCH_TEGRA
  1218. help
  1219. If you say yes here you get support for the
  1220. Tegra 200 series internal RTC module.
  1221. This drive can also be built as a module. If so, the module
  1222. will be called rtc-tegra.
  1223. config RTC_DRV_TILE
  1224. tristate "Tilera hypervisor RTC support"
  1225. depends on TILE
  1226. help
  1227. Enable support for the Linux driver side of the Tilera
  1228. hypervisor's real-time clock interface.
  1229. config RTC_DRV_PUV3
  1230. tristate "PKUnity v3 RTC support"
  1231. depends on ARCH_PUV3
  1232. help
  1233. This enables support for the RTC in the PKUnity-v3 SoCs.
  1234. This drive can also be built as a module. If so, the module
  1235. will be called rtc-puv3.
  1236. config RTC_DRV_LOONGSON1
  1237. tristate "loongson1 RTC support"
  1238. depends on MACH_LOONGSON32
  1239. help
  1240. This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
  1241. counter) to be used as a RTC.
  1242. This driver can also be built as a module. If so, the module
  1243. will be called rtc-ls1x.
  1244. config RTC_DRV_MXC
  1245. tristate "Freescale MXC Real Time Clock"
  1246. depends on ARCH_MXC
  1247. help
  1248. If you say yes here you get support for the Freescale MXC
  1249. RTC module.
  1250. This driver can also be built as a module, if so, the module
  1251. will be called "rtc-mxc".
  1252. config RTC_DRV_SNVS
  1253. tristate "Freescale SNVS RTC support"
  1254. select REGMAP_MMIO
  1255. depends on HAS_IOMEM
  1256. depends on OF
  1257. help
  1258. If you say yes here you get support for the Freescale SNVS
  1259. Low Power (LP) RTC module.
  1260. This driver can also be built as a module, if so, the module
  1261. will be called "rtc-snvs".
  1262. config RTC_DRV_SIRFSOC
  1263. tristate "SiRFSOC RTC"
  1264. depends on ARCH_SIRF
  1265. help
  1266. Say "yes" here to support the real time clock on SiRF SOC chips.
  1267. This driver can also be built as a module called rtc-sirfsoc.
  1268. config RTC_DRV_ST_LPC
  1269. tristate "STMicroelectronics LPC RTC"
  1270. depends on ARCH_STI
  1271. depends on OF
  1272. help
  1273. Say Y here to include STMicroelectronics Low Power Controller
  1274. (LPC) based RTC support.
  1275. To compile this driver as a module, choose M here: the
  1276. module will be called rtc-st-lpc.
  1277. config RTC_DRV_MOXART
  1278. tristate "MOXA ART RTC"
  1279. depends on ARCH_MOXART || COMPILE_TEST
  1280. help
  1281. If you say yes here you get support for the MOXA ART
  1282. RTC module.
  1283. This driver can also be built as a module. If so, the module
  1284. will be called rtc-moxart
  1285. config RTC_DRV_MT6397
  1286. tristate "Mediatek Real Time Clock driver"
  1287. depends on MFD_MT6397 || COMPILE_TEST
  1288. help
  1289. This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
  1290. MT6397 PMIC. You should enable MT6397 PMIC MFD before select
  1291. Mediatek(R) RTC driver.
  1292. If you want to use Mediatek(R) RTC interface, select Y or M here.
  1293. config RTC_DRV_XGENE
  1294. tristate "APM X-Gene RTC"
  1295. depends on HAS_IOMEM
  1296. depends on ARCH_XGENE || COMPILE_TEST
  1297. help
  1298. If you say yes here you get support for the APM X-Gene SoC real time
  1299. clock.
  1300. This driver can also be built as a module, if so, the module
  1301. will be called "rtc-xgene".
  1302. comment "HID Sensor RTC drivers"
  1303. config RTC_DRV_HID_SENSOR_TIME
  1304. tristate "HID Sensor Time"
  1305. depends on USB_HID
  1306. select IIO
  1307. select HID_SENSOR_HUB
  1308. select HID_SENSOR_IIO_COMMON
  1309. help
  1310. Say yes here to build support for the HID Sensors of type Time.
  1311. This drivers makes such sensors available as RTCs.
  1312. If this driver is compiled as a module, it will be named
  1313. rtc-hid-sensor-time.
  1314. endif # RTC_CLASS