Kconfig 12.8 KB
Newer Older
1
#
2 3 4
# RTC class/drivers configuration
#

A
Alessandro Zummo 已提交
5
menu "Real Time Clock"
6
	depends on !S390
A
Alessandro Zummo 已提交
7

8
config RTC_LIB
A
Alessandro Zummo 已提交
9 10 11 12 13 14 15 16 17
	tristate

config RTC_CLASS
	tristate "RTC class"
	default n
	select RTC_LIB
	help
	  Generic RTC class support. If you say yes here, you will
 	  be allowed to plug one or more RTCs to your system. You will
18
	  probably want to enable one or more of the interfaces below.
A
Alessandro Zummo 已提交
19 20 21 22 23

	  This driver can also be built as a module. If so, the module
	  will be called rtc-class.

config RTC_HCTOSYS
24
	bool "Set system time from RTC on startup and resume"
A
Alessandro Zummo 已提交
25 26 27
	depends on RTC_CLASS = y
	default y
	help
28 29 30
	  If you say yes here, the system time (wall clock) will be set using
	  the value read from a specified RTC device. This is useful to avoid
	  unnecessary fsck runs at boot time, and to network better.
A
Alessandro Zummo 已提交
31 32

config RTC_HCTOSYS_DEVICE
33
	string "RTC used to set the system time"
A
Alessandro Zummo 已提交
34 35 36
	depends on RTC_HCTOSYS = y
	default "rtc0"
	help
37 38 39 40 41 42 43 44 45 46 47 48
	  The RTC device that will be used to (re)initialize the system
	  clock, usually rtc0.  Initialization is done when the system
	  starts up, and when it resumes from a low power state.

	  This clock should be battery-backed, so that it reads the correct
	  time when the system boots from a power-off state.  Otherwise, your
	  system will need an external clock source (like an NTP server).

	  If the clock you specify here is not battery backed, it may still
	  be useful to reinitialize system time when resuming from system
	  sleep states.  Do not specify an RTC here unless it stays powered
	  during all this system's supported sleep states.
A
Alessandro Zummo 已提交
49

50 51 52 53 54 55 56
config RTC_DEBUG
	bool "RTC debug support"
	depends on RTC_CLASS = y
	help
	  Say yes here to enable debugging support in the RTC framework
	  and individual RTC drivers.

A
Alessandro Zummo 已提交
57 58 59
comment "RTC interfaces"
	depends on RTC_CLASS

60
config RTC_INTF_SYSFS
D
David Brownell 已提交
61
	boolean "/sys/class/rtc/rtcN (sysfs)"
62 63 64
	depends on RTC_CLASS && SYSFS
	default RTC_CLASS
	help
65 66
	  Say yes here if you want to use your RTCs using sysfs interfaces,
	  /sys/class/rtc/rtc0 through /sys/.../rtcN.
67 68 69 70

	  This driver can also be built as a module. If so, the module
	  will be called rtc-sysfs.

71
config RTC_INTF_PROC
D
David Brownell 已提交
72
	boolean "/proc/driver/rtc (procfs for rtc0)"
73 74 75
	depends on RTC_CLASS && PROC_FS
	default RTC_CLASS
	help
76 77 78
	  Say yes here if you want to use your first RTC through the proc
	  interface, /proc/driver/rtc.  Other RTCs will not be available
	  through that API.
79 80 81 82

	  This driver can also be built as a module. If so, the module
	  will be called rtc-proc.

83
config RTC_INTF_DEV
D
David Brownell 已提交
84
	boolean "/dev/rtcN (character devices)"
85 86 87
	depends on RTC_CLASS
	default RTC_CLASS
	help
88 89 90 91 92
	  Say yes here if you want to use your RTCs using the /dev
	  interfaces, which "udev" sets up as /dev/rtc0 through
	  /dev/rtcN.  You may want to set up a symbolic link so one
	  of these can be accessed as /dev/rtc, which is a name
	  expected by "hwclock" and some other programs.
93 94 95 96

	  This driver can also be built as a module. If so, the module
	  will be called rtc-dev.

97 98 99 100
config RTC_INTF_DEV_UIE_EMUL
	bool "RTC UIE emulation on dev interface"
	depends on RTC_INTF_DEV
	help
101
	  Provides an emulation for RTC_UIE if the underlying rtc chip
102 103
	  driver does not expose RTC_UIE ioctls.  Those requests generate
	  once-per-second update interrupts, used for synchronization.
