Kconfig 8.5 KB

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