Kconfig 6.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220
  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 of 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_DS1672
  94. tristate "Dallas/Maxim DS1672"
  95. depends on RTC_CLASS && I2C
  96. help
  97. If you say yes here you get support for the
  98. Dallas/Maxim DS1672 timekeeping chip.
  99. This driver can also be built as a module. If so, the module
  100. will be called rtc-ds1672.
  101. config RTC_DRV_PCF8563
  102. tristate "Philips PCF8563/Epson RTC8564"
  103. depends on RTC_CLASS && I2C
  104. help
  105. If you say yes here you get support for the
  106. Philips PCF8563 RTC chip. The Epson RTC8564
  107. should work as well.
  108. This driver can also be built as a module. If so, the module
  109. will be called rtc-pcf8563.
  110. config RTC_DRV_PCF8583
  111. tristate "Philips PCF8583"
  112. depends on RTC_CLASS && I2C
  113. help
  114. If you say yes here you get support for the
  115. Philips PCF8583 RTC chip.
  116. This driver can also be built as a module. If so, the module
  117. will be called rtc-pcf8583.
  118. config RTC_DRV_RS5C372
  119. tristate "Ricoh RS5C372A/B"
  120. depends on RTC_CLASS && I2C
  121. help
  122. If you say yes here you get support for the
  123. Ricoh RS5C372A and RS5C372B RTC chips.
  124. This driver can also be built as a module. If so, the module
  125. will be called rtc-rs5c372.
  126. config RTC_DRV_M48T86
  127. tristate "ST M48T86/Dallas DS12887"
  128. depends on RTC_CLASS
  129. help
  130. If you say Y here you will get support for the
  131. ST M48T86 and Dallas DS12887 RTC chips.
  132. This driver can also be built as a module. If so, the module
  133. will be called rtc-m48t86.
  134. config RTC_DRV_EP93XX
  135. tristate "Cirrus Logic EP93XX"
  136. depends on RTC_CLASS && ARCH_EP93XX
  137. help
  138. If you say yes here you get support for the
  139. RTC embedded in the Cirrus Logic EP93XX processors.
  140. This driver can also be built as a module. If so, the module
  141. will be called rtc-ep93xx.
  142. config RTC_DRV_SA1100
  143. tristate "SA11x0/PXA2xx"
  144. depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA)
  145. help
  146. If you say Y here you will get access to the real time clock
  147. built into your SA11x0 or PXA2xx CPU.
  148. To compile this driver as a module, choose M here: the
  149. module will be called rtc-sa1100.
  150. config RTC_DRV_VR41XX
  151. tristate "NEC VR41XX"
  152. depends on RTC_CLASS && CPU_VR41XX
  153. help
  154. If you say Y here you will get access to the real time clock
  155. built into your NEC VR41XX CPU.
  156. To compile this driver as a module, choose M here: the
  157. module will be called rtc-vr41xx.
  158. config RTC_DRV_PL031
  159. tristate "ARM AMBA PL031 RTC"
  160. depends on RTC_CLASS && ARM_AMBA
  161. help
  162. If you say Y here you will get access to ARM AMBA
  163. PrimeCell PL031 UART found on certain ARM SOCs.
  164. To compile this driver as a module, choose M here: the
  165. module will be called rtc-pl031.
  166. config RTC_DRV_TEST
  167. tristate "Test driver/device"
  168. depends on RTC_CLASS
  169. help
  170. If you say yes here you get support for the
  171. RTC test driver. It's a software RTC which can be
  172. used to test the RTC subsystem APIs. It gets
  173. the time from the system clock.
  174. You want this driver only if you are doing development
  175. on the RTC subsystem. Please read the source code
  176. for further details.
  177. This driver can also be built as a module. If so, the module
  178. will be called rtc-test.
  179. endmenu