104

A
Alessandro Zummo 已提交
105 106
config RTC_DRV_TEST
	tristate "Test driver/device"
A
Alessandro Zummo 已提交
107
	depends on RTC_CLASS
108 109
	help
	  If you say yes here you get support for the
A
Alessandro Zummo 已提交
110 111 112 113 114 115
	  RTC test driver. It's a software RTC which can be
	  used to test the RTC subsystem APIs. It gets
	  the time from the system clock.
	  You want this driver only if you are doing development
	  on the RTC subsystem. Please read the source code
	  for further details.
116 117

	  This driver can also be built as a module. If so, the module
A
Alessandro Zummo 已提交
118 119 120
	  will be called rtc-test.

comment "I2C RTC drivers"
D
David Brownell 已提交
121
	depends on RTC_CLASS && I2C
122

123
config RTC_DRV_DS1307
A
Alessandro Zummo 已提交
124
	tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00"
125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140
	depends on RTC_CLASS && I2C
	help
	  If you say yes here you get support for various compatible RTC
	  chips (often with battery backup) connected with I2C.  This driver
	  should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
	  and probably other chips.  In some cases the RTC must already
	  have been initialized (by manufacturing or a bootloader).

	  The first seven registers on these chips hold an RTC, and other
	  registers may add features such as NVRAM, a trickle charger for
	  the RTC/NVRAM backup power, and alarms.  This driver may not
	  expose all those available chip features.

	  This driver can also be built as a module. If so, the module
	  will be called rtc-ds1307.

A
Alessandro Zummo 已提交
141 142 143
config RTC_DRV_DS1672
	tristate "Dallas/Maxim DS1672"
	depends on RTC_CLASS && I2C
144 145
	help
	  If you say yes here you get support for the
A
Alessandro Zummo 已提交
146
	  Dallas/Maxim DS1672 timekeeping chip.
147 148

	  This driver can also be built as a module. If so, the module
A
Alessandro Zummo 已提交
149
	  will be called rtc-ds1672.
150

A
Alessandro Zummo 已提交
151 152
config RTC_DRV_MAX6900
	tristate "Maxim 6900"
153 154
	depends on RTC_CLASS && I2C
	help
A
Alessandro Zummo 已提交
155 156
	  If you say yes here you will get support for the
	  Maxim MAX6900 I2C RTC chip.
157 158

	  This driver can also be built as a module. If so, the module
A
Alessandro Zummo 已提交
159
	  will be called rtc-max6900.
160

A
Alessandro Zummo 已提交
161
config RTC_DRV_RS5C372
162
	tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A"
163 164 165
	depends on RTC_CLASS && I2C
	help
	  If you say yes here you get support for the
166
	  Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
167 168

	  This driver can also be built as a module. If so, the module
A
Alessandro Zummo 已提交
169
	  will be called rtc-rs5c372.
170

A
Alessandro Zummo 已提交
171 172 173
config RTC_DRV_ISL1208
	tristate "Intersil 1208"
	depends on RTC_CLASS && I2C
174 175
	help
	  If you say yes here you get support for the
A
Alessandro Zummo 已提交
176
	  Intersil 1208 RTC chip.
177 178

	  This driver can also be built as a module. If so, the module
A
Alessandro Zummo 已提交
179
	  will be called rtc-isl1208.
180

A
Alessandro Zummo 已提交
181 182 183
config RTC_DRV_X1205
	tristate "Xicor/Intersil X1205"
	depends on RTC_CLASS && I2C
D
David Brownell 已提交
184
	help
A
Alessandro Zummo 已提交
185 186 187 188 189
	  If you say yes here you get support for the
	  Xicor/Intersil X1205 RTC chip.

	  This driver can also be built as a module. If so, the module
	  will be called rtc-x1205.
D
David Brownell 已提交
190

191 192 193 194 195 196 197 198 199 200 201
config RTC_DRV_PCF8563
	tristate "Philips PCF8563/Epson RTC8564"
	depends on RTC_CLASS && I2C
	help
	  If you say yes here you get support for the
	  Philips PCF8563 RTC chip. The Epson RTC8564
	  should work as well.

	  This driver can also be built as a module. If so, the module
	  will be called rtc-pcf8563.

202 203
config RTC_DRV_PCF8583
	tristate "Philips PCF8583"
A
Alessandro Zummo 已提交
204
	depends on RTC_CLASS && I2C
205
	help
206
	  If you say yes here you get support for the Philips PCF8583
