Kconfig 45 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091109210931094109510961097109810991100110111021103110411051106110711081109111011111112111311141115111611171118111911201121112211231124112511261127112811291130113111321133113411351136113711381139114011411142114311441145114611471148114911501151115211531154115511561157115811591160116111621163116411651166116711681169117011711172117311741175117611771178117911801181118211831184118511861187118811891190119111921193119411951196119711981199120012011202120312041205120612071208120912101211121212131214121512161217121812191220122112221223122412251226122712281229123012311232123312341235123612371238123912401241124212431244124512461247124812491250125112521253125412551256125712581259126012611262126312641265126612671268126912701271127212731274127512761277127812791280128112821283128412851286128712881289129012911292129312941295129612971298129913001301130213031304130513061307130813091310131113121313131413151316131713181319132013211322132313241325132613271328132913301331133213331334133513361337133813391340134113421343134413451346134713481349135013511352135313541355135613571358135913601361136213631364136513661367136813691370137113721373137413751376137713781379138013811382138313841385138613871388138913901391139213931394139513961397139813991400140114021403140414051406140714081409141014111412141314141415141614171418141914201421142214231424142514261427142814291430143114321433143414351436143714381439144014411442144314441445144614471448144914501451145214531454145514561457145814591460146114621463146414651466146714681469147014711472147314741475147614771478147914801481148214831484148514861487148814891490149114921493149414951496149714981499150015011502150315041505150615071508150915101511151215131514151515161517151815191520152115221523152415251526152715281529153015311532153315341535153615371538153915401541154215431544154515461547154815491550155115521553155415551556155715581559156015611562156315641565156615671568156915701571157215731574157515761577157815791580158115821583158415851586158715881589159015911592159315941595159615971598159916001601
  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_S5M
  483. tristate "Samsung S2M/S5M series"
  484. depends on MFD_SEC_CORE
  485. help
  486. If you say yes here you will get support for the
  487. RTC of Samsung S2MPS14 and S5M PMIC series.
  488. This driver can also be built as a module. If so, the module
  489. will be called rtc-s5m.
  490. endif # I2C
  491. comment "SPI RTC drivers"
  492. if SPI_MASTER
  493. config RTC_DRV_M41T93
  494. tristate "ST M41T93"
  495. help
  496. If you say yes here you will get support for the
  497. ST M41T93 SPI RTC chip.
  498. This driver can also be built as a module. If so, the module
  499. will be called rtc-m41t93.
  500. config RTC_DRV_M41T94
  501. tristate "ST M41T94"
  502. help
  503. If you say yes here you will get support for the
  504. ST M41T94 SPI RTC chip.
  505. This driver can also be built as a module. If so, the module
  506. will be called rtc-m41t94.
  507. config RTC_DRV_DS1305
  508. tristate "Dallas/Maxim DS1305/DS1306"
  509. help
  510. Select this driver to get support for the Dallas/Maxim DS1305
  511. and DS1306 real time clock chips. These support a trickle
  512. charger, alarms, and NVRAM in addition to the clock.
  513. This driver can also be built as a module. If so, the module
  514. will be called rtc-ds1305.
  515. config RTC_DRV_DS1343
  516. select REGMAP_SPI
  517. tristate "Dallas/Maxim DS1343/DS1344"
  518. help
  519. If you say yes here you get support for the
  520. Dallas/Maxim DS1343 and DS1344 real time clock chips.
  521. Support for trickle charger, alarm is provided.
  522. This driver can also be built as a module. If so, the module
  523. will be called rtc-ds1343.
  524. config RTC_DRV_DS1347
  525. tristate "Dallas/Maxim DS1347"
  526. help
  527. If you say yes here you get support for the
  528. Dallas/Maxim DS1347 chips.
  529. This driver only supports the RTC feature, and not other chip
  530. features such as alarms.
  531. This driver can also be built as a module. If so, the module
  532. will be called rtc-ds1347.
  533. config RTC_DRV_DS1390
  534. tristate "Dallas/Maxim DS1390/93/94"
  535. help
  536. If you say yes here you get support for the
  537. Dallas/Maxim DS1390/93/94 chips.
  538. This driver only supports the RTC feature, and not other chip
  539. features such as alarms and trickle charging.
  540. This driver can also be built as a module. If so, the module
  541. will be called rtc-ds1390.
  542. config RTC_DRV_MAX6902
  543. tristate "Maxim MAX6902"
  544. help
  545. If you say yes here you will get support for the
  546. Maxim MAX6902 SPI RTC chip.
  547. This driver can also be built as a module. If so, the module
  548. will be called rtc-max6902.
  549. config RTC_DRV_R9701
  550. tristate "Epson RTC-9701JE"
  551. help
  552. If you say yes here you will get support for the
  553. Epson RTC-9701JE SPI RTC chip.
  554. This driver can also be built as a module. If so, the module
  555. will be called rtc-r9701.
  556. config RTC_DRV_RS5C348
  557. tristate "Ricoh RS5C348A/B"
  558. help
  559. If you say yes here you get support for the
  560. Ricoh RS5C348A and RS5C348B RTC chips.
  561. This driver can also be built as a module. If so, the module
  562. will be called rtc-rs5c348.
  563. config RTC_DRV_DS3234
  564. tristate "Maxim/Dallas DS3234"
  565. help
  566. If you say yes here you get support for the
  567. Maxim/Dallas DS3234 SPI RTC chip.
  568. This driver can also be built as a module. If so, the module
  569. will be called rtc-ds3234.
  570. config RTC_DRV_PCF2123
  571. tristate "NXP PCF2123"
  572. help
  573. If you say yes here you get support for the NXP PCF2123
  574. RTC chip.
  575. This driver can also be built as a module. If so, the module
  576. will be called rtc-pcf2123.
  577. config RTC_DRV_RX4581
  578. tristate "Epson RX-4581"
  579. help
  580. If you say yes here you will get support for the Epson RX-4581.
  581. This driver can also be built as a module. If so the module
  582. will be called rtc-rx4581.
  583. config RTC_DRV_MCP795
  584. tristate "Microchip MCP795"
  585. help
  586. If you say yes here you will get support for the Microchip MCP795.
  587. This driver can also be built as a module. If so the module
  588. will be called rtc-mcp795.
  589. endif # SPI_MASTER
  590. comment "Platform RTC drivers"
  591. # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
  592. # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
  593. # global rtc_lock ... it's not yet just another platform_device.
  594. config RTC_DRV_CMOS
  595. tristate "PC-style 'CMOS'"
  596. depends on X86 || ARM || M32R || PPC || MIPS || SPARC64
  597. default y if X86
  598. help
  599. Say "yes" here to get direct support for the real time clock
  600. found in every PC or ACPI-based system, and some other boards.
  601. Specifically the original MC146818, compatibles like those in
  602. PC south bridges, the DS12887 or M48T86, some multifunction
  603. or LPC bus chips, and so on.
  604. Your system will need to define the platform device used by
  605. this driver, otherwise it won't be accessible. This means
  606. you can safely enable this driver if you don't know whether
  607. or not your board has this kind of hardware.
  608. This driver can also be built as a module. If so, the module
  609. will be called rtc-cmos.
  610. config RTC_DRV_ALPHA
  611. bool "Alpha PC-style CMOS"
  612. depends on ALPHA
  613. default y
  614. help
  615. Direct support for the real-time clock found on every Alpha
  616. system, specifically MC146818 compatibles. If in doubt, say Y.
  617. config RTC_DRV_VRTC
  618. tristate "Virtual RTC for Intel MID platforms"
  619. depends on X86_INTEL_MID
  620. default y if X86_INTEL_MID
  621. help
  622. Say "yes" here to get direct support for the real time clock
  623. found on Moorestown platforms. The VRTC is a emulated RTC that
  624. derives its clock source from a real RTC in the PMIC. The MC146818
  625. style programming interface is mostly conserved, but any
  626. updates are done via IPC calls to the system controller FW.
  627. config RTC_DRV_DS1216
  628. tristate "Dallas DS1216"
  629. depends on SNI_RM
  630. help
  631. If you say yes here you get support for the Dallas DS1216 RTC chips.
  632. config RTC_DRV_DS1286
  633. tristate "Dallas DS1286"
  634. depends on HAS_IOMEM
  635. help
  636. If you say yes here you get support for the Dallas DS1286 RTC chips.
  637. config RTC_DRV_DS1302
  638. tristate "Dallas DS1302"
  639. depends on SH_SECUREEDGE5410
  640. help
  641. If you say yes here you get support for the Dallas DS1302 RTC chips.
  642. config RTC_DRV_DS1511
  643. tristate "Dallas DS1511"
  644. depends on HAS_IOMEM
  645. help
  646. If you say yes here you get support for the
  647. Dallas DS1511 timekeeping/watchdog chip.
  648. This driver can also be built as a module. If so, the module
  649. will be called rtc-ds1511.
  650. config RTC_DRV_DS1553
  651. tristate "Maxim/Dallas DS1553"
  652. depends on HAS_IOMEM
  653. help
  654. If you say yes here you get support for the
  655. Maxim/Dallas DS1553 timekeeping chip.
  656. This driver can also be built as a module. If so, the module
  657. will be called rtc-ds1553.
  658. config RTC_DRV_DS1685_FAMILY
  659. tristate "Dallas/Maxim DS1685 Family"
  660. help
  661. If you say yes here you get support for the Dallas/Maxim DS1685
  662. family of real time chips. This family includes the DS1685/DS1687,
  663. DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
  664. DS17885/DS17887 chips.
  665. This driver can also be built as a module. If so, the module
  666. will be called rtc-ds1685.
  667. choice
  668. prompt "Subtype"
  669. depends on RTC_DRV_DS1685_FAMILY
  670. default RTC_DRV_DS1685
  671. config RTC_DRV_DS1685
  672. bool "DS1685/DS1687"
  673. help
  674. This enables support for the Dallas/Maxim DS1685/DS1687 real time
  675. clock chip.
  676. This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
  677. systems, as well as EPPC-405-UC modules by electronic system design
  678. GmbH.
  679. config RTC_DRV_DS1689
  680. bool "DS1689/DS1693"
  681. help
  682. This enables support for the Dallas/Maxim DS1689/DS1693 real time
  683. clock chip.
  684. This is an older RTC chip, supplanted by the DS1685/DS1687 above,
  685. which supports a few minor features such as Vcc, Vbat, and Power
  686. Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
  687. It also works for the even older DS1688/DS1691 RTC chips, which are
  688. virtually the same and carry the same model number. Both chips
  689. have 114 bytes of user NVRAM.
  690. config RTC_DRV_DS17285
  691. bool "DS17285/DS17287"
  692. help
  693. This enables support for the Dallas/Maxim DS17285/DS17287 real time
  694. clock chip.
  695. This chip features 2kb of extended NV-SRAM. It may possibly be
  696. found in some SGI O2 systems (rare).
  697. config RTC_DRV_DS17485
  698. bool "DS17485/DS17487"
  699. help
  700. This enables support for the Dallas/Maxim DS17485/DS17487 real time
  701. clock chip.
  702. This chip features 4kb of extended NV-SRAM.
  703. config RTC_DRV_DS17885
  704. bool "DS17885/DS17887"
  705. help
  706. This enables support for the Dallas/Maxim DS17885/DS17887 real time
  707. clock chip.
  708. This chip features 8kb of extended NV-SRAM.
  709. endchoice
  710. config RTC_DS1685_PROC_REGS
  711. bool "Display register values in /proc"
  712. depends on RTC_DRV_DS1685_FAMILY && PROC_FS
  713. help
  714. Enable this to display a readout of all of the RTC registers in
  715. /proc/drivers/rtc. Keep in mind that this can potentially lead
  716. to lost interrupts, as reading Control Register C will clear
  717. all pending IRQ flags.
  718. Unless you are debugging this driver, choose N.
  719. config RTC_DS1685_SYSFS_REGS
  720. bool "SysFS access to RTC register bits"
  721. depends on RTC_DRV_DS1685_FAMILY && SYSFS
  722. help
  723. Enable this to provide access to the RTC control register bits
  724. in /sys. Some of the bits are read-write, others are read-only.
  725. Keep in mind that reading Control C's bits automatically clears
  726. all pending IRQ flags - this can cause lost interrupts.
  727. If you know that you need access to these bits, choose Y, Else N.
  728. config RTC_DRV_DS1742
  729. tristate "Maxim/Dallas DS1742/1743"
  730. depends on HAS_IOMEM
  731. help
  732. If you say yes here you get support for the
  733. Maxim/Dallas DS1742/1743 timekeeping chip.
  734. This driver can also be built as a module. If so, the module
  735. will be called rtc-ds1742.
  736. config RTC_DRV_DS2404
  737. tristate "Maxim/Dallas DS2404"
  738. help
  739. If you say yes here you get support for the
  740. Dallas DS2404 RTC chip.
  741. This driver can also be built as a module. If so, the module
  742. will be called rtc-ds2404.
  743. config RTC_DRV_DA9052
  744. tristate "Dialog DA9052/DA9053 RTC"
  745. depends on PMIC_DA9052
  746. help
  747. Say y here to support the RTC driver for Dialog Semiconductor
  748. DA9052-BC and DA9053-AA/Bx PMICs.
  749. config RTC_DRV_DA9055
  750. tristate "Dialog Semiconductor DA9055 RTC"
  751. depends on MFD_DA9055
  752. help
  753. If you say yes here you will get support for the
  754. RTC of the Dialog DA9055 PMIC.
  755. This driver can also be built as a module. If so, the module
  756. will be called rtc-da9055
  757. config RTC_DRV_DA9063
  758. tristate "Dialog Semiconductor DA9063 RTC"
  759. depends on MFD_DA9063
  760. help
  761. If you say yes here you will get support for the RTC subsystem
  762. of the Dialog Semiconductor DA9063.
  763. This driver can also be built as a module. If so, the module
  764. will be called "rtc-da9063".
  765. config RTC_DRV_EFI
  766. tristate "EFI RTC"
  767. depends on EFI && !X86
  768. help
  769. If you say yes here you will get support for the EFI
  770. Real Time Clock.
  771. This driver can also be built as a module. If so, the module
  772. will be called rtc-efi.
  773. config RTC_DRV_STK17TA8
  774. tristate "Simtek STK17TA8"
  775. depends on HAS_IOMEM
  776. help
  777. If you say yes here you get support for the
  778. Simtek STK17TA8 timekeeping chip.
  779. This driver can also be built as a module. If so, the module
  780. will be called rtc-stk17ta8.
  781. config RTC_DRV_M48T86
  782. tristate "ST M48T86/Dallas DS12887"
  783. help
  784. If you say Y here you will get support for the
  785. ST M48T86 and Dallas DS12887 RTC chips.
  786. This driver can also be built as a module. If so, the module
  787. will be called rtc-m48t86.
  788. config RTC_DRV_M48T35
  789. tristate "ST M48T35"
  790. depends on HAS_IOMEM
  791. help
  792. If you say Y here you will get support for the
  793. ST M48T35 RTC chip.
  794. This driver can also be built as a module, if so, the module
  795. will be called "rtc-m48t35".
  796. config RTC_DRV_M48T59
  797. tristate "ST M48T59/M48T08/M48T02"
  798. depends on HAS_IOMEM
  799. help
  800. If you say Y here you will get support for the
  801. ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
  802. These chips are usually found in Sun SPARC and UltraSPARC
  803. workstations.
  804. This driver can also be built as a module, if so, the module
  805. will be called "rtc-m48t59".
  806. config RTC_DRV_MSM6242
  807. tristate "Oki MSM6242"
  808. depends on HAS_IOMEM
  809. help
  810. If you say yes here you get support for the Oki MSM6242
  811. timekeeping chip. It is used in some Amiga models (e.g. A2000).
  812. This driver can also be built as a module. If so, the module
  813. will be called rtc-msm6242.
  814. config RTC_DRV_BQ4802
  815. tristate "TI BQ4802"
  816. depends on HAS_IOMEM
  817. help
  818. If you say Y here you will get support for the TI
  819. BQ4802 RTC chip.
  820. This driver can also be built as a module. If so, the module
  821. will be called rtc-bq4802.
  822. config RTC_DRV_RP5C01
  823. tristate "Ricoh RP5C01"
  824. depends on HAS_IOMEM
  825. help
  826. If you say yes here you get support for the Ricoh RP5C01
  827. timekeeping chip. It is used in some Amiga models (e.g. A3000
  828. and A4000).
  829. This driver can also be built as a module. If so, the module
  830. will be called rtc-rp5c01.
  831. config RTC_DRV_V3020
  832. tristate "EM Microelectronic V3020"
  833. help
  834. If you say yes here you will get support for the
  835. EM Microelectronic v3020 RTC chip.
  836. This driver can also be built as a module. If so, the module
  837. will be called rtc-v3020.
  838. config RTC_DRV_WM831X
  839. tristate "Wolfson Microelectronics WM831x RTC"
  840. depends on MFD_WM831X
  841. help
  842. If you say yes here you will get support for the RTC subsystem
  843. of the Wolfson Microelectronics WM831X series PMICs.
  844. This driver can also be built as a module. If so, the module
  845. will be called "rtc-wm831x".
  846. config RTC_DRV_WM8350
  847. tristate "Wolfson Microelectronics WM8350 RTC"
  848. depends on MFD_WM8350
  849. help
  850. If you say yes here you will get support for the RTC subsystem
  851. of the Wolfson Microelectronics WM8350.
  852. This driver can also be built as a module. If so, the module
  853. will be called "rtc-wm8350".
  854. config RTC_DRV_SPEAR
  855. tristate "SPEAR ST RTC"
  856. depends on PLAT_SPEAR
  857. default y
  858. help
  859. If you say Y here you will get support for the RTC found on
  860. spear
  861. config RTC_DRV_PCF50633
  862. depends on MFD_PCF50633
  863. tristate "NXP PCF50633 RTC"
  864. help
  865. If you say yes here you get support for the RTC subsystem of the
  866. NXP PCF50633 used in embedded systems.
  867. config RTC_DRV_AB3100
  868. tristate "ST-Ericsson AB3100 RTC"
  869. depends on AB3100_CORE
  870. default y if AB3100_CORE
  871. help
  872. Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
  873. support. This chip contains a battery- and capacitor-backed RTC.
  874. config RTC_DRV_AB8500
  875. tristate "ST-Ericsson AB8500 RTC"
  876. depends on AB8500_CORE
  877. select RTC_INTF_DEV
  878. select RTC_INTF_DEV_UIE_EMUL
  879. help
  880. Select this to enable the ST-Ericsson AB8500 power management IC RTC
  881. support. This chip contains a battery- and capacitor-backed RTC.
  882. config RTC_DRV_NUC900
  883. tristate "NUC910/NUC920 RTC driver"
  884. depends on ARCH_W90X900
  885. help
  886. If you say yes here you get support for the RTC subsystem of the
  887. NUC910/NUC920 used in embedded systems.
  888. config RTC_DRV_OPAL
  889. tristate "IBM OPAL RTC driver"
  890. depends on PPC_POWERNV
  891. default y
  892. help
  893. If you say yes here you get support for the PowerNV platform RTC
  894. driver based on OPAL interfaces.
  895. This driver can also be built as a module. If so, the module
  896. will be called rtc-opal.
  897. comment "on-CPU RTC drivers"
  898. config RTC_DRV_DAVINCI
  899. tristate "TI DaVinci RTC"
  900. depends on ARCH_DAVINCI_DM365
  901. help
  902. If you say yes here you get support for the RTC on the
  903. DaVinci platforms (DM365).
  904. This driver can also be built as a module. If so, the module
  905. will be called rtc-davinci.
  906. config RTC_DRV_DIGICOLOR
  907. tristate "Conexant Digicolor RTC"
  908. depends on ARCH_DIGICOLOR
  909. help
  910. If you say yes here you get support for the RTC on Conexant
  911. Digicolor platforms. This currently includes the CX92755 SoC.
  912. This driver can also be built as a module. If so, the module
  913. will be called rtc-digicolor.
  914. config RTC_DRV_IMXDI
  915. tristate "Freescale IMX DryIce Real Time Clock"
  916. depends on ARCH_MXC
  917. help
  918. Support for Freescale IMX DryIce RTC
  919. This driver can also be built as a module, if so, the module
  920. will be called "rtc-imxdi".
  921. config RTC_DRV_OMAP
  922. tristate "TI OMAP Real Time Clock"
  923. depends on ARCH_OMAP || ARCH_DAVINCI
  924. help
  925. Say "yes" here to support the on chip real time clock
  926. present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
  927. This driver can also be built as a module, if so, module
  928. will be called rtc-omap.
  929. config HAVE_S3C_RTC
  930. bool
  931. help
  932. This will include RTC support for Samsung SoCs. If
  933. you want to include RTC support for any machine, kindly
  934. select this in the respective mach-XXXX/Kconfig file.
  935. config RTC_DRV_S3C
  936. tristate "Samsung S3C series SoC RTC"
  937. depends on ARCH_S3C64XX || HAVE_S3C_RTC
  938. help
  939. RTC (Realtime Clock) driver for the clock inbuilt into the
  940. Samsung S3C24XX series of SoCs. This can provide periodic
  941. interrupt rates from 1Hz to 64Hz for user programs, and
  942. wakeup from Alarm.
  943. The driver currently supports the common features on all the
  944. S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
  945. and S3C2442.
  946. This driver can also be build as a module. If so, the module
  947. will be called rtc-s3c.
  948. config RTC_DRV_EP93XX
  949. tristate "Cirrus Logic EP93XX"
  950. depends on ARCH_EP93XX
  951. help
  952. If you say yes here you get support for the
  953. RTC embedded in the Cirrus Logic EP93XX processors.
  954. This driver can also be built as a module. If so, the module
  955. will be called rtc-ep93xx.
  956. config RTC_DRV_SA1100
  957. tristate "SA11x0/PXA2xx/PXA910"
  958. depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
  959. help
  960. If you say Y here you will get access to the real time clock
  961. built into your SA11x0 or PXA2xx CPU.
  962. To compile this driver as a module, choose M here: the
  963. module will be called rtc-sa1100.
  964. config RTC_DRV_SH
  965. tristate "SuperH On-Chip RTC"
  966. depends on SUPERH && HAVE_CLK
  967. help
  968. Say Y here to enable support for the on-chip RTC found in
  969. most SuperH processors.
  970. To compile this driver as a module, choose M here: the
  971. module will be called rtc-sh.
  972. config RTC_DRV_VR41XX
  973. tristate "NEC VR41XX"
  974. depends on CPU_VR41XX
  975. help
  976. If you say Y here you will get access to the real time clock
  977. built into your NEC VR41XX CPU.
  978. To compile this driver as a module, choose M here: the
  979. module will be called rtc-vr41xx.
  980. config RTC_DRV_PL030
  981. tristate "ARM AMBA PL030 RTC"
  982. depends on ARM_AMBA
  983. help
  984. If you say Y here you will get access to ARM AMBA
  985. PrimeCell PL030 RTC found on certain ARM SOCs.
  986. To compile this driver as a module, choose M here: the
  987. module will be called rtc-pl030.
  988. config RTC_DRV_PL031
  989. tristate "ARM AMBA PL031 RTC"
  990. depends on ARM_AMBA
  991. help
  992. If you say Y here you will get access to ARM AMBA
  993. PrimeCell PL031 RTC found on certain ARM SOCs.
  994. To compile this driver as a module, choose M here: the
  995. module will be called rtc-pl031.
  996. config RTC_DRV_AT32AP700X
  997. tristate "AT32AP700X series RTC"
  998. depends on PLATFORM_AT32AP
  999. help
  1000. Driver for the internal RTC (Realtime Clock) on Atmel AVR32
  1001. AT32AP700x family processors.
  1002. config RTC_DRV_AT91RM9200
  1003. tristate "AT91RM9200 or some AT91SAM9 RTC"
  1004. depends on ARCH_AT91
  1005. help
  1006. Driver for the internal RTC (Realtime Clock) module found on
  1007. Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
  1008. this is powered by the backup power supply.
  1009. config RTC_DRV_AT91SAM9
  1010. tristate "AT91SAM9 RTT as RTC"
  1011. depends on ARCH_AT91
  1012. select MFD_SYSCON
  1013. help
  1014. Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
  1015. can be used as an RTC thanks to the backup power supply (e.g. a
  1016. small coin cell battery) which keeps this block and the GPBR
  1017. (General Purpose Backup Registers) block powered when the device
  1018. is shutdown.
  1019. Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
  1020. probably want to use the real RTC block instead of the "RTT as an
  1021. RTC" driver.
  1022. config RTC_DRV_AU1XXX
  1023. tristate "Au1xxx Counter0 RTC support"
  1024. depends on MIPS_ALCHEMY
  1025. help
  1026. This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
  1027. counter) to be used as a RTC.
  1028. This driver can also be built as a module. If so, the module
  1029. will be called rtc-au1xxx.
  1030. config RTC_DRV_BFIN
  1031. tristate "Blackfin On-Chip RTC"
  1032. depends on BLACKFIN && !BF561
  1033. help
  1034. If you say yes here you will get support for the
  1035. Blackfin On-Chip Real Time Clock.
  1036. This driver can also be built as a module. If so, the module
  1037. will be called rtc-bfin.
  1038. config RTC_DRV_RS5C313
  1039. tristate "Ricoh RS5C313"
  1040. depends on SH_LANDISK
  1041. help
  1042. If you say yes here you get support for the Ricoh RS5C313 RTC chips.
  1043. config RTC_DRV_GENERIC
  1044. tristate "Generic RTC support"
  1045. # Please consider writing a new RTC driver instead of using the generic
  1046. # RTC abstraction
  1047. depends on PARISC || M68K || PPC || SUPERH32
  1048. help
  1049. Say Y or M here to enable RTC support on systems using the generic
  1050. RTC abstraction. If you do not know what you are doing, you should
  1051. just say Y.
  1052. config RTC_DRV_PXA
  1053. tristate "PXA27x/PXA3xx"
  1054. depends on ARCH_PXA
  1055. help
  1056. If you say Y here you will get access to the real time clock
  1057. built into your PXA27x or PXA3xx CPU.
  1058. This RTC driver uses PXA RTC registers available since pxa27x
  1059. series (RDxR, RYxR) instead of legacy RCNR, RTAR.
  1060. config RTC_DRV_VT8500
  1061. tristate "VIA/WonderMedia 85xx SoC RTC"
  1062. depends on ARCH_VT8500
  1063. help
  1064. If you say Y here you will get access to the real time clock
  1065. built into your VIA VT8500 SoC or its relatives.
  1066. config RTC_DRV_SUN4V
  1067. bool "SUN4V Hypervisor RTC"
  1068. depends on SPARC64
  1069. help
  1070. If you say Y here you will get support for the Hypervisor
  1071. based RTC on SUN4V systems.
  1072. config RTC_DRV_SUN6I
  1073. tristate "Allwinner A31 RTC"
  1074. depends on MACH_SUN6I || MACH_SUN8I
  1075. help
  1076. If you say Y here you will get support for the RTC found on
  1077. Allwinner A31.
  1078. config RTC_DRV_SUNXI
  1079. tristate "Allwinner sun4i/sun7i RTC"
  1080. depends on MACH_SUN4I || MACH_SUN7I
  1081. help
  1082. If you say Y here you will get support for the RTC found on
  1083. Allwinner A10/A20.
  1084. config RTC_DRV_STARFIRE
  1085. bool "Starfire RTC"
  1086. depends on SPARC64
  1087. help
  1088. If you say Y here you will get support for the RTC found on
  1089. Starfire systems.
  1090. config RTC_DRV_TX4939
  1091. tristate "TX4939 SoC"
  1092. depends on SOC_TX4939
  1093. help
  1094. Driver for the internal RTC (Realtime Clock) module found on
  1095. Toshiba TX4939 SoC.
  1096. config RTC_DRV_MV
  1097. tristate "Marvell SoC RTC"
  1098. depends on ARCH_DOVE || ARCH_MVEBU
  1099. help
  1100. If you say yes here you will get support for the in-chip RTC
  1101. that can be found in some of Marvell's SoC devices, such as
  1102. the Kirkwood 88F6281 and 88F6192.
  1103. This driver can also be built as a module. If so, the module
  1104. will be called rtc-mv.
  1105. config RTC_DRV_ARMADA38X
  1106. tristate "Armada 38x Marvell SoC RTC"
  1107. depends on ARCH_MVEBU
  1108. help
  1109. If you say yes here you will get support for the in-chip RTC
  1110. that can be found in the Armada 38x Marvell's SoC device
  1111. This driver can also be built as a module. If so, the module
  1112. will be called armada38x-rtc.
  1113. config RTC_DRV_GEMINI
  1114. tristate "Gemini SoC RTC"
  1115. depends on ARCH_GEMINI || COMPILE_TEST
  1116. depends on HAS_IOMEM
  1117. help
  1118. If you say Y here you will get support for the
  1119. RTC found on Gemini SoC's.
  1120. This driver can also be built as a module. If so, the module
  1121. will be called rtc-gemini.
  1122. config RTC_DRV_PS3
  1123. tristate "PS3 RTC"
  1124. depends on PPC_PS3
  1125. help
  1126. If you say yes here you will get support for the RTC on PS3.
  1127. This driver can also be built as a module. If so, the module
  1128. will be called rtc-ps3.
  1129. config RTC_DRV_COH901331
  1130. tristate "ST-Ericsson COH 901 331 RTC"
  1131. depends on ARCH_U300
  1132. help
  1133. If you say Y here you will get access to ST-Ericsson
  1134. COH 901 331 RTC clock found in some ST-Ericsson Mobile
  1135. Platforms.
  1136. This driver can also be built as a module. If so, the module
  1137. will be called "rtc-coh901331".
  1138. config RTC_DRV_STMP
  1139. tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
  1140. depends on ARCH_MXS
  1141. select STMP_DEVICE
  1142. help
  1143. If you say yes here you will get support for the onboard
  1144. STMP3xxx/i.MX23/i.MX28 RTC.
  1145. This driver can also be built as a module. If so, the module
  1146. will be called rtc-stmp3xxx.
  1147. config RTC_DRV_PCAP
  1148. tristate "PCAP RTC"
  1149. depends on EZX_PCAP
  1150. help
  1151. If you say Y here you will get support for the RTC found on
  1152. the PCAP2 ASIC used on some Motorola phones.
  1153. config RTC_DRV_MC13XXX
  1154. depends on MFD_MC13XXX
  1155. tristate "Freescale MC13xxx RTC"
  1156. help
  1157. This enables support for the RTCs found on Freescale's PMICs
  1158. MC13783 and MC13892.
  1159. config RTC_DRV_MPC5121
  1160. tristate "Freescale MPC5121 built-in RTC"
  1161. depends on PPC_MPC512x || PPC_MPC52xx
  1162. help
  1163. If you say yes here you will get support for the
  1164. built-in RTC on MPC5121 or on MPC5200.
  1165. This driver can also be built as a module. If so, the module
  1166. will be called rtc-mpc5121.
  1167. config RTC_DRV_JZ4740
  1168. tristate "Ingenic JZ4740 SoC"
  1169. depends on MACH_JZ4740
  1170. help
  1171. If you say yes here you get support for the Ingenic JZ4740 SoC RTC
  1172. controller.
  1173. This driver can also be buillt as a module. If so, the module
  1174. will be called rtc-jz4740.
  1175. config RTC_DRV_LPC32XX
  1176. depends on ARCH_LPC32XX
  1177. tristate "NXP LPC32XX RTC"
  1178. help
  1179. This enables support for the NXP RTC in the LPC32XX
  1180. This driver can also be buillt as a module. If so, the module
  1181. will be called rtc-lpc32xx.
  1182. config RTC_DRV_PM8XXX
  1183. tristate "Qualcomm PMIC8XXX RTC"
  1184. depends on MFD_PM8XXX || MFD_SPMI_PMIC
  1185. help
  1186. If you say yes here you get support for the
  1187. Qualcomm PMIC8XXX RTC.
  1188. To compile this driver as a module, choose M here: the
  1189. module will be called rtc-pm8xxx.
  1190. config RTC_DRV_TEGRA
  1191. tristate "NVIDIA Tegra Internal RTC driver"
  1192. depends on ARCH_TEGRA
  1193. help
  1194. If you say yes here you get support for the
  1195. Tegra 200 series internal RTC module.
  1196. This drive can also be built as a module. If so, the module
  1197. will be called rtc-tegra.
  1198. config RTC_DRV_TILE
  1199. tristate "Tilera hypervisor RTC support"
  1200. depends on TILE
  1201. help
  1202. Enable support for the Linux driver side of the Tilera
  1203. hypervisor's real-time clock interface.
  1204. config RTC_DRV_PUV3
  1205. tristate "PKUnity v3 RTC support"
  1206. depends on ARCH_PUV3
  1207. help
  1208. This enables support for the RTC in the PKUnity-v3 SoCs.
  1209. This drive can also be built as a module. If so, the module
  1210. will be called rtc-puv3.
  1211. config RTC_DRV_LOONGSON1
  1212. tristate "loongson1 RTC support"
  1213. depends on MACH_LOONGSON32
  1214. help
  1215. This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
  1216. counter) to be used as a RTC.
  1217. This driver can also be built as a module. If so, the module
  1218. will be called rtc-ls1x.
  1219. config RTC_DRV_MXC
  1220. tristate "Freescale MXC Real Time Clock"
  1221. depends on ARCH_MXC
  1222. help
  1223. If you say yes here you get support for the Freescale MXC
  1224. RTC module.
  1225. This driver can also be built as a module, if so, the module
  1226. will be called "rtc-mxc".
  1227. config RTC_DRV_SNVS
  1228. tristate "Freescale SNVS RTC support"
  1229. depends on HAS_IOMEM
  1230. depends on OF
  1231. help
  1232. If you say yes here you get support for the Freescale SNVS
  1233. Low Power (LP) RTC module.
  1234. This driver can also be built as a module, if so, the module
  1235. will be called "rtc-snvs".
  1236. config RTC_DRV_SIRFSOC
  1237. tristate "SiRFSOC RTC"
  1238. depends on ARCH_SIRF
  1239. help
  1240. Say "yes" here to support the real time clock on SiRF SOC chips.
  1241. This driver can also be built as a module called rtc-sirfsoc.
  1242. config RTC_DRV_ST_LPC
  1243. tristate "STMicroelectronics LPC RTC"
  1244. depends on ARCH_STI
  1245. depends on OF
  1246. help
  1247. Say Y here to include STMicroelectronics Low Power Controller
  1248. (LPC) based RTC support.
  1249. To compile this driver as a module, choose M here: the
  1250. module will be called rtc-st-lpc.
  1251. config RTC_DRV_MOXART
  1252. tristate "MOXA ART RTC"
  1253. depends on ARCH_MOXART || COMPILE_TEST
  1254. help
  1255. If you say yes here you get support for the MOXA ART
  1256. RTC module.
  1257. This driver can also be built as a module. If so, the module
  1258. will be called rtc-moxart
  1259. config RTC_DRV_MT6397
  1260. tristate "Mediatek Real Time Clock driver"
  1261. depends on MFD_MT6397 || COMPILE_TEST
  1262. help
  1263. This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
  1264. MT6397 PMIC. You should enable MT6397 PMIC MFD before select
  1265. Mediatek(R) RTC driver.
  1266. If you want to use Mediatek(R) RTC interface, select Y or M here.
  1267. config RTC_DRV_XGENE
  1268. tristate "APM X-Gene RTC"
  1269. depends on HAS_IOMEM
  1270. depends on ARCH_XGENE || COMPILE_TEST
  1271. help
  1272. If you say yes here you get support for the APM X-Gene SoC real time
  1273. clock.
  1274. This driver can also be built as a module, if so, the module
  1275. will be called "rtc-xgene".
  1276. comment "HID Sensor RTC drivers"
  1277. config RTC_DRV_HID_SENSOR_TIME
  1278. tristate "HID Sensor Time"
  1279. depends on USB_HID
  1280. select IIO
  1281. select HID_SENSOR_HUB
  1282. select HID_SENSOR_IIO_COMMON
  1283. help
  1284. Say yes here to build support for the HID Sensors of type Time.
  1285. This drivers makes such sensors available as RTCs.
  1286. If this driver is compiled as a module, it will be named
  1287. rtc-hid-sensor-time.
  1288. endif # RTC_CLASS