Kconfig 10 KB

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