A
Alessandro Zummo 已提交
207
	  RTC chip found on Acorn RiscPCs. This driver supports the
208
	  platform specific method of retrieving the current year from
A
Alessandro Zummo 已提交
209 210
	  the RTC's SRAM. It will work on other platforms with the same
	  chip, but the year will probably have to be tweaked.
211 212 213 214

	  This driver can also be built as a module. If so, the module
	  will be called rtc-pcf8583.

A
Atsushi Nemoto 已提交
215 216 217 218 219 220 221 222 223 224 225 226
config RTC_DRV_M41T80
	tristate "ST M41T80 series RTC"
	depends on RTC_CLASS && I2C
	help
	  If you say Y here you will get support for the
	  ST M41T80 RTC chips series. Currently following chips are
	  supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85
	  and M41ST87.

	  This driver can also be built as a module. If so, the module
	  will be called rtc-m41t80.

227 228 229 230 231 232 233
config RTC_DRV_M41T80_WDT
	bool "ST M41T80 series RTC watchdog timer"
	depends on RTC_DRV_M41T80
	help
	  If you say Y here you will get support for the
	  watchdog timer in ST M41T80 RTC chips series.

A
Alessandro Zummo 已提交
234
comment "SPI RTC drivers"
D
David Brownell 已提交
235
	depends on RTC_CLASS && SPI_MASTER
A
Alessandro Zummo 已提交
236

237 238
config RTC_DRV_RS5C348
	tristate "Ricoh RS5C348A/B"
D
David Brownell 已提交
239
	depends on RTC_CLASS && SPI_MASTER
240 241 242 243 244 245 246
	help
	  If you say yes here you get support for the
	  Ricoh RS5C348A and RS5C348B RTC chips.

	  This driver can also be built as a module. If so, the module
	  will be called rtc-rs5c348.

A
Alessandro Zummo 已提交
247 248
config RTC_DRV_MAX6902
	tristate "Maxim 6902"
D
David Brownell 已提交
249
	depends on RTC_CLASS && SPI_MASTER
A
Alessandro Zummo 已提交
250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266
	help
	  If you say yes here you will get support for the
	  Maxim MAX6902 SPI RTC chip.

	  This driver can also be built as a module. If so, the module
	  will be called rtc-max6902.

comment "Platform RTC drivers"
	depends on RTC_CLASS

# this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
# requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
# global rtc_lock ... it's not yet just another platform_device.

config RTC_DRV_CMOS
	tristate "PC-style 'CMOS'"
	depends on RTC_CLASS && (X86 || ALPHA || ARM26 || ARM \
267
		|| M32R || ATARI || PPC || MIPS)
A
Alessandro Zummo 已提交
268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285
	help
	  Say "yes" here to get direct support for the real time clock
	  found in every PC or ACPI-based system, and some other boards.
	  Specifically the original MC146818, compatibles like those in
	  PC south bridges, the DS12887 or M48T86, some multifunction
	  or LPC bus chips, and so on.

	  Your system will need to define the platform device used by
	  this driver, otherwise it won't be accessible.  This means
	  you can safely enable this driver if you don't know whether
	  or not your board has this kind of hardware.

	  This driver can also be built as a module. If so, the module
	  will be called rtc-cmos.

config RTC_DRV_DS1553
	tristate "Dallas DS1553"
	depends on RTC_CLASS
286 287
	help
	  If you say yes here you get support for the
A
Alessandro Zummo 已提交
288
	  Dallas DS1553 timekeeping chip.
289 290

	  This driver can also be built as a module. If so, the module
A
Alessandro Zummo 已提交
291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332
	  will be called rtc-ds1553.

config RTC_DRV_DS1742
	tristate "Dallas DS1742/1743"
	depends on RTC_CLASS
	help
	  If you say yes here you get support for the
	  Dallas DS1742/1743 timekeeping chip.

	  This driver can also be built as a module. If so, the module
	  will be called rtc-ds1742.

config RTC_DRV_M48T86
	tristate "ST M48T86/Dallas DS12887"
	depends on RTC_CLASS
	help
	  If you say Y here you will get support for the
	  ST M48T86 and Dallas DS12887 RTC chips.

	  This driver can also be built as a module. If so, the module
	  will be called rtc-m48t86.

config RTC_DRV_V3020
	tristate "EM Microelectronic V3020"
	depends on RTC_CLASS
	help
	  If you say yes here you will get support for the
	  EM Microelectronic v3020 RTC chip.

	  This driver can also be built as a module. If so, the module
	  will be called rtc-v3020.

