Kconfig 52 KB

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