Kconfig 12 KB

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