comment "on-CPU RTC drivers"
	depends on RTC_CLASS

config RTC_DRV_OMAP
	tristate "TI OMAP1"
	depends on RTC_CLASS && ( \
		ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 )
	help
	  Say "yes" here to support the real time clock on TI OMAP1 chips.
	  This driver can also be built as a module called rtc-omap.
333

334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349
config RTC_DRV_S3C
	tristate "Samsung S3C series SoC RTC"
	depends on RTC_CLASS && ARCH_S3C2410
	help
	  RTC (Realtime Clock) driver for the clock inbuilt into the
	  Samsung S3C24XX series of SoCs. This can provide periodic
	  interrupt rates from 1Hz to 64Hz for user programs, and
	  wakeup from Alarm.

	  The driver currently supports the common features on all the
	  S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
	  and S3C2442.

	  This driver can also be build as a module. If so, the module
	  will be called rtc-s3c.

350 351 352 353 354 355 356 357 358 359
config RTC_DRV_EP93XX
	tristate "Cirrus Logic EP93XX"
	depends on RTC_CLASS && ARCH_EP93XX
	help
	  If you say yes here you get support for the
	  RTC embedded in the Cirrus Logic EP93XX processors.

	  This driver can also be built as a module. If so, the module
	  will be called rtc-ep93xx.

360 361 362 363 364 365 366 367 368
config RTC_DRV_SA1100
	tristate "SA11x0/PXA2xx"
	depends on RTC_CLASS && (ARCH_SA1100 || ARCH_PXA)
	help
	  If you say Y here you will get access to the real time clock
	  built into your SA11x0 or PXA2xx CPU.

	  To compile this driver as a module, choose M here: the
	  module will be called rtc-sa1100.
369

370 371 372 373 374 375 376 377 378 379
config RTC_DRV_SH
	tristate "SuperH On-Chip RTC"
	depends on RTC_CLASS && SUPERH
	help
	  Say Y here to enable support for the on-chip RTC found in
	  most SuperH processors.

 	  To compile this driver as a module, choose M here: the
	  module will be called rtc-sh.

380
config RTC_DRV_VR41XX
381
	tristate "NEC VR41XX"
382
	depends on RTC_CLASS && CPU_VR41XX
383 384 385 386 387 388
	help
	  If you say Y here you will get access to the real time clock
	  built into your NEC VR41XX CPU.

	  To compile this driver as a module, choose M here: the
	  module will be called rtc-vr41xx.
389

390 391 392 393 394
config RTC_DRV_PL031
	tristate "ARM AMBA PL031 RTC"
	depends on RTC_CLASS && ARM_AMBA
	help
	  If you say Y here you will get access to ARM AMBA
A
Alessandro Zummo 已提交
395
	  PrimeCell PL031 RTC found on certain ARM SOCs.
396 397 398 399

	  To compile this driver as a module, choose M here: the
	  module will be called rtc-pl031.

400 401 402 403 404 405 406
config RTC_DRV_AT32AP700X
	tristate "AT32AP700X series RTC"
	depends on RTC_CLASS && PLATFORM_AT32AP
	help
	  Driver for the internal RTC (Realtime Clock) on Atmel AVR32
	  AT32AP700x family processors.

A
Andrew Victor 已提交
407
config RTC_DRV_AT91RM9200
A
Andrew Victor 已提交
408 409 410 411 412
	tristate "AT91RM9200"
	depends on RTC_CLASS && ARCH_AT91RM9200
	help
	  Driver for the Atmel AT91RM9200's internal RTC (Realtime Clock).

413 414 415 416 417 418 419 420 421 422
config RTC_DRV_BFIN
	tristate "Blackfin On-Chip RTC"
	depends on RTC_CLASS && BFIN
	help
	  If you say yes here you will get support for the
	  Blackfin On-Chip Real Time Clock.

	  This driver can also be built as a module. If so, the module
	  will be called rtc-bfin.

N
Nobuhiro Iwamatsu 已提交
423 424
config RTC_DRV_RS5C313
	tristate "Ricoh RS5C313"
425
	depends on RTC_CLASS && SH_LANDISK
N
Nobuhiro Iwamatsu 已提交
426 427 428
	help
	  If you say yes here you get support for the Ricoh RS5C313 RTC chips.

A
Alessandro Zummo 已提交
429
endmenu