Kconfig 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468
  1. #
  2. # RTC class/drivers configuration
  3. #
  4. config RTC_LIB
  5. tristate
  6. menuconfig RTC_CLASS
  7. tristate "Real Time Clock"
  8. default n
  9. depends on !S390
  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. This driver can also be built as a module. If so, the module
  16. will be called rtc-class.
  17. if RTC_CLASS
  18. if GEN_RTC || RTC
  19. comment "Conflicting RTC option has been selected, check GEN_RTC and RTC"
  20. endif
  21. config RTC_HCTOSYS
  22. bool "Set system time from RTC on startup and resume"
  23. depends on RTC_CLASS = y
  24. default y
  25. help
  26. If you say yes here, the system time (wall clock) will be set using
  27. the value read from a specified RTC device. This is useful to avoid
  28. unnecessary fsck runs at boot time, and to network better.
  29. config RTC_HCTOSYS_DEVICE
  30. string "RTC used to set the system time"
  31. depends on RTC_HCTOSYS = y
  32. default "rtc0"
  33. help
  34. The RTC device that will be used to (re)initialize the system
  35. clock, usually rtc0. Initialization is done when the system
  36. starts up, and when it resumes from a low power state. This
  37. device should record time in UTC, since the kernel won't do
  38. timezone correction.
  39. The driver for this RTC device must be loaded before late_initcall
  40. functions run, so it must usually be statically linked.
  41. This clock should be battery-backed, so that it reads the correct
  42. time when the system boots from a power-off state. Otherwise, your
  43. system will need an external clock source (like an NTP server).
  44. If the clock you specify here is not battery backed, it may still
  45. be useful to reinitialize system time when resuming from system
  46. sleep states. Do not specify an RTC here unless it stays powered
  47. during all this system's supported sleep states.
  48. config RTC_DEBUG
  49. bool "RTC debug support"
  50. depends on RTC_CLASS = y
  51. help
  52. Say yes here to enable debugging support in the RTC framework
  53. and individual RTC drivers.
  54. comment "RTC interfaces"
  55. config RTC_INTF_SYSFS
  56. boolean "/sys/class/rtc/rtcN (sysfs)"
  57. depends on SYSFS
  58. default RTC_CLASS
  59. help
  60. Say yes here if you want to use your RTCs using sysfs interfaces,
  61. /sys/class/rtc/rtc0 through /sys/.../rtcN.
  62. This driver can also be built as a module. If so, the module
  63. will be called rtc-sysfs.
  64. config RTC_INTF_PROC
  65. boolean "/proc/driver/rtc (procfs for rtc0)"
  66. depends on PROC_FS
  67. default RTC_CLASS
  68. help
  69. Say yes here if you want to use your first RTC through the proc
  70. interface, /proc/driver/rtc. Other RTCs will not be available
  71. through that API.
  72. This driver can also be built as a module. If so, the module
  73. will be called rtc-proc.
  74. config RTC_INTF_DEV
  75. boolean "/dev/rtcN (character devices)"
  76. default RTC_CLASS
  77. help
  78. Say yes here if you want to use your RTCs using the /dev
  79. interfaces, which "udev" sets up as /dev/rtc0 through
  80. /dev/rtcN. You may want to set up a symbolic link so one
  81. of these can be accessed as /dev/rtc, which is a name
  82. expected by "hwclock" and some other programs.
  83. This driver can also be built as a module. If so, the module
  84. will be called rtc-dev.
  85. config RTC_INTF_DEV_UIE_EMUL
  86. bool "RTC UIE emulation on dev interface"
  87. depends on RTC_INTF_DEV
  88. help
  89. Provides an emulation for RTC_UIE if the underlying rtc chip
  90. driver does not expose RTC_UIE ioctls. Those requests generate
  91. once-per-second update interrupts, used for synchronization.
  92. config RTC_DRV_TEST
  93. tristate "Test driver/device"
  94. help
  95. If you say yes here you get support for the
  96. RTC test driver. It's a software RTC which can be
  97. used to test the RTC subsystem APIs. It gets
  98. the time from the system clock.
  99. You want this driver only if you are doing development
  100. on the RTC subsystem. Please read the source code
  101. for further details.
  102. This driver can also be built as a module. If so, the module
  103. will be called rtc-test.
  104. comment "I2C RTC drivers"
  105. depends on I2C
  106. if I2C
  107. config RTC_DRV_DS1307
  108. tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00"
  109. help
  110. If you say yes here you get support for various compatible RTC
  111. chips (often with battery backup) connected with I2C. This driver
  112. should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
  113. and probably other chips. In some cases the RTC must already
  114. have been initialized (by manufacturing or a bootloader).
  115. The first seven registers on these chips hold an RTC, and other
  116. registers may add features such as NVRAM, a trickle charger for
  117. the RTC/NVRAM backup power, and alarms. NVRAM is visible in
  118. sysfs, but other chip features may not be available.
  119. This driver can also be built as a module. If so, the module
  120. will be called rtc-ds1307.
  121. config RTC_DRV_DS1374
  122. tristate "Dallas/Maxim DS1374"
  123. depends on RTC_CLASS && I2C
  124. help
  125. If you say yes here you get support for Dallas Semiconductor
  126. DS1374 real-time clock chips. If an interrupt is associated
  127. with the device, the alarm functionality is supported.
  128. This driver can also be built as a module. If so, the module
  129. will be called rtc-ds1374.
  130. config RTC_DRV_DS1672
  131. tristate "Dallas/Maxim DS1672"
  132. help
  133. If you say yes here you get support for the
  134. Dallas/Maxim DS1672 timekeeping chip.
  135. This driver can also be built as a module. If so, the module
  136. will be called rtc-ds1672.
  137. config RTC_DRV_MAX6900
  138. tristate "Maxim MAX6900"
  139. help
  140. If you say yes here you will get support for the
  141. Maxim MAX6900 I2C RTC chip.
  142. This driver can also be built as a module. If so, the module
  143. will be called rtc-max6900.
  144. config RTC_DRV_RS5C372
  145. tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A"
  146. help
  147. If you say yes here you get support for the
  148. Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
  149. This driver can also be built as a module. If so, the module
  150. will be called rtc-rs5c372.
  151. config RTC_DRV_ISL1208
  152. tristate "Intersil ISL1208"
  153. help
  154. If you say yes here you get support for the
  155. Intersil ISL1208 RTC chip.
  156. This driver can also be built as a module. If so, the module
  157. will be called rtc-isl1208.
  158. config RTC_DRV_X1205
  159. tristate "Xicor/Intersil X1205"
  160. help
  161. If you say yes here you get support for the
  162. Xicor/Intersil X1205 RTC chip.
  163. This driver can also be built as a module. If so, the module
  164. will be called rtc-x1205.
  165. config RTC_DRV_PCF8563
  166. tristate "Philips PCF8563/Epson RTC8564"
  167. help
  168. If you say yes here you get support for the
  169. Philips PCF8563 RTC chip. The Epson RTC8564
  170. should work as well.
  171. This driver can also be built as a module. If so, the module
  172. will be called rtc-pcf8563.
  173. config RTC_DRV_PCF8583
  174. tristate "Philips PCF8583"
  175. help
  176. If you say yes here you get support for the Philips PCF8583
  177. RTC chip found on Acorn RiscPCs. This driver supports the
  178. platform specific method of retrieving the current year from
  179. the RTC's SRAM. It will work on other platforms with the same
  180. chip, but the year will probably have to be tweaked.
  181. This driver can also be built as a module. If so, the module
  182. will be called rtc-pcf8583.
  183. config RTC_DRV_M41T80
  184. tristate "ST M41T80/81/82/83/84/85/87"
  185. help
  186. If you say Y here you will get support for the
  187. ST M41T80 RTC chips series. Currently following chips are
  188. supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85
  189. and M41ST87.
  190. This driver can also be built as a module. If so, the module
  191. will be called rtc-m41t80.
  192. config RTC_DRV_M41T80_WDT
  193. bool "ST M41T80 series RTC watchdog timer"
  194. depends on RTC_DRV_M41T80
  195. help
  196. If you say Y here you will get support for the
  197. watchdog timer in ST M41T80 RTC chips series.
  198. config RTC_DRV_TWL92330
  199. boolean "TI TWL92330/Menelaus"
  200. depends on MENELAUS
  201. help
  202. If you say yes here you get support for the RTC on the
  203. TWL92330 "Menelaus" power management chip, used with OMAP2
  204. platforms. The support is integrated with the rest of
  205. the Menelaus driver; it's not separate module.
  206. endif # I2C
  207. comment "SPI RTC drivers"
  208. if SPI_MASTER
  209. config RTC_DRV_MAX6902
  210. tristate "Maxim MAX6902"
  211. help
  212. If you say yes here you will get support for the
  213. Maxim MAX6902 SPI RTC chip.
  214. This driver can also be built as a module. If so, the module
  215. will be called rtc-max6902.
  216. config RTC_DRV_RS5C348
  217. tristate "Ricoh RS5C348A/B"
  218. help
  219. If you say yes here you get support for the
  220. Ricoh RS5C348A and RS5C348B RTC chips.
  221. This driver can also be built as a module. If so, the module
  222. will be called rtc-rs5c348.
  223. endif # SPI_MASTER
  224. comment "Platform RTC drivers"
  225. # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
  226. # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
  227. # global rtc_lock ... it's not yet just another platform_device.
  228. config RTC_DRV_CMOS
  229. tristate "PC-style 'CMOS'"
  230. depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS
  231. help
  232. Say "yes" here to get direct support for the real time clock
  233. found in every PC or ACPI-based system, and some other boards.
  234. Specifically the original MC146818, compatibles like those in
  235. PC south bridges, the DS12887 or M48T86, some multifunction
  236. or LPC bus chips, and so on.
  237. Your system will need to define the platform device used by
  238. this driver, otherwise it won't be accessible. This means
  239. you can safely enable this driver if you don't know whether
  240. or not your board has this kind of hardware.
  241. This driver can also be built as a module. If so, the module
  242. will be called rtc-cmos.
  243. config RTC_DRV_DS1216
  244. tristate "Dallas DS1216"
  245. depends on SNI_RM
  246. help
  247. If you say yes here you get support for the Dallas DS1216 RTC chips.
  248. config RTC_DRV_DS1553
  249. tristate "Maxim/Dallas DS1553"
  250. help
  251. If you say yes here you get support for the
  252. Maxim/Dallas DS1553 timekeeping chip.
  253. This driver can also be built as a module. If so, the module
  254. will be called rtc-ds1553.
  255. config RTC_DRV_DS1742
  256. tristate "Maxim/Dallas DS1742/1743"
  257. help
  258. If you say yes here you get support for the
  259. Maxim/Dallas DS1742/1743 timekeeping chip.
  260. This driver can also be built as a module. If so, the module
  261. will be called rtc-ds1742.
  262. config RTC_DRV_STK17TA8
  263. tristate "Simtek STK17TA8"
  264. depends on RTC_CLASS
  265. help
  266. If you say yes here you get support for the
  267. Simtek STK17TA8 timekeeping chip.
  268. This driver can also be built as a module. If so, the module
  269. will be called rtc-stk17ta8.
  270. config RTC_DRV_M48T86
  271. tristate "ST M48T86/Dallas DS12887"
  272. help
  273. If you say Y here you will get support for the
  274. ST M48T86 and Dallas DS12887 RTC chips.
  275. This driver can also be built as a module. If so, the module
  276. will be called rtc-m48t86.
  277. config RTC_DRV_M48T59
  278. tristate "ST M48T59"
  279. help
  280. If you say Y here you will get support for the
  281. ST M48T59 RTC chip.
  282. This driver can also be built as a module, if so, the module
  283. will be called "rtc-m48t59".
  284. config RTC_DRV_V3020
  285. tristate "EM Microelectronic V3020"
  286. help
  287. If you say yes here you will get support for the
  288. EM Microelectronic v3020 RTC chip.
  289. This driver can also be built as a module. If so, the module
  290. will be called rtc-v3020.
  291. comment "on-CPU RTC drivers"
  292. config RTC_DRV_OMAP
  293. tristate "TI OMAP1"
  294. depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730
  295. help
  296. Say "yes" here to support the real time clock on TI OMAP1 chips.
  297. This driver can also be built as a module called rtc-omap.
  298. config RTC_DRV_S3C
  299. tristate "Samsung S3C series SoC RTC"
  300. depends on ARCH_S3C2410
  301. help
  302. RTC (Realtime Clock) driver for the clock inbuilt into the
  303. Samsung S3C24XX series of SoCs. This can provide periodic
  304. interrupt rates from 1Hz to 64Hz for user programs, and
  305. wakeup from Alarm.
  306. The driver currently supports the common features on all the
  307. S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
  308. and S3C2442.
  309. This driver can also be build as a module. If so, the module
  310. will be called rtc-s3c.
  311. config RTC_DRV_EP93XX
  312. tristate "Cirrus Logic EP93XX"
  313. depends on ARCH_EP93XX
  314. help
  315. If you say yes here you get support for the
  316. RTC embedded in the Cirrus Logic EP93XX processors.
  317. This driver can also be built as a module. If so, the module
  318. will be called rtc-ep93xx.
  319. config RTC_DRV_SA1100
  320. tristate "SA11x0/PXA2xx"
  321. depends on ARCH_SA1100 || ARCH_PXA
  322. help
  323. If you say Y here you will get access to the real time clock
  324. built into your SA11x0 or PXA2xx CPU.
  325. To compile this driver as a module, choose M here: the
  326. module will be called rtc-sa1100.
  327. config RTC_DRV_SH
  328. tristate "SuperH On-Chip RTC"
  329. depends on RTC_CLASS && SUPERH
  330. help
  331. Say Y here to enable support for the on-chip RTC found in
  332. most SuperH processors.
  333. To compile this driver as a module, choose M here: the
  334. module will be called rtc-sh.
  335. config RTC_DRV_VR41XX
  336. tristate "NEC VR41XX"
  337. depends on CPU_VR41XX
  338. help
  339. If you say Y here you will get access to the real time clock
  340. built into your NEC VR41XX CPU.
  341. To compile this driver as a module, choose M here: the
  342. module will be called rtc-vr41xx.
  343. config RTC_DRV_PL031
  344. tristate "ARM AMBA PL031 RTC"
  345. depends on ARM_AMBA
  346. help
  347. If you say Y here you will get access to ARM AMBA
  348. PrimeCell PL031 RTC found on certain ARM SOCs.
  349. To compile this driver as a module, choose M here: the
  350. module will be called rtc-pl031.
  351. config RTC_DRV_AT32AP700X
  352. tristate "AT32AP700X series RTC"
  353. depends on PLATFORM_AT32AP
  354. help
  355. Driver for the internal RTC (Realtime Clock) on Atmel AVR32
  356. AT32AP700x family processors.
  357. config RTC_DRV_AT91RM9200
  358. tristate "AT91RM9200"
  359. depends on ARCH_AT91RM9200
  360. help
  361. Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).
  362. config RTC_DRV_BFIN
  363. tristate "Blackfin On-Chip RTC"
  364. depends on BLACKFIN
  365. help
  366. If you say yes here you will get support for the
  367. Blackfin On-Chip Real Time Clock.
  368. This driver can also be built as a module. If so, the module
  369. will be called rtc-bfin.
  370. config RTC_DRV_RS5C313
  371. tristate "Ricoh RS5C313"
  372. depends on SH_LANDISK
  373. help
  374. If you say yes here you get support for the Ricoh RS5C313 RTC chips.
  375. endif # RTC_CLASS