Kconfig 4.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175
  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. comment "RTC drivers"
  63. depends on RTC_CLASS
  64. config RTC_DRV_X1205
  65. tristate "Xicor/Intersil X1205"
  66. depends on RTC_CLASS && I2C
  67. help
  68. If you say yes here you get support for the
  69. Xicor/Intersil X1205 RTC chip.
  70. This driver can also be built as a module. If so, the module
  71. will be called rtc-x1205.
  72. config RTC_DRV_DS1672
  73. tristate "Dallas/Maxim DS1672"
  74. depends on RTC_CLASS && I2C
  75. help
  76. If you say yes here you get support for the
  77. Dallas/Maxim DS1672 timekeeping chip.
  78. This driver can also be built as a module. If so, the module
  79. will be called rtc-ds1672.
  80. config RTC_DRV_PCF8563
  81. tristate "Philips PCF8563/Epson RTC8564"
  82. depends on RTC_CLASS && I2C
  83. help
  84. If you say yes here you get support for the
  85. Philips PCF8563 RTC chip. The Epson RTC8564
  86. should work as well.
  87. This driver can also be built as a module. If so, the module
  88. will be called rtc-pcf8563.
  89. config RTC_DRV_RS5C372
  90. tristate "Ricoh RS5C372A/B"
  91. depends on RTC_CLASS && I2C
  92. help
  93. If you say yes here you get support for the
  94. Ricoh RS5C372A and RS5C372B RTC chips.
  95. This driver can also be built as a module. If so, the module
  96. will be called rtc-rs5c372.
  97. config RTC_DRV_M48T86
  98. tristate "ST M48T86/Dallas DS12887"
  99. depends on RTC_CLASS
  100. help
  101. If you say Y here you will get support for the
  102. ST M48T86 and Dallas DS12887 RTC chips.
  103. This driver can also be built as a module. If so, the module
  104. will be called rtc-m48t86.
  105. config RTC_DRV_EP93XX
  106. tristate "Cirrus Logic EP93XX"
  107. depends on RTC_CLASS && ARCH_EP93XX
  108. help
  109. If you say yes here you get support for the
  110. RTC embedded in the Cirrus Logic EP93XX processors.
  111. This driver can also be built as a module. If so, the module
  112. will be called rtc-ep93xx.
  113. config RTC_DRV_SA1100
  114. tristate "SA11x0/PXA2xx"
  115. depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA)
  116. help
  117. If you say Y here you will get access to the real time clock
  118. built into your SA11x0 or PXA2xx CPU.
  119. To compile this driver as a module, choose M here: the
  120. module will be called rtc-sa1100.
  121. config RTC_DRV_VR41XX
  122. tristate "NEC VR41XX"
  123. depends on RTC_CLASS && CPU_VR41XX
  124. help
  125. If you say Y here you will get access to the real time clock
  126. built into your NEC VR41XX CPU.
  127. To compile this driver as a module, choose M here: the
  128. module will be called rtc-vr41xx.
  129. config RTC_DRV_TEST
  130. tristate "Test driver/device"
  131. depends on RTC_CLASS
  132. help
  133. If you say yes here you get support for the
  134. RTC test driver. It's a software RTC which can be
  135. used to test the RTC subsystem APIs. It gets
  136. the time from the system clock.
  137. You want this driver only if you are doing development
  138. on the RTC subsystem. Please read the source code
  139. for further details.
  140. This driver can also be built as a module. If so, the module
  141. will be called rtc-test.
  142. endmenu