drivers/rtc/Kconfig

   1 #
   2 # RTC class/drivers configuration
   3 #
   4
   5 config RTC_LIB
   6         tristate
   7
   8 menuconfig RTC_CLASS
   9         tristate "Real Time Clock"
  10         default n
  11         depends on !S390
  12         select RTC_LIB
  13         help
  14           Generic RTC class support. If you say yes here, you will
  15           be allowed to plug one or more RTCs to your system. You will
  16           probably want to enable one or more of the interfaces below.
  17
  18           This driver can also be built as a module. If so, the module
  19           will be called rtc-class.
  20
  21 if RTC_CLASS
  22
  23 if GEN_RTC || RTC
  24 comment "Conflicting RTC option has been selected, check GEN_RTC and RTC"
  25 endif
  26
  27 config RTC_HCTOSYS
  28         bool "Set system time from RTC on startup and resume"
  29         depends on RTC_CLASS = y
  30         default y
  31         help
  32           If you say yes here, the system time (wall clock) will be set using
  33           the value read from a specified RTC device. This is useful to avoid
  34           unnecessary fsck runs at boot time, and to network better.
  35
  36 config RTC_HCTOSYS_DEVICE
  37         string "RTC used to set the system time"
  38         depends on RTC_HCTOSYS = y
  39         default "rtc0"
  40         help
  41           The RTC device that will be used to (re)initialize the system
  42           clock, usually rtc0.  Initialization is done when the system
  43           starts up, and when it resumes from a low power state.  This
  44           device should record time in UTC, since the kernel won't do
  45           timezone correction.
  46
  47           The driver for this RTC device must be loaded before late_initcall
  48           functions run, so it must usually be statically linked.
  49
  50           This clock should be battery-backed, so that it reads the correct
  51           time when the system boots from a power-off state.  Otherwise, your
  52           system will need an external clock source (like an NTP server).
  53
  54           If the clock you specify here is not battery backed, it may still
  55           be useful to reinitialize system time when resuming from system
  56           sleep states. Do not specify an RTC here unless it stays powered
  57           during all this system's supported sleep states.
  58
  59 config RTC_DEBUG
  60         bool "RTC debug support"
  61         depends on RTC_CLASS = y
  62         help
  63           Say yes here to enable debugging support in the RTC framework
  64           and individual RTC drivers.
  65
  66 comment "RTC interfaces"
  67
  68 config RTC_INTF_SYSFS
  69         boolean "/sys/class/rtc/rtcN (sysfs)"
  70         depends on SYSFS
  71         default RTC_CLASS
  72         help
  73           Say yes here if you want to use your RTCs using sysfs interfaces,
  74           /sys/class/rtc/rtc0 through /sys/.../rtcN.
  75
  76           This driver can also be built as a module. If so, the module
  77           will be called rtc-sysfs.
  78
  79 config RTC_INTF_PROC
  80         boolean "/proc/driver/rtc (procfs for rtc0)"
  81         depends on PROC_FS
  82         default RTC_CLASS
  83         help
  84           Say yes here if you want to use your first RTC through the proc
  85           interface, /proc/driver/rtc.  Other RTCs will not be available
  86           through that API.
  87
  88           This driver can also be built as a module. If so, the module
  89           will be called rtc-proc.
  90
  91 config RTC_INTF_DEV
  92         boolean "/dev/rtcN (character devices)"
  93         default RTC_CLASS
  94         help
  95           Say yes here if you want to use your RTCs using the /dev
  96           interfaces, which "udev" sets up as /dev/rtc0 through
  97           /dev/rtcN.  You may want to set up a symbolic link so one
  98           of these can be accessed as /dev/rtc, which is a name
  99           expected by "hwclock" and some other programs.
 100
 101           This driver can also be built as a module. If so, the module
 102           will be called rtc-dev.
 103
 104 config RTC_INTF_DEV_UIE_EMUL
 105         bool "RTC UIE emulation on dev interface"
 106         depends on RTC_INTF_DEV
 107         help
 108           Provides an emulation for RTC_UIE if the underlying rtc chip
 109           driver does not expose RTC_UIE ioctls.  Those requests generate
 110           once-per-second update interrupts, used for synchronization.
 111
 112 config RTC_DRV_TEST
 113         tristate "Test driver/device"
 114         help
 115           If you say yes here you get support for the
 116           RTC test driver. It's a software RTC which can be
 117           used to test the RTC subsystem APIs. It gets
 118           the time from the system clock.
 119           You want this driver only if you are doing development
 120           on the RTC subsystem. Please read the source code
 121           for further details.
 122
 123           This driver can also be built as a module. If so, the module
 124           will be called rtc-test.
 125
 126 comment "I2C RTC drivers"
 127         depends on I2C
 128
 129 if I2C
 130
 131 config RTC_DRV_DS1307
 132         tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00"
 133         help
 134           If you say yes here you get support for various compatible RTC
 135           chips (often with battery backup) connected with I2C.  This driver
 136           should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
 137           and probably other chips.  In some cases the RTC must already
 138           have been initialized (by manufacturing or a bootloader).
 139
 140           The first seven registers on these chips hold an RTC, and other
 141           registers may add features such as NVRAM, a trickle charger for
 142           the RTC/NVRAM backup power, and alarms.  NVRAM is visible in
 143           sysfs, but other chip features may not be available.
 144
 145           This driver can also be built as a module. If so, the module
 146           will be called rtc-ds1307.
 147
 148 config RTC_DRV_DS1374
 149         tristate "Dallas/Maxim DS1374"
 150         depends on RTC_CLASS && I2C
 151         help
 152           If you say yes here you get support for Dallas Semiconductor
 153           DS1374 real-time clock chips.  If an interrupt is associated
 154           with the device, the alarm functionality is supported.
 155
 156           This driver can also be built as a module.  If so, the module
 157           will be called rtc-ds1374.
 158
 159 config RTC_DRV_DS1672
 160         tristate "Dallas/Maxim DS1672"
 161         help
 162           If you say yes here you get support for the
 163           Dallas/Maxim DS1672 timekeeping chip.
 164
 165           This driver can also be built as a module. If so, the module
 166           will be called rtc-ds1672.
 167
 168 config RTC_DRV_MAX6900
 169         tristate "Maxim MAX6900"
 170         help
 171           If you say yes here you will get support for the
 172           Maxim MAX6900 I2C RTC chip.
 173
 174           This driver can also be built as a module. If so, the module
 175           will be called rtc-max6900.
 176
 177 config RTC_DRV_RS5C372
 178         tristate "Ricoh RS5C372A/B, RV5C386, RV5C387A"
 179         help
 180           If you say yes here you get support for the
 181           Ricoh RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
 182
 183           This driver can also be built as a module. If so, the module
 184           will be called rtc-rs5c372.
 185
 186 config RTC_DRV_ISL1208
 187         tristate "Intersil ISL1208"
 188         help
 189           If you say yes here you get support for the
 190           Intersil ISL1208 RTC chip.
 191
 192           This driver can also be built as a module. If so, the module
 193           will be called rtc-isl1208.
 194
 195 config RTC_DRV_X1205
 196         tristate "Xicor/Intersil X1205"
 197         help
 198           If you say yes here you get support for the
 199           Xicor/Intersil X1205 RTC chip.
 200
 201           This driver can also be built as a module. If so, the module
 202           will be called rtc-x1205.
 203
 204 config RTC_DRV_PCF8563
 205         tristate "Philips PCF8563/Epson RTC8564"
 206         help
 207           If you say yes here you get support for the
 208           Philips PCF8563 RTC chip. The Epson RTC8564
 209           should work as well.
 210
 211           This driver can also be built as a module. If so, the module
 212           will be called rtc-pcf8563.
 213
 214 config RTC_DRV_PCF8583
 215         tristate "Philips PCF8583"
 216         help
 217           If you say yes here you get support for the Philips PCF8583
 218           RTC chip found on Acorn RiscPCs. This driver supports the
 219           platform specific method of retrieving the current year from
 220           the RTC's SRAM. It will work on other platforms with the same
 221           chip, but the year will probably have to be tweaked.
 222
 223           This driver can also be built as a module. If so, the module
 224           will be called rtc-pcf8583.
 225
 226 config RTC_DRV_M41T80
 227         tristate "ST M41T80/81/82/83/84/85/87"
 228         help
 229           If you say Y here you will get support for the
 230           ST M41T80 RTC chips series. Currently following chips are
 231           supported: M41T80, M41T81, M41T82, M41T83, M41ST84, M41ST85
 232           and M41ST87.
 233
 234           This driver can also be built as a module. If so, the module
 235           will be called rtc-m41t80.
 236
 237 config RTC_DRV_M41T80_WDT
 238         bool "ST M41T80 series RTC watchdog timer"
 239         depends on RTC_DRV_M41T80
 240         help
 241           If you say Y here you will get support for the
 242           watchdog timer in ST M41T80 RTC chips series.
 243
 244 config RTC_DRV_TWL92330
 245         boolean "TI TWL92330/Menelaus"
 246         depends on MENELAUS
 247         help
 248           If you say yes here you get support for the RTC on the
 249           TWL92330 "Menelaus" power management chip, used with OMAP2
 250           platforms.  The support is integrated with the rest of
 251           the Menelaus driver; it's not separate module.
 252
 253 config RTC_DRV_S35390A
 254         tristate "Seiko Instruments S-35390A"
 255         help
 256           If you say yes here you will get support for the Seiko
 257           Instruments S-35390A.
 258
 259           This driver can also be built as a module. If so the module
 260           will be called rtc-s35390a.
 261
 262 endif # I2C
 263
 264 comment "SPI RTC drivers"
 265
 266 if SPI_MASTER
 267
 268 config RTC_DRV_MAX6902
 269         tristate "Maxim MAX6902"
 270         help
 271           If you say yes here you will get support for the
 272           Maxim MAX6902 SPI RTC chip.
 273
 274           This driver can also be built as a module. If so, the module
 275           will be called rtc-max6902.
 276
 277 config RTC_DRV_R9701
 278         tristate "Epson RTC-9701JE"
 279         help
 280           If you say yes here you will get support for the
 281           Epson RTC-9701JE SPI RTC chip.
 282
 283           This driver can also be built as a module. If so, the module
 284           will be called rtc-r9701.
 285
 286 config RTC_DRV_RS5C348
 287         tristate "Ricoh RS5C348A/B"
 288         help
 289           If you say yes here you get support for the
 290           Ricoh RS5C348A and RS5C348B RTC chips.
 291
 292           This driver can also be built as a module. If so, the module
 293           will be called rtc-rs5c348.
 294
 295 endif # SPI_MASTER
 296
 297 comment "Platform RTC drivers"
 298
 299 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
 300 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
 301 # global rtc_lock ... it's not yet just another platform_device.
 302
 303 config RTC_DRV_CMOS
 304         tristate "PC-style 'CMOS'"
 305         depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS
 306         help
 307           Say "yes" here to get direct support for the real time clock
 308           found in every PC or ACPI-based system, and some other boards.
 309           Specifically the original MC146818, compatibles like those in
 310           PC south bridges, the DS12887 or M48T86, some multifunction
 311           or LPC bus chips, and so on.
 312
 313           Your system will need to define the platform device used by
 314           this driver, otherwise it won't be accessible.  This means
 315           you can safely enable this driver if you don't know whether
 316           or not your board has this kind of hardware.
 317
 318           This driver can also be built as a module. If so, the module
 319           will be called rtc-cmos.
 320
 321 config RTC_DRV_DS1216
 322         tristate "Dallas DS1216"
 323         depends on SNI_RM
 324         help
 325           If you say yes here you get support for the Dallas DS1216 RTC chips.
 326
 327 config RTC_DRV_DS1302
 328         tristate "Dallas DS1302"
 329         depends on SH_SECUREEDGE5410
 330         help
 331           If you say yes here you get support for the Dallas DS1302 RTC chips.
 332
 333 config RTC_DRV_DS1511
 334         tristate "Dallas DS1511"
 335         depends on RTC_CLASS
 336         help
 337           If you say yes here you get support for the
 338           Dallas DS1511 timekeeping/watchdog chip.
 339
 340           This driver can also be built as a module. If so, the module
 341           will be called rtc-ds1511.
 342
 343 config RTC_DRV_DS1553
 344         tristate "Maxim/Dallas DS1553"
 345         help
 346           If you say yes here you get support for the
 347           Maxim/Dallas DS1553 timekeeping chip.
 348
 349           This driver can also be built as a module. If so, the module
 350           will be called rtc-ds1553.
 351
 352 config RTC_DRV_DS1742
 353         tristate "Maxim/Dallas DS1742/1743"
 354         help
 355           If you say yes here you get support for the
 356           Maxim/Dallas DS1742/1743 timekeeping chip.
 357
 358           This driver can also be built as a module. If so, the module
 359           will be called rtc-ds1742.
 360
 361 config RTC_DRV_STK17TA8
 362         tristate "Simtek STK17TA8"
 363         depends on RTC_CLASS
 364         help
 365           If you say yes here you get support for the
 366           Simtek STK17TA8 timekeeping chip.
 367
 368           This driver can also be built as a module. If so, the module
 369           will be called rtc-stk17ta8.
 370
 371 config RTC_DRV_M48T86
 372         tristate "ST M48T86/Dallas DS12887"
 373         help
 374           If you say Y here you will get support for the
 375           ST M48T86 and Dallas DS12887 RTC chips.
 376
 377           This driver can also be built as a module. If so, the module
 378           will be called rtc-m48t86.
 379
 380 config RTC_DRV_M48T59
 381         tristate "ST M48T59"
 382         help
 383           If you say Y here you will get support for the
 384           ST M48T59 RTC chip.
 385
 386           This driver can also be built as a module, if so, the module
 387           will be called "rtc-m48t59".
 388
 389 config RTC_DRV_V3020
 390         tristate "EM Microelectronic V3020"
 391         help
 392           If you say yes here you will get support for the
 393           EM Microelectronic v3020 RTC chip.
 394
 395           This driver can also be built as a module. If so, the module
 396           will be called rtc-v3020.
 397
 398 comment "on-CPU RTC drivers"
 399
 400 config RTC_DRV_OMAP
 401         tristate "TI OMAP1"
 402         depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730
 403         help
 404           Say "yes" here to support the real time clock on TI OMAP1 chips.
 405           This driver can also be built as a module called rtc-omap.
 406
 407 config RTC_DRV_S3C
 408         tristate "Samsung S3C series SoC RTC"
 409         depends on ARCH_S3C2410
 410         help
 411           RTC (Realtime Clock) driver for the clock inbuilt into the
 412           Samsung S3C24XX series of SoCs. This can provide periodic
 413           interrupt rates from 1Hz to 64Hz for user programs, and
 414           wakeup from Alarm.
 415
 416           The driver currently supports the common features on all the
 417           S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
 418           and S3C2442.
 419
 420           This driver can also be build as a module. If so, the module
 421           will be called rtc-s3c.
 422
 423 config RTC_DRV_EP93XX
 424         tristate "Cirrus Logic EP93XX"
 425         depends on ARCH_EP93XX
 426         help
 427           If you say yes here you get support for the
 428           RTC embedded in the Cirrus Logic EP93XX processors.
 429
 430           This driver can also be built as a module. If so, the module
 431           will be called rtc-ep93xx.
 432
 433 config RTC_DRV_SA1100
 434         tristate "SA11x0/PXA2xx"
 435         depends on ARCH_SA1100 || ARCH_PXA
 436         help
 437           If you say Y here you will get access to the real time clock
 438           built into your SA11x0 or PXA2xx CPU.
 439
 440           To compile this driver as a module, choose M here: the
 441           module will be called rtc-sa1100.
 442
 443 config RTC_DRV_SH
 444         tristate "SuperH On-Chip RTC"
 445         depends on RTC_CLASS && SUPERH
 446         help
 447           Say Y here to enable support for the on-chip RTC found in
 448           most SuperH processors.
 449
 450           To compile this driver as a module, choose M here: the
 451           module will be called rtc-sh.
 452
 453 config RTC_DRV_VR41XX
 454         tristate "NEC VR41XX"
 455         depends on CPU_VR41XX
 456         help
 457           If you say Y here you will get access to the real time clock
 458           built into your NEC VR41XX CPU.
 459
 460           To compile this driver as a module, choose M here: the
 461           module will be called rtc-vr41xx.
 462
 463 config RTC_DRV_PL031
 464         tristate "ARM AMBA PL031 RTC"
 465         depends on ARM_AMBA
 466         help
 467           If you say Y here you will get access to ARM AMBA
 468           PrimeCell PL031 RTC found on certain ARM SOCs.
 469
 470           To compile this driver as a module, choose M here: the
 471           module will be called rtc-pl031.
 472
 473 config RTC_DRV_AT32AP700X
 474         tristate "AT32AP700X series RTC"
 475         depends on PLATFORM_AT32AP
 476         help
 477           Driver for the internal RTC (Realtime Clock) on Atmel AVR32
 478           AT32AP700x family processors.
 479
 480 config RTC_DRV_AT91RM9200
 481         tristate "AT91RM9200 or AT91SAM9RL"
 482         depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
 483         help
 484           Driver for the internal RTC (Realtime Clock) module found on
 485           Atmel AT91RM9200's and AT91SAM9RL chips.  On SAM9RL chips
 486           this is powered by the backup power supply.
 487
 488 config RTC_DRV_AT91SAM9
 489         tristate "AT91SAM9x"
 490         depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
 491         help
 492           RTC driver for the Atmel AT91SAM9x internal RTT (Real Time Timer).
 493           These timers are powered by the backup power supply (such as a
 494           small coin cell battery), but do not need to be used as RTCs.
 495
 496           (On AT91SAM9rl chips you probably want to use the dedicated RTC
 497           module and leave the RTT available for other uses.)
 498
 499 config RTC_DRV_AT91SAM9_RTT
 500         int
 501         range 0 1
 502         default 0
 503         prompt "RTT module Number" if ARCH_AT91SAM9263
 504         depends on RTC_DRV_AT91SAM9
 505         help
 506           More than one RTT module is available.  You can choose which
 507           one will be used as an RTC.  The default of zero is normally
 508           OK to use, though some systems use that for non-RTC purposes.
 509
 510 config RTC_DRV_AT91SAM9_GPBR
 511         int
 512         range 0 3 if !ARCH_AT91SAM9263
 513         range 0 15 if ARCH_AT91SAM9263
 514         default 0
 515         prompt "Backup Register Number"
 516         depends on RTC_DRV_AT91SAM9
 517         help
 518           The RTC driver needs to use one of the General Purpose Backup
 519           Registers (GPBRs) as well as the RTT.  You can choose which one
 520           will be used.  The default of zero is normally OK to use, but
 521           on some systems other software needs to use that register.
 522
 523 config RTC_DRV_BFIN
 524         tristate "Blackfin On-Chip RTC"
 525         depends on BLACKFIN
 526         help
 527           If you say yes here you will get support for the
 528           Blackfin On-Chip Real Time Clock.
 529
 530           This driver can also be built as a module. If so, the module
 531           will be called rtc-bfin.
 532
 533 config RTC_DRV_RS5C313
 534         tristate "Ricoh RS5C313"
 535         depends on SH_LANDISK
 536         help
 537           If you say yes here you get support for the Ricoh RS5C313 RTC chips.
 538
 539 endif # RTC_CLASS