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           The emulation code will read the time from the hardware
 109           clock several times per second, please enable this option
 110           only if you know that you really need it.
 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 R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
 179         help
 180           If you say yes here you get support for the
 181           Ricoh R2025S/D, 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 M41T65/M41T80/81/82/83/84/85/87"
 228         help
 229           If you say Y here you will get support for the ST M41T60
 230           and M41T80 RTC chips series. Currently, the following chips are
 231           supported: M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
 232           M41ST85, 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 M41T65/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 the ST M41T60 and 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_TWL4030
 254         tristate "TI TWL4030/TWL5030/TPS659x0"
 255         depends on RTC_CLASS && TWL4030_CORE
 256         help
 257           If you say yes here you get support for the RTC on the
 258           TWL4030 family chips, used mostly with OMAP3 platforms.
 259
 260           This driver can also be built as a module. If so, the module
 261           will be called rtc-twl4030.
 262
 263 config RTC_DRV_S35390A
 264         tristate "Seiko Instruments S-35390A"
 265         select BITREVERSE
 266         help
 267           If you say yes here you will get support for the Seiko
 268           Instruments S-35390A.
 269
 270           This driver can also be built as a module. If so the module
 271           will be called rtc-s35390a.
 272
 273 config RTC_DRV_FM3130
 274         tristate "Ramtron FM3130"
 275         help
 276           If you say Y here you will get support for the
 277           Ramtron FM3130 RTC chips.
 278           Ramtron FM3130 is a chip with two separate devices inside,
 279           RTC clock and FRAM. This driver provides only RTC functionality.
 280
 281           This driver can also be built as a module. If so the module
 282           will be called rtc-fm3130.
 283
 284 config RTC_DRV_RX8581
 285         tristate "Epson RX-8581"
 286         help
 287           If you say yes here you will get support for the Epson RX-8581.
 288
 289           This driver can also be built as a module. If so the module
 290           will be called rtc-rx8581.
 291
 292 endif # I2C
 293
 294 comment "SPI RTC drivers"
 295
 296 if SPI_MASTER
 297
 298 config RTC_DRV_M41T94
 299         tristate "ST M41T94"
 300         help
 301           If you say yes here you will get support for the
 302           ST M41T94 SPI RTC chip.
 303
 304           This driver can also be built as a module. If so, the module
 305           will be called rtc-m41t94.
 306
 307 config RTC_DRV_DS1305
 308         tristate "Dallas/Maxim DS1305/DS1306"
 309         help
 310           Select this driver to get support for the Dallas/Maxim DS1305
 311           and DS1306 real time clock chips.  These support a trickle
 312           charger, alarms, and NVRAM in addition to the clock.
 313
 314           This driver can also be built as a module. If so, the module
 315           will be called rtc-ds1305.
 316
 317 config RTC_DRV_DS1390
 318         tristate "Dallas/Maxim DS1390/93/94"
 319         help
 320           If you say yes here you get support for the DS1390/93/94 chips.
 321
 322           This driver only supports the RTC feature, and not other chip
 323           features such as alarms and trickle charging.
 324
 325           This driver can also be built as a module. If so, the module
 326           will be called rtc-ds1390.
 327
 328 config RTC_DRV_MAX6902
 329         tristate "Maxim MAX6902"
 330         help
 331           If you say yes here you will get support for the
 332           Maxim MAX6902 SPI RTC chip.
 333
 334           This driver can also be built as a module. If so, the module
 335           will be called rtc-max6902.
 336
 337 config RTC_DRV_R9701
 338         tristate "Epson RTC-9701JE"
 339         help
 340           If you say yes here you will get support for the
 341           Epson RTC-9701JE SPI RTC chip.
 342
 343           This driver can also be built as a module. If so, the module
 344           will be called rtc-r9701.
 345
 346 config RTC_DRV_RS5C348
 347         tristate "Ricoh RS5C348A/B"
 348         help
 349           If you say yes here you get support for the
 350           Ricoh RS5C348A and RS5C348B RTC chips.
 351
 352           This driver can also be built as a module. If so, the module
 353           will be called rtc-rs5c348.
 354
 355 config RTC_DRV_DS3234
 356         tristate "Maxim/Dallas DS3234"
 357         help
 358           If you say yes here you get support for the
 359           Maxim/Dallas DS3234 SPI RTC chip.
 360
 361           This driver can also be built as a module. If so, the module
 362           will be called rtc-ds3234.
 363
 364 endif # SPI_MASTER
 365
 366 comment "Platform RTC drivers"
 367
 368 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
 369 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
 370 # global rtc_lock ... it's not yet just another platform_device.
 371
 372 config RTC_DRV_CMOS
 373         tristate "PC-style 'CMOS'"
 374         depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
 375         default y if X86
 376         help
 377           Say "yes" here to get direct support for the real time clock
 378           found in every PC or ACPI-based system, and some other boards.
 379           Specifically the original MC146818, compatibles like those in
 380           PC south bridges, the DS12887 or M48T86, some multifunction
 381           or LPC bus chips, and so on.
 382
 383           Your system will need to define the platform device used by
 384           this driver, otherwise it won't be accessible.  This means
 385           you can safely enable this driver if you don't know whether
 386           or not your board has this kind of hardware.
 387
 388           This driver can also be built as a module. If so, the module
 389           will be called rtc-cmos.
 390
 391 config RTC_DRV_DS1216
 392         tristate "Dallas DS1216"
 393         depends on SNI_RM
 394         help
 395           If you say yes here you get support for the Dallas DS1216 RTC chips.
 396
 397 config RTC_DRV_DS1286
 398         tristate "Dallas DS1286"
 399         help
 400           If you say yes here you get support for the Dallas DS1286 RTC chips.
 401
 402 config RTC_DRV_DS1302
 403         tristate "Dallas DS1302"
 404         depends on SH_SECUREEDGE5410
 405         help
 406           If you say yes here you get support for the Dallas DS1302 RTC chips.
 407
 408 config RTC_DRV_DS1511
 409         tristate "Dallas DS1511"
 410         depends on RTC_CLASS
 411         help
 412           If you say yes here you get support for the
 413           Dallas DS1511 timekeeping/watchdog chip.
 414
 415           This driver can also be built as a module. If so, the module
 416           will be called rtc-ds1511.
 417
 418 config RTC_DRV_DS1553
 419         tristate "Maxim/Dallas DS1553"
 420         help
 421           If you say yes here you get support for the
 422           Maxim/Dallas DS1553 timekeeping chip.
 423
 424           This driver can also be built as a module. If so, the module
 425           will be called rtc-ds1553.
 426
 427 config RTC_DRV_DS1742
 428         tristate "Maxim/Dallas DS1742/1743"
 429         help
 430           If you say yes here you get support for the
 431           Maxim/Dallas DS1742/1743 timekeeping chip.
 432
 433           This driver can also be built as a module. If so, the module
 434           will be called rtc-ds1742.
 435
 436 config RTC_DRV_STK17TA8
 437         tristate "Simtek STK17TA8"
 438         depends on RTC_CLASS
 439         help
 440           If you say yes here you get support for the
 441           Simtek STK17TA8 timekeeping chip.
 442
 443           This driver can also be built as a module. If so, the module
 444           will be called rtc-stk17ta8.
 445
 446 config RTC_DRV_M48T86
 447         tristate "ST M48T86/Dallas DS12887"
 448         help
 449           If you say Y here you will get support for the
 450           ST M48T86 and Dallas DS12887 RTC chips.
 451
 452           This driver can also be built as a module. If so, the module
 453           will be called rtc-m48t86.
 454
 455 config RTC_DRV_M48T35
 456         tristate "ST M48T35"
 457         help
 458           If you say Y here you will get support for the
 459           ST M48T35 RTC chip.
 460
 461           This driver can also be built as a module, if so, the module
 462           will be called "rtc-m48t35".
 463
 464 config RTC_DRV_M48T59
 465         tristate "ST M48T59/M48T08/M48T02"
 466         help
 467           If you say Y here you will get support for the
 468           ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
 469
 470           These chips are usually found in Sun SPARC and UltraSPARC
 471           workstations.
 472
 473           This driver can also be built as a module, if so, the module
 474           will be called "rtc-m48t59".
 475
 476 config RTC_DRV_BQ4802
 477         tristate "TI BQ4802"
 478         help
 479           If you say Y here you will get support for the TI
 480           BQ4802 RTC chip.
 481
 482           This driver can also be built as a module. If so, the module
 483           will be called rtc-bq4802.
 484
 485 config RTC_DRV_V3020
 486         tristate "EM Microelectronic V3020"
 487         help
 488           If you say yes here you will get support for the
 489           EM Microelectronic v3020 RTC chip.
 490
 491           This driver can also be built as a module. If so, the module
 492           will be called rtc-v3020.
 493
 494 config RTC_DRV_WM8350
 495         tristate "Wolfson Microelectronics WM8350 RTC"
 496         depends on MFD_WM8350
 497         help
 498           If you say yes here you will get support for the RTC subsystem
 499           of the Wolfson Microelectronics WM8350.
 500
 501           This driver can also be built as a module. If so, the module
 502           will be called "rtc-wm8350".
 503
 504 comment "on-CPU RTC drivers"
 505
 506 config RTC_DRV_OMAP
 507         tristate "TI OMAP1"
 508         depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730
 509         help
 510           Say "yes" here to support the real time clock on TI OMAP1 chips.
 511           This driver can also be built as a module called rtc-omap.
 512
 513 config RTC_DRV_S3C
 514         tristate "Samsung S3C series SoC RTC"
 515         depends on ARCH_S3C2410
 516         help
 517           RTC (Realtime Clock) driver for the clock inbuilt into the
 518           Samsung S3C24XX series of SoCs. This can provide periodic
 519           interrupt rates from 1Hz to 64Hz for user programs, and
 520           wakeup from Alarm.
 521
 522           The driver currently supports the common features on all the
 523           S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
 524           and S3C2442.
 525
 526           This driver can also be build as a module. If so, the module
 527           will be called rtc-s3c.
 528
 529 config RTC_DRV_EP93XX
 530         tristate "Cirrus Logic EP93XX"
 531         depends on ARCH_EP93XX
 532         help
 533           If you say yes here you get support for the
 534           RTC embedded in the Cirrus Logic EP93XX processors.
 535
 536           This driver can also be built as a module. If so, the module
 537           will be called rtc-ep93xx.
 538
 539 config RTC_DRV_SA1100
 540         tristate "SA11x0/PXA2xx"
 541         depends on ARCH_SA1100 || ARCH_PXA
 542         help
 543           If you say Y here you will get access to the real time clock
 544           built into your SA11x0 or PXA2xx CPU.
 545
 546           To compile this driver as a module, choose M here: the
 547           module will be called rtc-sa1100.
 548
 549 config RTC_DRV_SH
 550         tristate "SuperH On-Chip RTC"
 551         depends on RTC_CLASS && SUPERH
 552         help
 553           Say Y here to enable support for the on-chip RTC found in
 554           most SuperH processors.
 555
 556           To compile this driver as a module, choose M here: the
 557           module will be called rtc-sh.
 558
 559 config RTC_DRV_VR41XX
 560         tristate "NEC VR41XX"
 561         depends on CPU_VR41XX
 562         help
 563           If you say Y here you will get access to the real time clock
 564           built into your NEC VR41XX CPU.
 565
 566           To compile this driver as a module, choose M here: the
 567           module will be called rtc-vr41xx.
 568
 569 config RTC_DRV_PL030
 570         tristate "ARM AMBA PL030 RTC"
 571         depends on ARM_AMBA
 572         help
 573           If you say Y here you will get access to ARM AMBA
 574           PrimeCell PL030 RTC found on certain ARM SOCs.
 575
 576           To compile this driver as a module, choose M here: the
 577           module will be called rtc-pl030.
 578
 579 config RTC_DRV_PL031
 580         tristate "ARM AMBA PL031 RTC"
 581         depends on ARM_AMBA
 582         help
 583           If you say Y here you will get access to ARM AMBA
 584           PrimeCell PL031 RTC found on certain ARM SOCs.
 585
 586           To compile this driver as a module, choose M here: the
 587           module will be called rtc-pl031.
 588
 589 config RTC_DRV_AT32AP700X
 590         tristate "AT32AP700X series RTC"
 591         depends on PLATFORM_AT32AP
 592         help
 593           Driver for the internal RTC (Realtime Clock) on Atmel AVR32
 594           AT32AP700x family processors.
 595
 596 config RTC_DRV_AT91RM9200
 597         tristate "AT91RM9200 or AT91SAM9RL"
 598         depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
 599         help
 600           Driver for the internal RTC (Realtime Clock) module found on
 601           Atmel AT91RM9200's and AT91SAM9RL chips.  On SAM9RL chips
 602           this is powered by the backup power supply.
 603
 604 config RTC_DRV_AT91SAM9
 605         tristate "AT91SAM9x/AT91CAP9"
 606         depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
 607         help
 608           RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
 609           (Real Time Timer). These timers are powered by the backup power
 610           supply (such as a small coin cell battery), but do not need to
 611           be used as RTCs.
 612
 613           (On AT91SAM9rl chips you probably want to use the dedicated RTC
 614           module and leave the RTT available for other uses.)
 615
 616 config RTC_DRV_AT91SAM9_RTT
 617         int
 618         range 0 1
 619         default 0
 620         prompt "RTT module Number" if ARCH_AT91SAM9263
 621         depends on RTC_DRV_AT91SAM9
 622         help
 623           More than one RTT module is available.  You can choose which
 624           one will be used as an RTC.  The default of zero is normally
 625           OK to use, though some systems use that for non-RTC purposes.
 626
 627 config RTC_DRV_AT91SAM9_GPBR
 628         int
 629         range 0 3 if !ARCH_AT91SAM9263
 630         range 0 15 if ARCH_AT91SAM9263
 631         default 0
 632         prompt "Backup Register Number"
 633         depends on RTC_DRV_AT91SAM9
 634         help
 635           The RTC driver needs to use one of the General Purpose Backup
 636           Registers (GPBRs) as well as the RTT.  You can choose which one
 637           will be used.  The default of zero is normally OK to use, but
 638           on some systems other software needs to use that register.
 639
 640 config RTC_DRV_BFIN
 641         tristate "Blackfin On-Chip RTC"
 642         depends on BLACKFIN && !BF561
 643         help
 644           If you say yes here you will get support for the
 645           Blackfin On-Chip Real Time Clock.
 646
 647           This driver can also be built as a module. If so, the module
 648           will be called rtc-bfin.
 649
 650 config RTC_DRV_RS5C313
 651         tristate "Ricoh RS5C313"
 652         depends on SH_LANDISK
 653         help
 654           If you say yes here you get support for the Ricoh RS5C313 RTC chips.
 655
 656 config RTC_DRV_PARISC
 657         tristate "PA-RISC firmware RTC support"
 658         depends on PARISC
 659         help
 660           Say Y or M here to enable RTC support on PA-RISC systems using
 661           firmware calls. If you do not know what you are doing, you should
 662           just say Y.
 663
 664 config RTC_DRV_PPC
 665        tristate "PowerPC machine dependent RTC support"
 666        depends on PPC
 667        help
 668          The PowerPC kernel has machine-specific functions for accessing
 669          the RTC. This exposes that functionality through the generic RTC
 670          class.
 671
 672 config RTC_DRV_SUN4V
 673         bool "SUN4V Hypervisor RTC"
 674         depends on SPARC64
 675         help
 676           If you say Y here you will get support for the Hypervisor
 677           based RTC on SUN4V systems.
 678
 679 config RTC_DRV_STARFIRE
 680         bool "Starfire RTC"
 681         depends on SPARC64
 682         help
 683           If you say Y here you will get support for the RTC found on
 684           Starfire systems.
 685
 686 endif # RTC_CLASS