Kconfig 9.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324
  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. config RTC_DRV_X1205
  82. tristate "Xicor/Intersil X1205"
  83. depends on RTC_CLASS && I2C
  84. help
  85. If you say yes here you get support for the
  86. Xicor/Intersil X1205 RTC chip.
  87. This driver can also be built as a module. If so, the module
  88. will be called rtc-x1205.
  89. config RTC_DRV_DS1307
  90. tristate "Dallas/Maxim DS1307 and similar I2C RTC chips"
  91. depends on RTC_CLASS && I2C
  92. help
  93. If you say yes here you get support for various compatible RTC
  94. chips (often with battery backup) connected with I2C. This driver
  95. should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
  96. and probably other chips. In some cases the RTC must already
  97. have been initialized (by manufacturing or a bootloader).
  98. The first seven registers on these chips hold an RTC, and other
  99. registers may add features such as NVRAM, a trickle charger for
  100. the RTC/NVRAM backup power, and alarms. This driver may not
  101. expose all those available chip features.
  102. This driver can also be built as a module. If so, the module
  103. will be called rtc-ds1307.
  104. config RTC_DRV_DS1553
  105. tristate "Dallas DS1553"
  106. depends on RTC_CLASS
  107. help
  108. If you say yes here you get support for the
  109. Dallas DS1553 timekeeping chip.
  110. This driver can also be built as a module. If so, the module
  111. will be called rtc-ds1553.
  112. config RTC_DRV_ISL1208
  113. tristate "Intersil 1208"
  114. depends on RTC_CLASS && I2C
  115. help
  116. If you say yes here you get support for the
  117. Intersil 1208 RTC chip.
  118. This driver can also be built as a module. If so, the module
  119. will be called rtc-isl1208.
  120. config RTC_DRV_DS1672
  121. tristate "Dallas/Maxim DS1672"
  122. depends on RTC_CLASS && I2C
  123. help
  124. If you say yes here you get support for the
  125. Dallas/Maxim DS1672 timekeeping chip.
  126. This driver can also be built as a module. If so, the module
  127. will be called rtc-ds1672.
  128. config RTC_DRV_DS1742
  129. tristate "Dallas DS1742"
  130. depends on RTC_CLASS
  131. help
  132. If you say yes here you get support for the
  133. Dallas DS1742 timekeeping chip.
  134. This driver can also be built as a module. If so, the module
  135. will be called rtc-ds1742.
  136. config RTC_DRV_PCF8563
  137. tristate "Philips PCF8563/Epson RTC8564"
  138. depends on RTC_CLASS && I2C
  139. help
  140. If you say yes here you get support for the
  141. Philips PCF8563 RTC chip. The Epson RTC8564
  142. should work as well.
  143. This driver can also be built as a module. If so, the module
  144. will be called rtc-pcf8563.
  145. config RTC_DRV_PCF8583
  146. tristate "Philips PCF8583"
  147. depends on RTC_CLASS && I2C
  148. help
  149. If you say yes here you get support for the
  150. Philips PCF8583 RTC chip.
  151. This driver can also be built as a module. If so, the module
  152. will be called rtc-pcf8583.
  153. config RTC_DRV_RS5C348
  154. tristate "Ricoh RS5C348A/B"
  155. depends on RTC_CLASS && SPI
  156. help
  157. If you say yes here you get support for the
  158. Ricoh RS5C348A and RS5C348B RTC chips.
  159. This driver can also be built as a module. If so, the module
  160. will be called rtc-rs5c348.
  161. config RTC_DRV_RS5C372
  162. tristate "Ricoh RS5C372A/B"
  163. depends on RTC_CLASS && I2C
  164. help
  165. If you say yes here you get support for the
  166. Ricoh RS5C372A and RS5C372B RTC chips.
  167. This driver can also be built as a module. If so, the module
  168. will be called rtc-rs5c372.
  169. config RTC_DRV_S3C
  170. tristate "Samsung S3C series SoC RTC"
  171. depends on RTC_CLASS && ARCH_S3C2410
  172. help
  173. RTC (Realtime Clock) driver for the clock inbuilt into the
  174. Samsung S3C24XX series of SoCs. This can provide periodic
  175. interrupt rates from 1Hz to 64Hz for user programs, and
  176. wakeup from Alarm.
  177. The driver currently supports the common features on all the
  178. S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
  179. and S3C2442.
  180. This driver can also be build as a module. If so, the module
  181. will be called rtc-s3c.
  182. config RTC_DRV_M48T86
  183. tristate "ST M48T86/Dallas DS12887"
  184. depends on RTC_CLASS
  185. help
  186. If you say Y here you will get support for the
  187. ST M48T86 and Dallas DS12887 RTC chips.
  188. This driver can also be built as a module. If so, the module
  189. will be called rtc-m48t86.
  190. config RTC_DRV_EP93XX
  191. tristate "Cirrus Logic EP93XX"
  192. depends on RTC_CLASS && ARCH_EP93XX
  193. help
  194. If you say yes here you get support for the
  195. RTC embedded in the Cirrus Logic EP93XX processors.
  196. This driver can also be built as a module. If so, the module
  197. will be called rtc-ep93xx.
  198. config RTC_DRV_SA1100
  199. tristate "SA11x0/PXA2xx"
  200. depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA)
  201. help
  202. If you say Y here you will get access to the real time clock
  203. built into your SA11x0 or PXA2xx CPU.
  204. To compile this driver as a module, choose M here: the
  205. module will be called rtc-sa1100.
  206. config RTC_DRV_SH
  207. tristate "SuperH On-Chip RTC"
  208. depends on RTC_CLASS && SUPERH
  209. help
  210. Say Y here to enable support for the on-chip RTC found in
  211. most SuperH processors.
  212. To compile this driver as a module, choose M here: the
  213. module will be called rtc-sh.
  214. config RTC_DRV_VR41XX
  215. tristate "NEC VR41XX"
  216. depends on RTC_CLASS && CPU_VR41XX
  217. help
  218. If you say Y here you will get access to the real time clock
  219. built into your NEC VR41XX CPU.
  220. To compile this driver as a module, choose M here: the
  221. module will be called rtc-vr41xx.
  222. config RTC_DRV_PL031
  223. tristate "ARM AMBA PL031 RTC"
  224. depends on RTC_CLASS && ARM_AMBA
  225. help
  226. If you say Y here you will get access to ARM AMBA
  227. PrimeCell PL031 UART found on certain ARM SOCs.
  228. To compile this driver as a module, choose M here: the
  229. module will be called rtc-pl031.
  230. config RTC_DRV_AT91
  231. tristate "AT91RM9200"
  232. depends on RTC_CLASS && ARCH_AT91RM9200
  233. help
  234. Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).
  235. config RTC_DRV_TEST
  236. tristate "Test driver/device"
  237. depends on RTC_CLASS
  238. help
  239. If you say yes here you get support for the
  240. RTC test driver. It's a software RTC which can be
  241. used to test the RTC subsystem APIs. It gets
  242. the time from the system clock.
  243. You want this driver only if you are doing development
  244. on the RTC subsystem. Please read the source code
  245. for further details.
  246. This driver can also be built as a module. If so, the module
  247. will be called rtc-test.
  248. config RTC_DRV_MAX6902
  249. tristate "Maxim 6902"
  250. depends on RTC_CLASS && SPI
  251. help
  252. If you say yes here you will get support for the
  253. Maxim MAX6902 spi RTC chip.
  254. This driver can also be built as a module. If so, the module
  255. will be called rtc-max6902.
  256. config RTC_DRV_V3020
  257. tristate "EM Microelectronic V3020"
  258. depends on RTC_CLASS
  259. help
  260. If you say yes here you will get support for the
  261. EM Microelectronic v3020 RTC chip.
  262. This driver can also be built as a module. If so, the module
  263. will be called rtc-v3020.
  264. endmenu