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