Kconfig 13 KB

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